Executive summary

DeploySutra AI answers one question before a release: "What exactly changed, how risky is it, and can we get back if it goes wrong?" It does that offline, from files you already have, and it never deploys anything.

Trace the Change. Prove the Risk. Deploy by Human Decision.

The problem

Release reviews rely on people reading YAML diffs at the end of a long day. Risky changes (a Service flipping to a public load balancer, a container turning privileged, a password pasted into an env var, replicas dropping to zero, a rollback plan nobody tested) hide in noise. Tools that "approve" releases create false confidence, and tools that need cluster credentials are hard to adopt.

What it does

What makes it different

PrincipleHow it shows up
Never approvesThe gate has two states only: BLOCKED and HUMAN_REVIEW_REQUIRED. There is no READY. The audit proves no input reaches any other state.
No credentials, no networkNo cluster access, no telemetry, no API key, zero dependencies.
Honest about limitsEvery report lists what was NOT_RUN or NOT_TESTED and why.
Proof over promises312 automated tests, a 50-case rule corpus and a self-audit are shipped with recorded results.

Recorded results (version 0.2.0)

Who should use it

Platform and DevOps engineers preparing changes, release managers who need a defensible gate, SREs reviewing rollbacks, security reviewers checking exposure and privilege, and CI maintainers who want a fail-closed check with no credentials.

What it is not

Not a deployment tool, not an admission controller, not a vulnerability scanner, not a compliance certification, and not proof of live state. See the assurance document for the full list.

Decision guide

Adopt it as a pre-merge or pre-release gate input. Keep your existing CD system, approvals and runtime policy engines. Treat HUMAN_REVIEW_REQUIRED as "a person must now decide", never as "safe".