Deploy
Approve with the evidence in front of you. One click ships it, one click brings it back.
A passing build becomes an approval with the evidence attached, and under the Default policy, production waits for a named person who is not the one asking. Approve once, and DeployNX tags, deploys and checks health through the pipeline you already have. Going back is one click too.
- GitHub: Merged to main
- Tests ci.yml › testQueuedRunningPassed
- Deploy to stageWaitingDeployingHealthy
Promote v2.14.0 to prod?
- Test pipeline passed
- Stage healthy
- Tag v2.14.0
- Commit 3f9c2e1
RejectApproveApproved by Ryan- Release to prodWaitingDeployingHealthy
- Tag created
- Deploying
- Health check 200 · 184 ms
- Healthy
- prodpayments-api · GET /healthQueuedChecking…Healthy · 200 · 184 ms
- stagepayments-api · GET /healthQueuedChecking…Healthy · 200 · 212 ms
- Roll back
Deploy: The human gate
Green to prod, through a named person.
Evidence on every approval
A passing test pipeline opens an approval automatically. Each approval shows the test result, stage health, release tag, commit and who asked.
A named approver who isn't the requester
By default, a prod release through DeployNX waits for a named approver who isn't the person who asked for it. Both are Default policy rules that can be switched off, and break-glass skips the approval in an incident.
Tag, deploy, health check
Approve, and DeployNX creates the release tag, runs your production deploy pipeline and checks your health URL. Roll back to any shipped release you choose, with a reason on the record.
Evidence on every approval
A passing test run opens an approval by itself. Green stage builds open promote approvals too: instantly on GitHub through the one-click App, and checked every 30 minutes on Bitbucket, GitLab and GitHub with a token, or right away when you click Check now. Each one carries the test result, stage health, tag, commit and requester, and shows how many policy requirements it meets.
- A passing test pipeline opens an approval automatically.
- Green stage builds open a promote-to-prod approval automatically: instantly on GitHub through the one-click App, and checked every 30 minutes on Bitbucket, GitLab and GitHub repos connected with a token. Check now looks right away.
- Approvals expire, and a newer promote request closes the one it replaces.
Approve from Slack or Google Chat
Approvers get the request in Slack, Google Chat or email, and can decide from Slack or Google Chat with the same checks as the app. Owners and admins approve prod, and the Default policy stops anyone approving their own request.
- By default, a prod release through DeployNX waits for a named approver who isn't the person who asked for it. Both are Default policy rules that can be switched off, and break-glass skips the approval in an incident.
- Owners and admins approve prod. Members request anything and approve stage.
- A decided approval cannot be decided again, and rejecting one needs a reason.
Default policy
Every organization starts with a Default policy that applies on every git host, and you can switch its rules off one by one. Freeze prod before a launch or a holiday. When an incident needs a fix now, break-glass skips the freeze and the approval for up to four hours and leaves a review item.
- Freeze prod now or on a schedule. Held requests become ready after the thaw, and rollbacks stay allowed.
- In an incident, break-glass lets you ship to prod past a freeze and without an approval, for up to four hours. It alerts approvers and leaves a review item for an owner or admin to close.
Tag, deploy, health check
DeployNX creates the release tag, runs your production deploy pipeline and calls your health URL, then records every step on the release timeline. Only one deploy runs per repo and environment, and prod waits for a healthy stage.
- One deploy at a time per repo and environment, and prod waits for a healthy stage.
- On GitHub, DeployNX releases the environment gate as the approver, so the team approves once. The approver must be a required reviewer on the GitHub environment and have authorized the DeployNX GitHub App.
What's live, and is it healthy
See every repo across your organization's environments, in promotion order: the tag that's live, when it shipped, its health and response time. When an environment is behind the one before it, Promote is one click away.
- Your own environments, such as QA, UAT or regional prod, each with a tier, a place in the order and who approves. Every organization starts with Stage and Production, DeployNX proposes more from your CI config, and each repo releases and promotes along the ones it maps (Stage, then Production, when it maps none or auto-detects green stage builds). Freezes, and the healthy-environment and force-completed rules, can be scoped to environments or tiers, and break-glass to one environment.
Roll back to any release
Pick any shipped release, give a reason and confirm. The rollback goes on the record with the reason you gave.
Deploy: Stage by stage
Everything in the Deploy stage
In the order a release meets them, from a green build to a healthy prod.
Detect
From a green build to an open request.
Approvals from green builds
A passing test pipeline opens an approval automatically.
Stage to prod promote
Green stage builds open a promote-to-prod approval.
GitHub, Bitbucket and GitLab
Automatically: instantly on GitHub through the one-click App, and checked every 30 minutes on Bitbucket, GitLab and GitHub repos connected with a token. Check now looks right away.
GitLab stage-build detection
On GitLab, the newest green push pipeline on the default branch opens a promote-to-prod approval automatically, checked every 30 minutes. Check now looks right away.
What it checks
Name its deploy and health jobs and DeployNX checks they passed first. Approving runs your prod pipeline on that branch with REBUILD=false. DeployNX doesn't release GitLab protected-environment approvals.
Evidence
What the approver sees before saying yes.
Evidence on every approval
Each approval shows the test result, stage health, release tag, commit and who asked.
Decide
Who can say yes, and where.
A named approver who isn't the requester
By default, a prod release through DeployNX waits for a named approver who isn't the person who asked for it.
When it doesn't apply
Both are Default policy rules that can be switched off, and break-glass skips the approval in an incident.
Owner, admin and member roles
Owners and admins approve prod. Members request anything and approve stage.
Approve from Slack or Google Chat
Approve or reject from Slack or Google Chat, with the same checks as the app.
Decisions that stick
A decided approval cannot be decided again, and rejecting one needs a reason.
Scutor never approves
Scutor cannot approve anything. It acts only after you click, and every action is logged with your name.
Guardrails
Rules that hold, and a way past them in an incident.
Default policy
Every organization gets a Default policy: one approval, no self-approval, a healthy stage first, and no force-completed runs to prod.
Freeze windows
Freeze prod now or on a schedule. Held requests become ready after the thaw, and rollbacks stay allowed.
Break-glass
In an incident, break-glass lets you ship to prod past a freeze and without an approval, for up to four hours.
What it leaves behind
It alerts approvers and leaves a review item for an owner or admin to close.
Approvals that expire
Approvals expire, and a newer promote request closes the one it replaces.
One deploy at a time
One deploy at a time per repo and environment, and prod waits for a healthy stage.
More policy rules
Approver teams from BizStats Hub, more than one approval per environment, allowed source branches and deploy schedules.
Time-boxed production access
Rollbacks, cancels and manual runs on an environment you protect need a grant that someone else approves and that ends on its own within 8 hours. Approve rights lock for people who stop using them.
Release
Approve once, and DeployNX tags, deploys and checks health. Going back is one click too.
Tag, deploy, health check
Approve, and DeployNX creates the release tag, runs your production deploy pipeline and checks your health URL.
GitHub environments, approved once
On GitHub, DeployNX releases the environment gate as the approver, so the team approves once.
What it needs
The approver must be a required reviewer on the GitHub environment and have authorized the DeployNX GitHub App.
What's live, and is it healthy
Every environment each repo releases through: the tag that's live, its health and response time, and a Promote button when an environment is behind the one before it.
Custom environments
Your own environments, such as QA, UAT or regional prod, each with a tier, a place in the order and who approves.
Routes, freezes and break-glass
Every organization starts with Stage and Production, DeployNX proposes more from your CI config, and each repo releases and promotes along the ones it maps (Stage, then Production, when it maps none or auto-detects green stage builds). Freezes, and the healthy-environment and force-completed rules, can be scoped to environments or tiers, and break-glass to one environment.
Roll back to any release
Roll back to any shipped release you choose, with a reason on the record.
- Dependency graph and impact PlannedA dependency graph of your services, and the impact of a release before you ship it.
Product views on this page are illustrative demo data. Approvals from test runs work on all three providers. Promote approvals from green stage builds open instantly on GitHub with the one-click App; GitHub token connections, Bitbucket and GitLab are checked every 30 minutes, and Check now looks right away. Deploys, rollbacks and cancels work on GitHub, Bitbucket and GitLab. Releasing the GitHub environment gate applies to GitHub only, and needs an approver who is a required reviewer on the environment and has authorized the DeployNX GitHub App. DeployNX doesn't release GitLab protected-environment approvals.


