Manage isolated configurations across dev, staging, and production. Environments are defined at the workspace level — apps point to them rather than owning them. Each environment operates independently with its own variables, deployed releases, and configuration state.
Environments are workspace-level resources that provide isolation for different deployment stages. Apps reference environments rather than defining their own, ensuring consistent environment definitions across your workspace. Instead of deploying directly to production, you work through a promotion chain where each environment has its own configuration, variables, and deployed releases.
Define per-environment secrets and configuration values that are injected into pipeline execution. API keys, feature flags, and connection strings can differ between dev and production without changing your pipeline logic.
Each environment can have a different release deployed. Promote releases through your environment chain — dev, then staging, then production — ensuring each stage is validated before moving forward.
The UI allows selecting environments across the platform. When viewing endpoints, augmentations, and releases, you can filter by environment to see exactly what is deployed and configured in each stage.
If a release causes issues in production, instantly rollback to the previous release for that specific environment. No need to redeploy the entire stack — rollbacks are scoped to individual environments.
Namespace data — threads, sources, memory, and artifacts — can be scoped per environment. This means your dev environment operates on a separate data set from production, preventing test data from leaking into live systems.
Tools support per-environment configuration profiles. A webhook tool can point to a sandbox API in dev and a production API in prod, with different auth credentials and parameters for each environment.
Vault secrets can be scoped per environment. Store separate API keys, credentials, and certificates for each environment so that dev never accidentally uses production secrets.
Releases move through environments in a controlled promotion chain. Each step gives your team confidence that the release is ready for the next stage.