Configuration Reference
All Corbulo configuration is done through environment variables. There are no configuration files. Required variables have no defaults — the application will not start if they are missing.Core
Database
Redis
Temporal
FalkorDB
Authentication (Clerk)
GitHub
Frontend and CORS
For production deployments, set
CORS_ORIGINS to your actual frontend domain (e.g., https://corbulo.yourcompany.com). The defaults are intended for local development only.AI Models
Corbulo uses 4 model slots for different analysis tasks. Each slot can be configured independently, allowing you to use different providers or models for different workloads.Slot Overview
At minimum, configure the OpenAI Large and OpenAI Small slots. The Anthropic slots are optional overrides.
Environment Variables per Slot
Each slot uses the same set of variables with a different prefix:
For each prefix, the following variables are available:
Example Configuration
Task-to-Model Routing
By default, tasks are routed to model slots automatically. You can override this with theTASK_MODEL_MAPPING variable:
Default routing:
Override example:
Analyzers
Kubernetes Agent (k8s mode only)
These variables are only used whenAGENT_EXECUTION_MODE is set to k8s:
Worker Concurrency
Increase these values on machines with more CPU and memory to improve throughput. Reduce them if workers are running out of memory.
OpenTelemetry
Health Endpoints
The API server exposes the following operational endpoints:Monitoring
Prometheus
Scrape the/metrics endpoint on port 8080. If deploying on Kubernetes with the Helm chart, enable the ServiceMonitor to configure automatic discovery.
OpenTelemetry
Set theOTEL_* variables above to send distributed traces to your OpenTelemetry collector. Traces cover HTTP requests, Temporal workflow execution, database queries, and AI model calls.
Structured Logging
All components emit structured JSON logs to stdout. Key fields:
Set
LOG_LEVEL to debug for verbose output during troubleshooting. Use info or warn in production.