GitHub and Cloudflare are the SaaS connectors you can connect today, in Beta. The others below are not connectable yet: this post documents what each one is planned to read and the token scope it will ask for, so you can judge the access before it ships. A platform goes live only once its scanner has run against a real account and its findings have been checked by hand. The shared pattern: a least-privilege, read-only API token, a scheduled scan, and the same finding model as the cloud connectors.
GitHub (connectable now, Beta)
One connection per user account or organization, with a fine-grained personal access token that is read-only throughout: Metadata, Actions, Administration, Code scanning alerts, Dependabot alerts and Secret scanning alerts. On every repository CloudMonitor checks default-branch protection, open code-scanning, secret-scanning and Dependabot alerts, and deploy keys. It also reads CI/CD health from the default branch's recent workflow runs — a workflow whose latest run failed, a run stuck queued or running, a workflow that keeps flipping between pass and fail — and shows the runs on a CI/CD board. For an organization it reviews fine-grained token expiry, GitHub App installations, API quota and seat use, and Copilot seats when the token belongs to an organization owner; without those permissions, those parts report the missing permission and everything else still runs. It never re-runs a workflow, never writes to a repository, and never reads code. GitHub Enterprise Server works by pointing the connection at your server's API base.
Cloudflare (connectable now, Beta)
Zones, SSL certificate expiry, WAF status, dangling CNAME records, and Workers, Pages, R2 and D1 inventory. Token scope, all Read: Zone and SSL and Certificates (required), plus Zone WAF, DNS, Workers Scripts, Cloudflare Pages, Workers R2 Storage and D1 (optional).
PagerDuty
Services, escalation policies, schedules with coverage gaps, recent incident counts. Token scope: read-only API key.
Datadog
Monitors and their states, SLOs, host count against plan. Key scope: an Application Key paired with an API key, read-only via a custom role.
Okta
Apps, user counts and last-sign-in buckets, enrolled factors, admin assignments. Read-only OAuth scopes or a read-only admin role.
HashiCorp Vault
Seal status, mounts, audit-device health. A policy that allows list + read on sys/* only — never a secret path.
MongoDB Atlas, Vercel, Terraform Cloud
Atlas: clusters, backup state, network access list (any 0.0.0.0/0 entry is flagged). Vercel: projects, domains and certificate state, failed deployments. Terraform Cloud: workspaces and latest run status. Each with the platform's read-only key.
Stripe (operational view only)
Aggregate counts only — charges, refunds, disputes, webhook delivery success. A restricted key with no customer-list or payment-method scope.
The full list and the scope for each is on the Connectors page, marked "coming soon" until it ships. If you would like one of them sooner, tell us: a real account to verify against is what moves a platform up the list.