esc

Security

Built to hold the keys to production.

DeployNX can run your production pipelines, so it is built to need as little access as possible and to record everything it does. This page says what it does today, not what it might do later.

Last updated 2026-10-01.

How DeployNX connects to your code

You connect GitHub, Bitbucket or GitLab in one of two ways: one click (the DeployNX GitHub App, or Bitbucket and GitLab OAuth), or a scoped access token you create yourself. Nothing is installed on your runners or servers. DeployNX calls your provider's API to read repositories and pipelines, start the runs you ask for, and read their results.

Before a token is saved, DeployNX checks it and shows which permissions it has and which are missing. When you connect GitHub in one click, DeployNX first confirms that you can see the installation you are linking, so an installation can't be claimed by someone else. See Connecting providers for the exact scopes.

URLs you give DeployNX, such as health URLs and self-managed GitLab addresses, are only called if they resolve to public addresses. Private, loopback, link-local and cluster addresses are refused.

Your organization, and only yours

Every repository, run, approval, release, audit event and notification belongs to exactly one organization. Requests, live updates and Scutor tools are all scoped to the organization you are signed in to. An automated test suite checks every API route, live-update topic and Scutor tool to make sure one organization can't see another's data.

Encryption

  • In transit: all traffic to DeployNX uses TLS.
  • Git provider tokens at rest: access and refresh tokens are encrypted in the database. The encryption key is kept in our secrets vault, not in the database.
  • Backups: encrypted before they are stored. The key that decrypts them is kept in our secrets vault, not in the cluster, and is supplied only to restore jobs.

Backups

We take encrypted database backups by hand when they are needed, and restore them by hand. Nothing backs up on a schedule or during a deploy.

New backups are kept for 14 days; older ones expire within 12 months.

Sign-in and roles

You sign in with your BizStats Hub account using OpenID Connect with PKCE. DeployNX verifies the Hub's signed ID token against the Hub's published keys before it creates a session. There are no DeployNX passwords.

Each person has one role in their organization. Owners and admins can approve production; members can request anything and approve stage. By default, nobody can approve their own production request. Live updates require a signed-in session.

Scutor and your data

  • Scutor sees only what you can already see in your organization: runs, steps, logs, approvals and releases.
  • Scutor can't approve anything. Every action it proposes waits for your click, and each confirmed action is recorded as "Scutor on behalf of" you in the audit log.
  • By default, Scutor's language model runs on infrastructure BizStats operates, so your prompts and run data are not sent to a third-party AI provider. If a hosted model provider is ever enabled, it will be listed below first.
  • Each organization has a request quota for Scutor.
  • Scutor can be wrong. It links the evidence it used so you can check.

What we store

  • Your name and email from the BizStats Hub, your organization, its members and their roles.
  • Connected providers, with tokens encrypted as described above.
  • Repository names, branches, CI configuration and the pipelines you confirmed.
  • Run, step and log data needed to show and diagnose runs.
  • Approvals, releases, rollbacks, policies, freezes and the audit log.
  • Scutor conversations and the actions you confirmed.
  • Notification settings and the delivery log.

Where it runs, and who else is involved

DeployNX runs on Kubernetes infrastructure operated by BizStats. These services are involved in running it:

ServiceWhat for
BizStats infrastructureHosting the app, database and backups
CloudflareDNS and the encrypted tunnel that carries traffic to DeployNX
BizStats HubSign-in
BizStats email serviceSending notification emails
Google AnalyticsVisit statistics for this site and the app, only after you accept cookies

Git providers, Slack and Google Chat receive data only when you connect them, and only what each integration needs.

This website

The marketing site loads Google Analytics only after you accept cookies; until then it loads no third-party scripts and sets no tracking cookies. Fonts are served from our own domain, and a strict Content Security Policy allows Google's analytics hosts and blocks anything else. Our web server keeps standard access logs.

Compliance

DeployNX has no third-party security attestation yet. We will publish attestations here once an audit is complete. In the meantime, the audit log and its export are designed to give your own auditors the evidence change-management controls ask for.

Report a vulnerability

Email security@bizstats.ai with the details and steps to reproduce. Please give us a reasonable time to fix the issue before you share it publicly.