Three environments. Production when you say so.
The agents work in dev. You check the app on test, which runs like production. Production stays off until an owner of your organization turns it on — and the platform enforces that, not just the agents' instructions.
Control that does not slow the team down
The agents prepare everything; the decisions that cannot be taken back stay with people.
Three environments in every project
Dev is the agents' workspace. Test and production run on the same kind of infrastructure, each with its own data and keys.
A person presses Deploy
Agents prepare releases. Nothing is deployed, not even to test, until someone in your organization presses Deploy.
Production needs an owner
Production stays off until an organization owner turns it on for the project. Until then, the platform refuses the agents.
What you tested is what goes live
Only a release that ran on test can be promoted to production: the same build, not a rebuild.
Releases checked for leaked keys
Before a release is deployed, its code is scanned for keys it could leak, and you see what was found.
Test and production keys stay hidden
Values stored for test and production are never shown to the agents, or to anyone else.
From a release to production
Five steps, and two of them are a person pressing a button.
DevOps prepares a release
The platform cuts a tagged release, scans it and builds it once.
A person deploys it to test
The platform migrates the database, publishes the release and checks that it answers.
You check it on test
The app and its environment as production will run them, at the test address.
An owner turns production on
Once for the project. Until then, an agent that tries production gets a refusal.
You promote the release
The build that ran on test goes to production. If a production deploy fails, the code goes back to the previous release.
What an agent gets without the grant
Production is enforced by the platform, not just by the agents' instructions. An agent that tries production before an owner has turned it on is refused:
403 PRODUCTION_NOT_AUTHORIZED
Production is not enabled for project 7f3c2a91. A human must enable production access from the dashboard before production resources can be provisioned. Deploy to `test` instead.Good to know
- Database changes are not undone when a production deploy fails: the code goes back to the previous release, and the data stays as it is.
Ready to build?
Describe your first app. The agents take it from there, and production waits for you.