Deploys, updates, and rollback
A deployment creates a new version without replacing the working version until the new one is ready. The pipeline makes each stage visible, blocks known configuration problems, and keeps successful versions available for rollback.
Last updated
AI agent? Start with llms.txt.
The pipeline moves from code to a running version
The Service page shows four phases.
- Code records the source submitted by paste, git push, or GitHub.
- Review detects what changed and surfaces decisions such as missing environment values or database choices.
- Build prepares the new version and checks that the application can be assembled.
- Go Live starts the version, runs its release work, and makes it active after the required checks pass.
Builds can start while review decisions are still open. This lets you resolve a missing value without waiting to begin the build afterward.
Web apps switch traffic after health checks
A web app's new version starts beside the current version. Tokay sends it health checks before any visitor traffic.
When the checks pass, traffic moves to the new version. When they fail, the current version keeps serving and the failed deployment records a diagnosis and boot output. Visitors do not see an unhealthy version take over.
Blockers stop predictable failures early
Tokay blocks deployment when a required environment variable has no value, two sources conflict, or a database choice needs confirmation. The Service page names the required action.
These decisions can be resolved while the build runs. The deploy continues from the same prepared version after the blocker is cleared.
Auto-deploy belongs to the Project
A Project can deploy affected Services automatically after a push or wait for a person to choose Update. This supports a staging Project that follows every commit and a production Project that uses the same repository but waits for approval.
Only Services whose source changed are considered for deployment.
History connects a release to its code
The Deployments tab shows every deployment with its time, commit, summary, result, and whether it required a full build. Current marks the deployment the Service runs now. Show diff displays the code changes between versions.
A changed value or a resume redeploys the same build, so several deployments can share one commit.
Rollback is another health checked deployment
Choose Restore this version on a previous successful deployment. Tokay creates a new deployment from that version and uses the normal Go Live checks before it takes over.
A rollback runs no migrations, because that version's migrations already ran when it was live. When a release since then changed the database in a way the older code may not handle, the restore dialog lists those changes first. Choose Keep current data, or, while the restore point is still kept, Restore data too to put the database back as it was before those changes. Restoring loses anything written since.
The Service stays on the version you restored. Auto-deploy waits for your next push, and pausing and resuming keep the rollback in place. Deploying the Service again moves it forward to the newest code.
Rollback restores code and build output. It does not restore old Project Config, Secret, or managed resource values because current runtime settings and credentials should stay current. Some very old versions can expire, and the restore dialog explains when a version is no longer available.