Configuration

backend/app/core/config.py is the complete settings catalog. Non-secret deployment defaults live in service manifests; secrets belong in Vault or the hosting platform’s secret store.

Core runtime

Variable	Purpose	Typical default
`DATABASE_URL`	Postgres connection	Required outside local defaults
`REDIS_URL`	Queues, locks, rate limits, and heartbeats	Required
`LUCIM_STAGE`	Mount Stage 1, 2, or 3 surfaces	`1`
`ALLOWED_ORIGINS`	Comma-separated browser origins	Deployment-specific
`OBJECT_STORAGE_*`	S3-compatible artifact storage	Deployment-specific
`BACKGROUND_WORKER_REQUIRED_FOR_READINESS`	Require ordinary-worker heartbeat	`false`
`REPOSITORY_SCANNER_REQUIRED_FOR_READINESS`	Require scanner heartbeat	`false`

Programmatic access

Variable	Purpose	Default
`API_RATE_LIMIT_PER_MINUTE`	Per-key short-window limit	`60`
`API_RATE_LIMIT_PER_DAY`	Per-key daily limit	`5000`
`LUCIM_MCP_API_KEY`	Single-tenant stdio MCP credential	Empty

Acquisition and discovery

Gate	Related secret	Purpose
`FIRECRAWL_ENABLED`	`FIRECRAWL_API_KEY`	Public map, search, and rendered acquisition
`FIRECRAWL_WEBHOOKS_ENABLED`	`FIRECRAWL_WEBHOOK_SECRET`	Signed async provider callbacks
`EXA_ENABLED`	`EXA_API_KEY`	Semantic gap-search leads
`MCP_INTROSPECTION_ENABLED`	Referenced worker auth payloads	Remote MCP capture
`REPOSITORY_SCANNER_ENABLED`	Intake credentials	Non-executing repository scans

Each provider also has explicit concurrency, request, item, byte, page, credit, timeout, and retry bounds. Invalid values fail startup rather than widening admission.

AI

OPENROUTER_API_KEY enables AI-only work through the shared OpenRouter client. Deterministic monitoring remains available without it. Remediation uses the dedicated configured model tier; embeddings and other tasks use their own explicit settings.

Provider delivery

Nango authorization requires NANGO_ENABLED, runtime API and webhook-signing keys, and stable provider integration IDs. PROVIDER_ROUTING_ENABLED exposes route management; PROVIDER_DISPATCH_ENABLED separately permits outbound provider work.

Sandbox execution

Keep SANDBOX_ENABLED, SANDBOX_STDIO_ENABLED, and broker/provider gates false until runtime digests, signing and broker keys, provider conformance evidence, and dedicated-worker health match across control and execution planes.

Do not copy a broad .env file into every process. Give API, ordinary worker, hosted MCP, scanner, and sandbox worker only the secrets each process owns.

​Core runtime

​Programmatic access

​Acquisition and discovery

​AI

​Provider delivery

​Sandbox execution

Core runtime

Programmatic access

Acquisition and discovery

AI

Provider delivery

Sandbox execution