esc

Integrations

Connect your git host once.

GitHub, Bitbucket and GitLab each connect in one click or with a scoped token. Approvals reach Slack, Google Chat and email. Nothing to install, and your pipelines stay where they are.

Git hostsAvailable today

One click, or a scoped token.

The three hosts connect the same two ways, and runs, deploys and rollbacks work the same on each. DeployNX calls your host's API; nothing runs on your runners.

  • GitHub

    GitHub Actions

    One click
    Install the DeployNX GitHub App on your account or organization.
    Token
    Your own fine-grained or classic personal access token.

    Run workflows, deploy and roll back. Green stage builds open promote approvals automatically: instantly with the one-click App, checked every 30 minutes by default with a token. Check now looks right away. DeployNX releases the environment gate for approvers who are required reviewers and have authorized the DeployNX GitHub App, so they approve once.

    Scopes and setup
  • Bitbucket Cloud

    Bitbucket Pipelines

    One click
    Authorize DeployNX on your Bitbucket Cloud workspace.
    Token
    Your own API token, with your Atlassian email.

    Run pipelines, deploy and roll back. Green stage builds open promote approvals automatically, checked every 30 minutes by default. Check now looks right away.

    Scopes and setup
  • GitLab

    GitLab CI/CD

    One click
    Authorize DeployNX on GitLab.com, or on your self-managed instance with your own GitLab application.
    Token
    Your own personal access token, on GitLab.com or your self-managed instance.

    Run pipelines, deploy and roll back. Green stage builds open promote approvals automatically, checked every 30 minutes by default. Check now looks right away.

    Scopes and setup

Tokens are encrypted at rest. One-click connections refresh their own access; pasted tokens get a warning before they expire.

CompareHost by host

What each provider supports.

Every row works on all three today, except where a cell says otherwise.

What GitHub, Bitbucket Cloud and GitLab each support in DeployNX.
CapabilityGitHubGitHub ActionsBitbucketBitbucket PipelinesGitLabGitLab CI/CD
Connect
Connect in one clickSupportedSupportedSupported
Connect with a scoped tokenSupportedSupportedSupported
Repository and branch syncSupportedSupportedSupported
Verify
Pipelines found from the CI fileSupportedSupportedSupported
Trigger test runsSupportedSupportedSupported
Pipeline runs on demandSupportedSupportedSupported
Live step status and logsSupportedSupportedSupported
Deploy
Deploy, roll back and cancelSupportedSupportedSupported
Promote approvals from green stage buildsSupportedInstant with the one-click App; every 30 minutes with a tokenSupportedAutomatic, every 30 minutes, or right away with Check nowSupportedAutomatic, every 30 minutes, or right away with Check now
Environment gate released for youSupportedApprover is a required reviewer and has authorized the AppNot applicableNot applicableProtected-environment approvals stay in GitLab

NotifyChat, email and sign-in

Approve where your team already talks.

Approval requests, failures and release updates go to Slack, Google Chat and email. Approve or reject right there, with the same checks as the app.

The approval must still be pending and your role must allow it, nobody approves their own production request, and rejecting needs a reason.

On every channel

  • Choose which events it gets
  • Narrow it to some repositories or environments
  • Check its delivery log, or send a test
  • Slack

    Install the DeployNX app in your workspace

    Approval requests arrive as cards with Approve and Reject buttons, and run and release updates land in the channels you pick.

    • Approve or reject with the same checks as the app
    • Link your Slack account so your click counts as yours
    • Or post updates to any channel through an incoming webhook
    How it works
  • Google Chat

    Add the DeployNX app to a space

    The same approval cards and updates in a Google Chat space. Add the app, then confirm the link it posts there.

    • Approve or reject with the same checks as the app
    • Link your Google Chat account so your click counts as yours
    • Or post updates to a space through an incoming webhook
    How it works
  • Email

    Nothing to install

    Approval, failure and release emails, to each person and to the team lists you add.

    • A team list is a channel, with its own events
    • Each person sets their own email preferences
    How it works
  • BizStats Hub sign-in

    One account for DeployNX and other BizStats products

    Sign in with your Hub account, or create one with any of these.

    • Google
    • GitHub
    • Microsoft
    • Apple
    • LinkedIn
    • Email
    • OpenID Connect with PKCE, and no DeployNX passwords
    • Owner, admin and member roles for your organization
    How it works

Your own tools

  • Outbound webhooks. Signed release, approval, test run and freeze events, posted to your own HTTPS endpoints, with retries, a delivery log and redeliver.
  • API tokens. Scoped, expiring tokens for CI scripts that read, request promotions or start test runs, each acting as the person who created it.
How webhooks and API tokens work

Coming soonPlanned, not built yet

Next on the list.

More code hosts and CI systems are planned. Tell us which one you need and we'll count it.

Code hosts

Repositories and their built-in CI.

CI and CD

Systems that run beside your code host.

Each one is on the roadmap, with no date until it ships.

Connect your first repository.

Need a host or CI that isn't listed? Tell us.