Skip to main content
ChangeGuard is designed to sit alongside the tools you already run, not replace them. This page describes each integration with the same structure — what it reads, what it writes, the permissions and effort it takes, and its support level — so you can plan a rollout without surprises.
This list covers the integrations we verified for this release. If you need one that isn’t here (a specific chat platform, ticketing system, or CI vendor), contact support@changeguard.ai — several are handled case-by-case and aren’t self-serve yet.

​
GitOps — Argo CD & Flux

ChangeGuard ingests changes from GitOps controllers so that “what changed” reflects your real delivery pipeline, not just raw cluster mutations.

​
CI / CD — pre-flight gate via API

The same pre-flight check you run in the UI is available to your pipeline, so you can ask “is it safe to ship right now?” as a step in CI.
Roll this out in two phases: first log the verdict without acting on it so your team sees it match reality, then make BLOCK fail the build. The score is deterministic, so a gate built on it is stable.

​
Notifications

ChangeGuard can alert your team when it detects a change or an incident, so the signal lands where people already look.
Specific notification destinations are configured inside the product and may vary by plan. Check the in-app notification settings for the current list, or ask support if you need a destination you don’t see.

​
Security scanners (bundled)

The scanners aren’t third-party integrations you wire up — they ship with ChangeGuard and run as optional in-cluster jobs. They’re listed here so you know what’s producing findings.
Scanner findings are sent to the control plane; the scanned images and manifests are not. See Architecture & data flow.

​
What ChangeGuard does not integrate with (yet)

To keep this honest: there is no outbound HTTP-proxy support for the collector today, and no SSO/SAML for app sign-in as of this release. If either is a requirement for you, raise it with support before you plan a rollout — we’d rather set the right expectation up front.