.env.example, overbae/settings.py, docker-compose.yml and frontend/.env.example define the current deployment contract. Set secrets through protected configuration; do not commit filled environment files.
Use this in your platform checkout when self-hosting Overmind.
Local development endpoints
These addresses apply when running the platform locally with Compose. A remote self-hosted deployment uses its configured addresses.Required configuration
Current API startup validation requires values for the following services, even if your first task does not launch training:FINETUNING_BACKEND must be modal. Set MODAL_ENVIRONMENT explicitly and deploy the immutable worker releases expected by the API. Local hot reload does not deploy changed provider code.
Identity and URLs
Local frontend overrides belong in
.env.development.local; the repository’s environment-specific files take precedence over a generic .env.
Workers and sandbox
Compose has six Celery worker/queue profiles:control, io, io_traces, batch, landing and interactive. Trace scoring is isolated from file landing and interactive preparation. Waiting jobs do not imply that their execution attempt has started.
Document parsing and retained Python packages execute through the isolated sandbox. It has no platform credentials, shared application media mount or outbound network. The landing worker streams retained bytes and receives progress; unavailable parsing does not fall back to application-process execution.
WORKSHOP_PROJECT_CONCURRENCY bounds per-project interactive execution. Shared admission and observed capacity govern landing. Do not change queue topology merely to clear a slow job without understanding its resource limits.
Model pacing and analytics
JEV_REQUESTS_PER_MINUTE and JEV_TOKENS_PER_SECOND control account-wide pacing through shared capacity. Configuration failure is a technical scoring error, not permission to substitute a generative judge.
POSTHOG_PROJECT_TOKEN enables optional server product analytics according to deployment settings. Local analytics remains off unless configured. Training evidence is retained independently of analytics delivery.
Metering and billing
WithSTRIPE_SECRET_KEY configured, remaining-credit and seat/plan controls apply. Without it, usage can still be metered without the remaining-credit gate. Native coding-agent usage belongs to its external environment; model evaluations, training and serving have their own execution costs.
Published rates, worker measurements and recorded ledger charges have different scopes. A local API address or a missing platform credit gate is not a promise of free provider execution.