Skip to main content

Environment Variables Reference

This reference documents all environment variables available for configuring Simba Intelligence. Variables are grouped by function and include defaults and descriptions.
๐Ÿ“ Note: LLM provider credentials are not configured via environment variables. They are managed per-tenant through the web interface at /llm-configuration. See the LLM Provider Configuration guide.

Application Mode

APP_MODE Values


Core Infrastructure


Web Server (Gunicorn)

These variables tune the Gunicorn web server that runs the main application (APP_MODE=web).
๐Ÿ’ก Pro Tip: For memory-constrained environments, reduce GUNICORN_WORKERS and GUNICORN_MAX_REQUESTS. For high-throughput deployments, increase workers and threads proportionally to available CPU cores.

MCP Server

These variables configure the MCP server container (APP_MODE=mcp). See the MCP Server Guide for full deployment details.

Database Migrations

โš ๏ธ Important: In production Kubernetes deployments, it is recommended to set DISABLE_DB_MIGRATIONS=true on the web container and run migrations via the dedicated simba-intelligence-db-migrate-job Helm job instead. This prevents migration race conditions when running multiple web replicas.

CORS Configuration

Cross-Origin Resource Sharing settings for the web application.
๐Ÿ“ Note: CORS is disabled by default, which is the most secure configuration for same-origin deployments. Only enable CORS if your frontend is hosted on a different domain than the Simba Intelligence API.

Content Security Policy (CSP)

These variables control the Content-Security-Policy response headers.
โš ๏ธ Important: If you embed Simba Intelligence in an iframe or load external resources (e.g., custom fonts from a CDN), you must adjust the relevant CSP directives. Overly restrictive CSP values can break frontend functionality.

Logging

Example LOG_LEVELS configuration:

Celery (Background Tasks)

๐Ÿ“ Note: REDIS_URL (listed under Core Infrastructure) is also used as the Celery broker and result backend.

Composer Integration


Caching

The field-value cache stores the distinct values seen for each data-source attribute field (e.g., the list of values in a โ€œRegionโ€ or โ€œStatusโ€ column), so the Query Agent can match user text against real values without re-fetching them from Composer on every query.
๐Ÿ“ Note: FIELD_VALUE_CACHE_BUDGET_MB sizes only this one cache โ€” it is not a limit on Redisโ€™s total memory usage. Redis also holds the semantic/question-record cache, suggestions cache, and Celery broker data, none of which count against this budget. It is set via extraEnvs on both the web and worker deployments (see APP_MODE above) in the Helm chartโ€™s values.yaml. Keep the value identical across both โ€” the cache is shared/tenant-scoped in Redis, not tuned per pod type.