# One click to live, through the security check

> A builder sends a tool to Substrait with one command, through their AI model, and goes live with one click. Substrait promotes the exact build tested in dev to production, only through the security check.

URL: https://substrait.build/capabilities/one-command-go-live/  
Last updated: 2026-11-06

A builder runs one command, through their AI model, and the tool is live in dev, behind your organisation's sign-in. One click takes it to production, promoting the exact build that was tested, through the security check, with rollback if anything goes wrong.

## How it works

**A deploy is an act, never a side effect.**
A tool reaches Substrait only because someone ran the deploy command.
Source arrives either from the builder's own GitHub repository or as a stored snapshot, with no git host at all.

**Dev first.**
Every new tool starts in dev, behind sign-in for your organisation.
The builder cannot switch that sign-in off; turning it off in dev needs a written reason and an operator's approval.

**Production comes last.**
Production does not exist until the builder goes live.
Going live is one click, and it promotes the build already tested in dev, with no rebuild.
Later deploys keep landing in dev until the next promotion.

**Promotion is the only way into production.**
Every promotion runs the security check on that exact build.
A build within your policy is promoted automatically.
A build with too many issues stops for a human approver.

**Versions and rollback.**
Every release is versioned.
A bad release rolls back to the last good version in one click.

**Each environment is separate.**
Dev and production each have their own database, file storage, settings and address.

## Questions and answers

### Does a git push deploy a tool on Substrait?

No. On Substrait a deploy is an act. A tool changes only when someone runs the deploy command. A push to the builder's repository does not touch the running tool.

### How many environments does a tool have?

Two: dev and production. Every new tool starts in dev. Production exists only once the builder goes live.

## Related

- [A security check before every release reaches production](https://substrait.build/capabilities/security-check/): Substrait scans every release for leaked secrets, weak code, vulnerable dependencies, container issues and problems in the running tool. A tool reaches production only through a promotion that clears the check.
- [How to put a tool built with AI into production](https://substrait.build/problems/put-an-ai-built-prototype-into-production/): A tool built with Claude Code or Cursor works on a laptop. Substrait takes it to production with one command: dev behind sign-in first, then promotion through a security check, with rollback.
- [Nothing breaks quietly](https://substrait.build/capabilities/monitoring-and-alerts/): Substrait watches every tool it runs: crash detection, startup checks and request-level monitoring, with alerts to the builder and the owner about build questions, scan results and release status.
- [On Substrait's cloud, or inside yours](https://substrait.build/capabilities/your-own-cloud/): Start on a standard setup on Substrait's cloud with nothing to install, or run Substrait in your own cloud account or data centre. In your environment, the whole tool and its data stay inside your perimeter.