production, staging, or development). Database Configs, data-source connectors, and signal bindings are all scoped to an environment so you can point the same OpenLIT project at different backends without redeploying with new env vars.
Day-2 connection changes happen in the UI under the selected environment — not by editing
INIT_DB_* on the running container. See Database Config.Why environments exist
Switch environment
Use the environment control in the top navigation (next to organisation and project). Switching environment refreshes:- Available Database Configs for that environment
- Connectors created in that environment
- Signal bindings for traces, logs, and metrics
Create or use an environment
Environments are created when you add a Database Config or connector with a new environment name, or from project environment management in Organisation settings. Names must be lowercase letters, numbers, dots, hyphens, or underscores (for exampleproduction, us-east.staging).
1
Select project
Choose the project in the header.
2
Pick or create environment
Select an existing environment, or enter a new name when adding a Database Config / connector.
3
Attach resources
Add a Database Config and optional connectors for that environment.
4
Bind signals
Use signal routing so traces, logs, and metrics resolve to the right connector for this environment.
Relation to Database Config and connectors
- Database Config — ClickHouse for this environment (app store + default telemetry). Seeded once from
INIT_DB_*, then managed in the UI. - Connectors — external backends (Tempo, Loki, Prometheus, Jaeger) also carry an environment.
- Signal routing — bindings are unique per project + signal + environment.
Related
Database Config
Env vars → ClickHouse Database Config per environment.
Connectors
Data-source connectors available in OpenLIT.
Signal routing
Bind traces, logs, and metrics per environment.
Projects
Project boundaries that own environments.

