Integrations

Your stack,
checked and mapped to your controls

53 integrations, 165 automated checks, every one listed on this page. Most run over a read-only key you scope yourself; GitHub, GitLab, Jira, Asana and Slack sync work both ways; and the MCP server lets your AI read your compliance data.

Book a conversation

Automated checks

devguard reads your configuration with a read-only key and turns what it finds into evidence on your controls

Two-way sync

Work flows both directions: remediation opens as issues in your tracker, status flows back as evidence

AI access

Point Claude, Cursor or any MCP client at your compliance data and ask it questions

The directory

Every integration, every check, listed

No teasers and nothing "coming soon": each tile below is shipped, and its page lists every check it runs

Cloud11Identity6Source control3Developer tools9Monitoring6Security3Communication7HR & devices4Business4

Cloud

11
Amazon Web Services
3 checks
Microsoft Azure / Entra ID
3 checks
Cloudflare
4 checks
DigitalOcean
3 checks
Divio
3 checks
Exoscale
3 checks
Fly.io
2 checks
Google Cloud Platform
3 checks
Hetzner Cloud
2 checks
Netlify
3 checks
Vercel
4 checks

Identity

6
Bitwarden
4 checks
Google Workspace
4 checks
JumpCloud
2 checks
Microsoft Entra ID
3 checks
Okta
4 checks
1Password
1 check

Source control

3
Bitbucket
3 checks
Two-way sync
GitHub
4 checks
Two-way sync
GitLab
4 checks

Developer tools

9
Anthropic
4 checks
Buildkite
3 checks
CircleCI
3 checks
Mailgun
3 checks
AI access
MCP server
OpenAI
4 checks
Postmark
4 checks
SendGrid
4 checks
Twilio
3 checks

Monitoring

6
Better Stack
4 checks
Datadog
3 checks
Grafana Cloud
3 checks
Opsgenie
4 checks
PagerDuty
4 checks
Sentry
4 checks

Security

3
Have I Been Pwned
3 checks
Snyk
3 checks
SonarCloud
4 checks

Communication

7
Two-way sync
Asana
3 checks
Atlassian Jira & Confluence
2 checks
ClickUp
2 checks
Two-way sync
Jira
Notion
3 checks
Two-way sync
Slack
3 checks
Zoom
4 checks

HR & devices

4
BambooHR
3 checks
Microsoft Intune
3 checks
Jamf Pro
3 checks
Kandji
2 checks

Business

4
HubSpot
3 checks
Intercom
4 checks
Stripe
4 checks
Zendesk
4 checks

Plus a generic HTTP and TLS check runner for anything with an endpoint See the developer docs

How it works

From read-only key to audit-ready evidence

The same three steps for every provider on this page — nothing scraped behind your back

01

Connect with a read-only key

You create the credential yourself, scoped to the minimum the checks need, and paste it in. Each integration page lists exactly which permissions that is, and the key is revocable on your side at any time.

02

Checks run on a schedule

Each check reads your configuration and verifies one concrete thing — 2FA enforced, branch protected, TLS on every domain. It only ever reads: devguard holds no write access and remediates nothing silently.

03

Results attach to your controls

A passing check becomes evidence on the control it supports; a failing one becomes a finding you decide how to treat. Nothing pages your engineers, and the trail is ready when the audit comes.

You connect it. You stay in control.

Every connection is one you make: scoped by you, read-only where the page says read-only, revocable whenever you want. Checks run from Swiss infrastructure, and results and evidence stay in Switzerland.

Bring your current test list, we'll map the gaps

20 minutes on how you run certification today. Bring your current platform's test or control list and we'll tell you honestly where these checks cover it — and where they don't yet.

Book a conversation
Sign in
Start for free
Book a conversationStart for free