Skip to main content
ChangeGuard AI is the decision and control layer for infrastructure change. Before a change executes, it judges the proposed change against the environment it will actually enter and answers SHIP, HOLD or BLOCK with the reasons in plain terms. If the change is authorized — by a person, or by a policy you wrote — that authority becomes a short-lived Permit, an Executor carries out only the permitted action, and ChangeGuard observes what actually happened and verifies it. Everything is kept, permanently, on one record per change.
ChangeGuard AI Preflight showing a HOLD verdict with reasons, the CSC score and an evidence panel

A real verdict: a proposed change judged against a live environment, with the reasons, the evidence it had — and the evidence it did not have.

​
The vocabulary you need (and nothing else)

You do not need to know Kubernetes internals, how evidence is collected, or any internal identifier to read a verdict. Those details exist, and are documented further down, but the first-use path never requires them.

​
Where you are going

1

Run your first Preflight

A verdict in about two minutes, with nothing connected. Step 2
2

Understand SHIP / HOLD / BLOCK

What each verdict means and why HOLD is the honest default. Step 3
3

Connect an environment

Live context for every judgment, read-only. Step 4
4

Connect GitHub

A verdict on every pull request — nothing to paste. Step 5
5

Judge a real proposed change

Open a pull request and watch it get judged. Step 6
6

Observe the outcome

What actually happened, written into the same record. Step 7
7

Understand the Change record

One change, one permanent address. Step 8
8

Optional: enable execution

Let ChangeGuard AI apply approved fixes through the Cloud Executor — under a Permit. Step 9
9

Optional: choose Advise or Auto

Decide how much authority it gets, per environment. Step 10
Prefer to watch first? The live demo walks this exact path against a live environment — every verdict in it is real.

​
What is free and what is not

Judging a change in Preflight and getting a verdict on every GitHub pull request are available on every plan, including the trial. Connecting an environment for live evidence (Fleet, and the optional Edge collector) and enabling execution are available on Professional and above, and to design partners; the product marks those surfaces with a Pro tag and explains the gate when you open them. A judgment without a connected environment is still a real judgment — it simply says that live environment evidence was not available.