Test freely. Ship safely.
Environments gives every project separate development, staging, preview and production spaces — each with its own variables, secrets, resources and domains.
Included with [plan] · See pricingEach stage gets its own stack.
Switch environments and everything follows: services, databases, caches, storage and domains belong to one environment, so testing in staging never touches production.
The right config in every stage.
See each variable side by side across environments. Override a value for one environment, and keep secrets masked so keys never end up in your code or on screen.
Managing variables →Decide who can touch production.
Limit who can deploy and promote to production. When you need a new environment, clone an existing one and start with its configuration already in place.
Everything each stage needs.
Set up your stages in four steps.
- 01 Create environments Add development, staging, preview and production.
- 02 Set variables and secrets Give each environment its own configuration.
- 03 Attach resources Add databases, storage and a domain per stage.
- 04 Promote to production Ship the release you tested, with controls in place.
Manage environments as code.
Create and clone environments, set variables and secrets, and promote releases from the CLI, the SDKs or the REST API.
How teams use Environments.
Common questions.
Its own variables, secrets, resources and domains, plus the release it is currently running. Environments sit inside a project: Organization → Workspace → Project → Environment → Resource.
Set up your environments.
Create a project with development, staging and production on Stack53 — or talk to us about larger teams.