Skip to main content
ChangeGuard AI is the independent judgment layer for production changes. Before a change ships, it judges the proposed change against the environment it will actually enter and answers SHIP, HOLD or BLOCK with the reasons in plain terms. After the change deploys, it observes what actually happened and writes that into the same record. If something goes wrong, it proposes the fix within the authority you grant — advisory unless you say otherwise.
Production changes now come from humans and AI agents, and every one of them arrives with a green build. A passing build says the code compiled; it says nothing about the environment the change is about to land in. That question — should this ship, here, now? — is the one ChangeGuard AI answers, and it never treats missing evidence as safe.

​
New here? Start here

The first-use path takes you from a blank account to a verdict on your own pull requests without learning the architecture first. Nothing to install for your first verdict; nothing to paste for GitHub.

1. What ChangeGuard AI does

The vocabulary, the lifecycle, and what is free.

2. Run your first Preflight

A real verdict in about two minutes, with nothing connected.

3. Understand SHIP / HOLD / BLOCK

What each verdict means and what earns it.

4. Connect an environment

Live context for every judgment — read-only.

5. Connect GitHub

A verdict on every pull request. No API key, nothing to paste.

6 – 8. Judge, observe, keep the record

A real change judged, its outcome recorded, one permanent address.

9 – 10. Remediation and authority

Optional: let it propose fixes; choose Advise or Auto per environment.

Watch the two-minute demo

The same path, recorded live against a real environment.

​
Then go deeper

Everything else in these docs explains one part of the lifecycle in depth: how environments are connected and what evidence is collected (Fleet centrally, the optional Edge collector locally), how the verdict is computed, how the GitHub and CI integrations work, how remediation is bounded and verified, the security and trust model, and the API.
Maturity labels. Capabilities are marked GA (generally available), Early Access (design partners / on request), or Roadmap. The Engineering Advisor and related reasoning capabilities are Early Access. Nothing emerging is documented as if it ships today. See Product concepts and Known limitations.
Who these docs are for. Anyone deciding whether a change should ship — developers, on-call engineers, platform teams — and the operators who connect environments. If you’re evaluating ChangeGuard AI for your organization, start at changeguard.ai.