esc

Verify. Deploy. Grow.

Your GitHub, Bitbucket and GitLab pipelines in one release control room.

And ship to production with a person in the loop.

By default, nothing ships to prod until a named person says yes.

Works with
  • GitHub
  • Bitbucket
  • GitLab
  • Slack
  • Google Chat
  • BizStats Hub SSO

Before DeployNX

Your path to production lives in three tools and one person's head.

Approvals happen in DMs.

"Ship it?" "Yep." Six months later, nobody can show who approved the release that took checkout down.

Every git host gates prod its own way.

GitHub environments, Bitbucket deployment permissions, GitLab protected environments: three settings pages, three audit trails, and none of them sees the other two.

Rollback is pipeline archaeology.

At 2 a.m. someone hunts for the last good tag and the right pipeline to re-run while the incident channel waits.

Follow one release: payments-api · v2.14.0 · 3f9c2e1 · Illustrative

On top of your CI

One path to production, whichever git host your repos live on.

Keep your pipelines. DeployNX sits on top of the CI you already run and adds the approval, the release record and the rollback button around it.

Connect once.

Connect GitHub, Bitbucket or GitLab in one click, or with a scoped access token. Nothing to install. Git provider tokens are encrypted at rest, and OAuth tokens refresh on their own.

Pipelines found for you

DeployNX reads your CI file, finds the test, stage and production pipelines, and asks you to confirm them. Your deploy scripts stay where they are.

.github/workflows/deploy.yml
name: deployon:  push:    branches: [main]  workflow_dispatch: jobs:  test:Annotation: test pipeline    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - run: make test   deploy-stage:Annotation: stage deploy · green builds reported by the App    needs: test    environment: stage    runs-on: ubuntu-latest    steps:      - run: ./scripts/deploy.sh stage   deploy-prod:Annotation: production deploy · runs on approval    needs: deploy-stage    environment: productionAnnotation: gate released by DeployNX on approve    runs-on: ubuntu-latest    steps:      - run: ./scripts/deploy.sh prod

Examples are illustrative. Deploys started directly in your CI skip DeployNX: make DeployNX the only path to prod

GitHub, Bitbucket, GitLab. One queue.

DeployNX works with GitHub Actions, Bitbucket Pipelines and GitLab CI today. Runs, releases and rollbacks from each of them land in one list, in the same words.

More git providers are on the way. Planned

Verify: The test gates

Run the test pipelines you already have, and see why they fail.

Test runs on every host

Trigger test pipelines in GitHub Actions, Bitbucket Pipelines and GitLab CI from one place.

Live step status

Step status updates as your pipeline moves. No refresh button. Every step's log is one click away, GitHub Actions included.

Scutor explains failures

Scutor reads a failed run's steps and logs and tells you which step broke and why. If it offers to re-run something, it waits for your click.

Pipeline runs

Run migrations, smoke suites and other non-deploy pipelines on demand. Stage and prod pipelines always go through approval.

  • Test health Steps marked flaky or broken from same-commit retries, ranked by the releases they block.
  • Per-test results and quarantine Every test with its flaky score and history, from the JUnit XML your pipelines upload and the failures in each run's logs. Quarantine a flaky test so a run that fails only on it counts as passed.

Deploy: Stage

Stage goes green. Prod gets asked.

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.

Green stage builds ask for prod

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.

One deploy at a time

One deploy at a time per repo and environment, and prod waits for a healthy stage.

Deploy: The human gate

A passing build becomes an approval with the evidence attached.

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.

Illustrative example

  • Test pipeline passed
  • Stage healthy 212 ms
  • Tag v2.14.0
  • Commit 3f9c2e1
  • Requested by auto

It opens for a named person.By default, never the one who asked.

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.

Approve from Slack or Google Chat

Approve or reject from Slack or Google Chat, with the same checks as the app. Slack, Google Chat and email notifications, routed per organization, with a delivery log and a test send.

Scutor never approves

Scutor cannot approve anything. It acts only after you click, and every action is logged with your name.

  • By default, the requester can't approve their own prod request.
  • By default, a named approver decides: in this example, Ryan.
  • Scutor can't approve anything.

Deploy: Rules that hold

Least privilege for production, not standing access.

By default, a prod release through DeployNX waits for a named approver who isn't the requester, and leaves a record. The Default policy, freeze windows and break-glass work the same way on every git host.

Default policy

Every organization gets a Default policy: one approval, no self-approval, a healthy stage first, and no force-completed runs to prod.

  • One approval
  • No self-approval
  • A healthy stage first
  • No force-completed runs to prod
  • Step-up re-auth Planned
  • Release policy as code Planned

Approvals that expire

Approvals expire, and a newer promote request closes the one it replaces.

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. It alerts approvers and leaves a review item for an owner or admin to close.

Deploy: Release

Approve, and it ships.

Decisions that stick

In this example, Ryan approves at 14:02. A decided approval cannot be decided again, and rejecting one needs a reason.

Tag, deploy, health check

Approve, and DeployNX creates the release tag, runs your production deploy pipeline and checks your health URL. DeployNX doesn't run your deploys; your CI does.

GitHub environments, approved once

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.

GitHub only

Live, and healthy

The tag that's live, its health and response time. In this example: v2.14.0 on prod, 200 in 184 ms.

Deploy: Roll back

One click back, to any release you shipped.

Roll back to any release

Roll back to any shipped release you choose, with a reason on the record.

Allowed even in a freeze

Rollbacks stay allowed during a freeze.

Not pipeline archaeology

Rollbacks are one click, not pipeline archaeology.

Grow: The record

Know who shipped what and on whose approval, and use that record to ship better.

Answer "who shipped this, and who said yes?" in seconds, and hand auditors an export instead of screenshots. The same record shows the team where to ship better.

Audit log with export

An audit log of every change, with before and after, filters, and CSV or JSON export.

One activity timeline

Runs, approvals, releases and Scutor actions on one timeline, filterable by person and repo.

CI insights

Pass rate without cancelled runs, p50 and p95 duration, time to green and the steps that fail most. Every point opens the runs behind it.

Delivery metrics

Deploy frequency, lead time, change-failure rate and time to restore, each shown with how it is calculated.

Compared

How DeployNX fits next to the tools you know.

DeployNX sits on top of the CI you already run. Here is how its release controls line up with each tool's own, from their public docs as of September 2026.

  • One queue, every git host

    One approval queue for GitHub, Bitbucket and GitLab, while your pipelines stay where they are.

  • Decide in chat

    Approve or reject from Slack or Google Chat, with the same checks as the app.

  • Evidence on every approval

    Every prod approval shows its evidence: tests on that commit, stage health, release tag and who asked.

  • Roll back, with the reason

    Roll back to any release you shipped, with the reason on the record.

Release controls in DeployNX and six CI/CD tools, from each vendor's public documentation as of September 2026. Each cell opens a note with its source.
CapabilityDeployNXOn top of your existing CIGitHub ActionsEnvironments + deployment protection rulesGitLab CI/CDProtected environments, approvals, deploy freezesBitbucket PipelinesDeployments + deployment permissionsJenkinsCore + official pluginsHarness CDContinuous Delivery moduleOctopus DeployCloud or self-hosted
One queue across git hostsOne approval policy and queue across GitHub, Bitbucket and GitLab repos at once

DeployNX · One queue across git hosts

Yes

Repos on all three hosts share one approvals inbox and one org policy.

Plan: Staging for two hosts, Production or higher for all three,

Available in DeployNX today.

GitHub Actions · One queue across git hosts

No

Environments govern GitHub Actions workflows in GitHub repositories.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · One queue across git hosts

Partial

By running GitLab CI/CD for mirrored GitHub or Bitbucket Cloud repos (Premium/Ultimate).

Plan: Premium or Ultimate

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · One queue across git hosts

Partial

Not in Pipelines itself; Atlassian's separate Jira Service Management Premium adds deployment gating for Bitbucket, GitHub, GitLab and Jenkins.

Plan: Jira Service Management Premium (a separate Atlassian product)

Source: support.atlassian.com (opens in a new tab)

Jenkins · One queue across git hosts

Partial

Builds repos from all three hosts (branch source plugins); approvals are per-pipeline input steps, no central policy.

Source: jenkins.io (opens in a new tab)

Harness CD · One queue across git hosts

Yes

Git connectors for GitHub, GitLab and Bitbucket; approvals live in Harness pipelines.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · One queue across git hosts

Yes

Any CI hands releases to Octopus (GitHub Actions, Bitbucket Pipelines, Jenkins; CLI elsewhere); one 'Needs Approval' list.

Source: octopus.com (opens in a new tab)

Keeps your existing pipelinesWorks on top of your existing CI pipelines, with no migration of pipeline definitions

DeployNX · Keeps your existing pipelines

Yes

Reads your CI file and runs your own test, stage and prod pipelines. On GitHub, prod still passes your environment's required reviewers.

Available in DeployNX today.

GitHub Actions · Keeps your existing pipelines

Yes

Native: add environment rules to existing GitHub Actions workflows (for GitHub Actions).

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Keeps your existing pipelines

Yes

Native: protected environments and approvals on existing GitLab CI/CD jobs (for GitLab CI).

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Keeps your existing pipelines

Yes

Native: deployment environments on existing Pipelines steps (for Bitbucket Pipelines).

Source: support.atlassian.com (opens in a new tab)

Jenkins · Keeps your existing pipelines

Yes

Native: input steps go in your existing Jenkinsfile (for Jenkins jobs).

Source: jenkins.io (opens in a new tab)

Harness CD · Keeps your existing pipelines

Partial

Deploys are modeled as Harness pipelines; existing Jenkins jobs can be called from a CD stage.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Keeps your existing pipelines

Partial

Your CI keeps building; the deployment process is defined and run in Octopus.

Source: octopus.com (opens in a new tab)

Named prod approver, no self-approvalNamed approver required for prod, with self-approval blocked

DeployNX · Named prod approver, no self-approval

Yes

Default policy: owners/admins approve prod, never their own request. Rules can be switched off; break-glass skips approval.

Available in DeployNX today.

GitHub Actions · Named prod approver, no self-approval

Yes

Required reviewers + 'Prevent self-review'. Private repos need GitHub Enterprise; admins can bypass unless disabled.

Plan: GitHub Enterprise for private repositories

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Named prod approver, no self-approval

Yes

Deployment approvals (Premium/Ultimate); the pipeline triggerer cannot approve unless allowed.

Plan: Premium or Ultimate

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Named prod approver, no self-approval

Partial

Deployment permissions (Premium) limit who can run a deploy step; no separate approver or self-approval block documented.

Plan: Premium

Source: support.atlassian.com (opens in a new tab)

Jenkins · Named prod approver, no self-approval

Partial

Input step 'submitter' names approvers; blocking the build's starter isn't built in, and Jenkins admins can always respond.

Source: jenkins.io (opens in a new tab)

Harness CD · Named prod approver, no self-approval

Yes

Approval step with user groups and a minimum count; 'Disallow the executor' (manual runs) and 'Disallowed User Emails'.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Named prod approver, no self-approval

Partial

Manual intervention limited to responsible teams; blocking the deployer from approving isn't documented.

Source: octopus.com (opens in a new tab)

Evidence on the approvalApproval request carries evidence (tests passed on that commit, stage healthy) at decision time

DeployNX · Evidence on the approval

Yes

Each approval shows the test result, stage health, release tag, commit and who asked.

Available in DeployNX today.

GitHub Actions · Evidence on the approval

Partial

Reviewer approves from the workflow run (earlier jobs visible); custom protection rules can gate on external checks.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Evidence on the approval

Partial

Approval view shows eligible approvers, count and history; pipeline results are in the same pipeline.

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Evidence on the approval

Partial

Promote preview shows commits, file changes and linked Jira issues.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Evidence on the approval

Partial

Input step shows the message the pipeline author writes; stage results are on the build.

Source: jenkins.io (opens in a new tab)

Harness CD · Evidence on the approval

Yes

'Include stage execution details in approval' gives approvers the execution history.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Evidence on the approval

Partial

Approver sees the step's instructions and the release, including lifecycle phases already deployed.

Source: octopus.com (opens in a new tab)

Approve from Slack or Google ChatApprove or reject from Slack / Google Chat, with the same guards (role, no self-approval, reason on reject)

DeployNX · Approve from Slack or Google Chat

Yes

Slack and Google Chat buttons with the app checks: the request must still be pending, the role must allow it, no self-approval, a reason on reject.

Plan: Staging or higher

Available in DeployNX today.

GitHub Actions · Approve from Slack or Google Chat

Partial

Approve deployments from Slack or Microsoft Teams via the GitHub app; no Google Chat.

Source: github.com (opens in a new tab)

GitLab CI/CD · Approve from Slack or Google Chat

No

Not documented: approvals are in the GitLab UI or API; the Slack app sends deployment notifications.

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Approve from Slack or Google Chat

No

Pipelines has no approval step; the Slack app sends deployment notifications and re-runs failed pipelines.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Approve from Slack or Google Chat

No

The Slack Notification plugin sends messages; input steps are answered in Jenkins.

Source: plugins.jenkins.io (opens in a new tab)

Harness CD · Approve from Slack or Google Chat

Partial

Approval-required notifications to Slack, Microsoft Teams or email link to the approval in Harness.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Approve from Slack or Google Chat

Partial

Slack integration (Server 2026.3+) posts notifications; manual interventions are approved in Octopus.

Source: octopus.com (opens in a new tab)

Green stage opens a prod requestA green stage build automatically opens a prod promote request

DeployNX · Green stage opens a prod request

Yes

GitHub App: instant. Otherwise checked every 30 minutes, or right away with 'Check now'.

Plan: Staging or higher

Available in DeployNX today.

GitHub Actions · Green stage opens a prod request

Yes

A prod job with required reviewers waits for review once the stage job in the same workflow passes.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Green stage opens a prod request

Yes

A prod job in a protected environment waits for approval after the stage job (approvals Premium+).

Plan: Approvals need Premium or higher

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Green stage opens a prod request

Yes

Manual deployment steps show a Promote button once earlier steps pass.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Green stage opens a prod request

Yes

An input step after the stage deploy pauses the pipeline for approval.

Source: jenkins.io (opens in a new tab)

Harness CD · Green stage opens a prod request

Yes

Approval stage or step between the stage and prod deploys.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Green stage opens a prod request

Yes

Lifecycle phases can deploy automatically; a manual intervention step makes that a pending approval.

Source: octopus.com (opens in a new tab)

Freeze windows and break-glassFreeze windows (deploy freezes) + a break-glass bypass with an audit/review trail

DeployNX · Freeze windows and break-glass

Yes

Freeze now or on a schedule; break-glass (up to 4 hours) alerts approvers and leaves a review item.

Plan: Production or higher

Available in DeployNX today.

GitHub Actions · Freeze windows and break-glass

Partial

No built-in freeze window; custom protection rules can block deploys; admins can bypass rules with a comment.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Freeze windows and break-glass

Partial

Deploy freezes on all tiers, enforced with $CI_DEPLOY_FREEZE job rules; no dedicated break-glass flow documented.

Plan: Every tier

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Freeze windows and break-glass

Unclear

No freeze setting documented for Pipelines; whether Jira Service Management change windows block Bitbucket deploys isn't stated.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Freeze windows and break-glass

Partial

Working Hours plugin holds builds outside allowed times or on excluded dates, with a manual 'Release job' override.

Plan: With the Working Hours plugin

Source: plugins.jenkins.io (opens in a new tab)

Harness CD · Freeze windows and break-glass

Yes

Scheduled and recurring freeze windows; Override permission for chosen users; freeze bypass is an audit action.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Freeze windows and break-glass

Yes

Scheduled and recurring freezes; override needs DeploymentFreezeAdminister; multi-project freezes need Enterprise.

Plan: Multi-project freezes need Enterprise

Source: octopus.com (opens in a new tab)

Roll back to any release, with a reasonOne-click rollback to any previously shipped release, with a reason recorded

DeployNX · Roll back to any release, with a reason

Yes

Roll back to any shipped release you choose, with a reason on the record.

Available in DeployNX today.

GitHub Actions · Roll back to any release, with a reason

Partial

No rollback action; re-run an earlier workflow run (same commit) within 30 days.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Roll back to any release, with a reason

Partial

'Rollback environment' to any earlier successful deployment (all tiers); no rollback reason field documented.

Plan: Every tier

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Roll back to any release, with a reason

Partial

Redeploy a previous successful deployment from the Deployments dashboard while its artifacts exist; no rollback reason documented.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Roll back to any release, with a reason

Partial

Restart an earlier Declarative Pipeline run from a stage with the same SCM inputs; no rollback reason.

Source: jenkins.io (opens in a new tab)

Harness CD · Roll back to any release, with a reason

Partial

One-click post-deployment rollback to the most recent successful deployment (supported types, 30 days).

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Roll back to any release, with a reason

Yes

Redeploy any retained earlier release; 'Prevent progression' records a reason against the bad release.

Source: octopus.com (opens in a new tab)

Exportable audit logAudit log of approvals/deploys exportable (CSV/JSON), across providers

DeployNX · Exportable audit log

Yes

Every change with before/after, filters, and CSV or JSON export, for all connected hosts.

Plan: Hyperscale

Available in DeployNX today.

GitHub Actions · Exportable audit log

Partial

Org audit log records deployment approvals and rejections; JSON or CSV export (180 days); for GitHub.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Exportable audit log

Partial

Deployment approved/rejected audit events (Premium+); CSV export on Self-Managed; for GitLab.

Plan: Premium or higher

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Exportable audit log

Partial

Deployment history per repo on the dashboard; deployment events not listed for the workspace audit log.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Exportable audit log

Partial

Audit Trail plugin logs to file, syslog or Elasticsearch; no CSV/JSON export documented.

Plan: With the Audit Trail plugin

Source: plugins.jenkins.io (opens in a new tab)

Harness CD · Exportable audit log

Yes

Audit Trail (2-year retention; pipeline execution events opt-in); JSON streaming to S3, GCS or a SIEM.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Exportable audit log

Yes

Audit log of every change and deployment queued; JSONL archives via download or REST API; SIEM streaming on Enterprise.

Plan: SIEM streaming needs Enterprise

Source: octopus.com (opens in a new tab)

Approvals expire and supersedeApprovals expire, and a newer request supersedes an older one

DeployNX · Approvals expire and supersede

Yes

Approvals expire, and a newer promote request closes the one it replaces.

Available in DeployNX today.

GitHub Actions · Approvals expire and supersede

Partial

Waiting jobs fail after 30 days (fixed); concurrency groups cancel older pending runs; superseding a run already awaiting review isn't documented.

Source: docs.github.com (opens in a new tab)

GitLab CI/CD · Approvals expire and supersede

Partial

'Prevent outdated deployment jobs' (all tiers) stops older deploy jobs; no approval expiry documented.

Plan: Every tier

Source: docs.gitlab.com (opens in a new tab)

Bitbucket Pipelines · Approvals expire and supersede

Unclear

Concurrency control pauses later deploys; expiry of waiting manual steps isn't documented.

Source: support.atlassian.com (opens in a new tab)

Jenkins · Approvals expire and supersede

Yes

Via plugins: a timeout step around input, and the Milestone step aborts older builds once a newer one passes.

Plan: With the plugins named

Source: jenkins.io (opens in a new tab)

Harness CD · Approvals expire and supersede

Yes

Approval timeout (default 1 day) and 'Auto-reject previous deployments in approval'.

Source: developer.harness.io (opens in a new tab)

Octopus Deploy · Approvals expire and supersede

Unclear

No expiry or supersede for pending manual interventions found in the docs.

Source: octopus.com (opens in a new tab)

Based on each vendor's public documentation as of September 2026. Features vary by plan. Trademarks belong to their owners. GitHub: required reviewers, wait timers and custom deployment protection rules in private repositories need GitHub Enterprise (on Free, Pro and Team, public repositories). GitLab: protected environments, deployment approvals and CI/CD for external repositories need Premium or Ultimate; deploy freezes are on every tier. Bitbucket: deployment permissions need Premium; Jira Service Management deployment gating is a separate Atlassian product (Premium). Jenkins: rows assume the plugins named. Harness and Octopus: features vary by edition; Octopus multi-project freezes and audit streaming need Enterprise. DeployNX items marked Planned are not available yet.

Next on the line

Planned, and marked that way.

  1. Step-up re-auth Planned

    A fresh sign-in before anyone approves or ships to production.

  2. Dependency graph and impact Planned

    A dependency graph of your services, and the impact of a release before you ship it.

  3. More code hosts and CI systems Planned

    Azure DevOps Services, GitHub Enterprise Server, Bitbucket Data Center, Azure DevOps Server, Gitea and Forgejo, Gitee, Gerrit, Jenkins, CircleCI, Buildkite, TeamCity and Argo CD.

From sign-in to your first approved release.

No agents, runners or pipeline rewrites.

  1. Step 1: Sign in

    Use your BizStats Hub account, or create one.

  2. Step 2: Connect

    Add GitHub, Bitbucket or GitLab in one click or with a scoped token, and pick your repos.

  3. Step 3: Map

    Confirm the test, stage and prod pipelines DeployNX found in your CI file. Add health URLs.

Ship

  1. Step 4: Verify

    Run your tests from DeployNX and watch each step as it runs.

    Everything in Verify
  2. Step 5: Deploy

    Approve your first release to prod. Roll it back in one click if it isn't healthy.

    Everything in Deploy
  3. Step 6: Grow

    Scutor explains failed runs; the activity timeline and audit log keep the record, and CI insights show where to improve.

    Everything in Grow

Security and access

Read the security overview
  • Records only your organization can see
  • Encrypted database backups
  • Invite teammates and choose their role

A strong fit when

  • Two or more repos already deploy through CI
  • You use more than one git host
  • Someone must be named as the approver for prod
  • You have stage and prod environments with health URLs

Not the best fit when

  • You want a CD engine to replace your pipelines
  • You run pure GitOps sync on Kubernetes
  • You need 24/7 synthetic monitoring

DeployNX doesn't replace your CI runners, your deploy scripts or your monitoring. It works alongside them.

Put a named person between green and prod.

Start free on Localhost, no card needed. Connect a repo, confirm its pipelines and ship your first approved release.

ConnectGitHub,Bitbucket orGitLab

One click or a scoped token. Nothing to install.

By default, nothing ships from stage to prod until a named person says yes.

DeployNX grew out of the release tool BizStats built to ship its own services.