Firecrawl Production Deployment

Overview

Deploy the application client and the Firecrawl service as separate responsibilities. Cloud integrations need a protected key and egress policy; self-hosting adds databases, queues, browsers, storage, authentication, upgrades, and recovery.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The source authorization, data classification, and environment policy.
• Current Firecrawl documentation, credentials only when needed, and an owner for approvals.

Current Contract

Cloud clients use the v2 API and secret-managed FIRECRAWL_API_KEY. The official self-host guide's Compose example is an evaluation baseline with authentication disabled and without durable storage, TLS, high availability, or every Cloud capability. Pin the reviewed release and its own Compose contract; do not copy a floating main configuration into production.

Authentication