Skip to main content
ChangeGuard is an autonomous deployment safety platform. Beyond scoring and gating deploys, it can detect a failing workload, diagnose the root cause, propose a concrete fix, execute that fix inside your cluster under an explicit policy, verify that the fix actually worked, and roll it back if it didn’t. Every step is recorded, attributable, and visible in the dashboard. This is a closed-loop control system, not an observability tool with a chatbot attached. The loop is only ever closed under controls you configure: nothing executes automatically until you set the autonomy level to Auto and define a complete execution policy. Out of the box, ChangeGuard only observes and advises.

​
The loop

Two properties of this loop matter more than any individual feature:
  1. Every arrow is auditable. Each transition appends an event to an append-only audit trail, and the full lifecycle renders as an activity timeline on every incident in the dashboard.
  2. Failure escalates, it never loops. A failed verification triggers exactly one compensating action, and a rollback - whether it succeeds or fails - always leaves the incident escalated for a human. The system never retries indefinitely, never rolls back a rollback, and never silently resolves an incident it couldn’t fix.

​
Lifecycle states

Remediations and incidents move through first-class states - not free-form strings - so you can filter, alert, and reason about them precisely.

​
Where to go next

Autonomy model

The four-level dial that decides what ChangeGuard may do on its own

Execution policy

The allowlist contract that bounds Auto mode - editable from the dashboard

Verification

How ChangeGuard proves a fix worked before claiming success

Compensating actions

Automatic rollback: pre-state capture, drift refusal, single attempt, escalation

Safety guarantees

The invariants that hold even when things crash mid-flight

RBAC boundaries

Why the control plane physically cannot exceed what you granted

Audit trail

The append-only record and the incident activity timeline