How to put a tool built with AI into production

Why this is hard

“Just deploy it” sounds like one step. Underneath it are a dozen specialist steps: packaging the tool, private networking, a secrets vault, least-privilege access, a private path to company systems, a deploy and rollback pipeline, logging, sign-on and data residency. Each step needs platform and security skills that most builders, and many IT teams, do not have.

What Substrait does

One command, through the builder’s AI model. The Substrait plugin checks the project, packs the code and tells Substrait to build it.
Dev first, behind sign-in. Every new tool starts in dev, open only to your organisation. The builder cannot switch that sign-in off.
Going live creates production. Substrait promotes the build that was tested in dev, without rebuilding it.
The security check runs on that exact build. A clean build is promoted automatically. A build with too many issues stops for a human approver.
Rollback in one click. Every release is versioned, and a bad release rolls back to the last good one.

Substrait plugin: what happens when a builder runs the deploy command, from checking the project to showing each step as the tool goes live. — What the deploy command does. Product UI. Sample data.

Questions and answers

What does a tool need before it can go to production?

A place to run, a sign-in, secrets kept out of the code, a security check, a way to roll back, logs, and an owner. Substrait provides all of them as one path, so the builder runs one command.

Does Substrait rewrite the tool?

No. Substrait runs the unmodified tool the builder produced. It does not rebuild it on another framework.

Can a production tool be public, for customers?

Yes. In production, sign-in is the owner's choice, because the tool has already passed the security check. A customer-facing form or status page can be public.