Connects to the tools your changes already flow through.
ChangeGuard AI reads change and environment state from where it already lives, and writes only with a Permit, where you asked it to. What each integration reads, writes and needs — and its claim class.
| Integration | Reads | Writes | Permissions | Effort | Status |
|---|---|---|---|---|---|
| AWS / EKS — AWS Account Center & Fleet | EKS cluster discovery; workloads, events, quotas, posture — read-only, collected centrally | Nothing | One discovery role (eks:ListClusters, eks:DescribeCluster) trusting ChangeGuard with your external ID; a per-cluster get/list grant you apply | Connect AWS once; authorize clusters you select | Live |
| Cloud Executor | Nothing on its own | Exactly one permitted patch per Permit, to workloads in your chosen namespaces | One execution role per environment with no AWS service permissions — it exists only to authenticate to EKS; Kubernetes authority is scoped separately through an EKS access entry and a namespaced get/list/patch RBAC grant | Generated per environment from its Execution section; nothing installed | Live-proven |
| Local Executor | Nothing on its own | The same single permitted patch, from inside your cluster | Its own service account with a namespaced get/list/patch grant — never the Edge collector’s identity | One generated manifest, applied by you | Supported |
| GitHub pull requests (OIDC) | The changed manifests the workflow sends | A verdict on the pull request; the outcome after deploy, joined back to it | The short-lived identity token GitHub issues to the workflow — no API key, nothing to paste | Connect the repository; add the workflow | Live |
| Any CI/CD or agent (GitHub Actions, GitLab CI, Jenkins, shell, coding agents) | The change or manifest you submit for judgment | Nothing in your environment; returns SHIP / HOLD / BLOCK | A cicd-scoped API key | Add a step or template | Live |
| Amazon EKS MCP (Kiro, Claude Code, Cursor and any MCP client) | The exact manifest or resource body the agent is about to apply | Nothing in your environment; returns SHIP / HOLD / BLOCK, and a pre-tool hook admits the agent’s own write only on a fresh SHIP for that exact content | The same cicd-scoped API key, through the CLI; ChangeGuard AI gains no EKS MCP permissions | One installer, one hook (guide) | Live |
| ChangeGuard Edge (optional collector) | Node-local evidence (runtime signals, benchmarks) plus the same cluster state | Nothing — Edge supplies evidence only and is never the execution path | Read-only ClusterRole. It lists Secret and RBAC objects to discover Helm and GitOps state; secret values are never sent | One generated install | Supported |
| ArgoCD / Flux CD | Application and reconciliation state for GitOps change visibility | Nothing | Read access to Argo / Flux resources in-cluster | Auto-discovered with Edge | Supported |
| GitHub App (fix pull requests) | Repository metadata and contents | Opens pull requests with proposed fixes for you to review | contents:write, pull_requests:write, metadata:read on selected repositories | Install the app | Supported |
| Slack / Microsoft Teams / webhook | Nothing | Outbound notifications you configure | An incoming webhook URL | Paste a webhook | Live |
| Amazon Bedrock (analysis) | — | — | Runs in the ChangeGuard control plane, never in your environment | None | Live |
| Self-hosted inference (NVIDIA NIM) | — | — | In-VPC inference for judgment and reasoning, for teams that require it | — | Roadmap |
Claim classes: Live — running in production · Live-proven — exercised end to end in production acceptance and continuous security testing · Supported — available, used where the topology calls for it · Roadmap — planned, not shipping.
Judgment in CI, enforcement your call
Add a step and get SHIP / HOLD / BLOCK on the change. The shipped GitHub Action fails the job on BLOCK by default and never on HOLD; you can run it purely advisory. Whether a failed check stops a merge is your branch rule.
Execution only with a Permit
Reading your environment never grants writing — not through Fleet, not through Edge. The Executor acts only on a signed, single-use Permit bound to one action in one environment, whether it runs in ChangeGuard’s estate (Cloud) or in your cluster (Local).
Agents welcome
A coding agent that can change infrastructure gets the same judgment, the same Permit requirement and the same verified outcome as a person or a pipeline. One call to ask; nothing executes on its say-so. With the Amazon EKS MCP companion, an agent judges the exact change before it calls a privileged EKS MCP tool: AWS gives the agent the tool; ChangeGuard AI decides whether the exact change should happen.
AI can make the change. ChangeGuard AI decides whether it should.
The EKS MCP companion puts the judgment immediately before an agent’s privileged write: a change judged SHIP is admitted, a scale-up judged BLOCK is denied, an environment never observed is HOLD, and a write with no judgment at all is denied. Setup takes one installer, one hook and one environment mapping; the steps are in the guide.
Bring your stack
A first verdict on a pull request takes minutes to set up. Setup steps for every integration are in the docs.