Skip to main content
Core environment variables are centralized in api/constants.py. Variables marked Required in the description must be explicitly set โ€” the application will either fail to boot or behave insecurely without them.

Deployment Modes

Ringlyra supports two deployment modes, set via DEPLOYMENT_MODE:
  • OSS: The default mode. Designed for self-hosted deployments using Docker Compose โ€” the fastest way to get Ringlyra running. Uses local JWT authentication and MinIO for storage.
  • SaaS: Intended for customised deployments outside of Docker. Authentication and API key management are handled through Ringlyra Managed Platform Services (MPS), allowing greater flexibility in how the platform is hosted and integrated.
The relevant required variables for each mode are noted in the descriptions below.

Application


Database


Authentication (OSS)

Never use the placeholder OSS_JWT_SECRET in a production deployment. Generate a strong random secret and store it securely.

URLs


Storage

Ringlyra uses MinIO by default, which is bundled with the self-hosted deployment and requires no external setup. Set ENABLE_AWS_S3=true to switch to AWS S3 โ€” typically used for cloud or managed deployments where S3 is already part of the infrastructure.

MinIO (OSS default)

AWS S3 (alternative)


WebRTC


Tracing (Langfuse)

Tracing activates automatically as soon as credentials are available โ€” either via these environment variables (applied to all organizations) or per-organization in the UI under Platform Settings. If neither is set, spans are dropped silently. See the Tracing guide for setup instructions.

Monitoring


Logging


Campaigns


Further Customisation

The variables documented here cover the standard configuration surface. For advanced customisation โ€” such as integrating additional services or tuning internal behaviour โ€” consult the relevant module alongside api/constants.py to understand how each variable is consumed.