Integrations

Connects to the tools your changes already flow through.

ChangeGuard reads change and cluster state from where it already lives, and writes back only where you ask it to. Here’s exactly what each integration reads, what it writes, and what it needs.

IntegrationReadsWritesPermissionsEffortSupport
Kubernetes (collector)Workloads, events, config, posture — cluster-wide, read-onlyNothing by default; workload patches only at opt-in remediationRead-only ClusterRole; optional namespaced write Role you apply1 Helm commandGA
GitHub AppRepo metadata & contents (for recommended-fix PRs and the optional code graph)Opens pull requests with proposed fixesExactly contents:write, pull_requests:write, metadata:readInstall the app on selected reposGA
ArgoCDApplication & sync state for GitOps change visibilityNothingRead access to Argo resources in-clusterAuto-discoveredGA
Flux CDGitOps reconciliation stateNothingRead access to Flux resources in-clusterAuto-discoveredGA
CI/CD (GitHub Actions, GitLab CI, shell)Change/manifest you submit for a pre-flight checkNothing in your cluster; returns a verdictA cicd-scoped API keyAdd a step/templateGA
Slack / Microsoft Teams / WebhookNothingOutbound notifications you configureAn incoming webhook URLPaste a webhookGA
Amazon Bedrock (Claude)Runs in the ChangeGuard control plane (not your cluster)NoneGA
Self-hosted inference (NVIDIA NIM)For teams that require in-VPC model inferenceRoadmap

GitOps-native

ChangeGuard understands ArgoCD and Flux, so change visibility works fleet-wide without you wiring anything up per cluster.

Advisory in CI

Add a pre-flight step and get a SHIP/HOLD/BLOCK verdict on the PR. It reports a verdict; it never blocks the job unless you choose to gate on it.

Fixes as pull requests

With the GitHub App, recommended fixes arrive as PRs you review and merge — the same review flow your team already trusts.

Bring your stack

Most teams are connected end-to-end in well under an hour. Setup steps for each integration are in the docs.