Connector setup guides
Connect your tools to replace empty dashboards with your real metrics. Connectors only ever read — most providers offer narrowly-scoped tokens and we request exactly those; where a provider has no scoped token tier, the guide says so plainly and recommends a short expiration. Each guide walks through creating the credential and connecting it — step by step.
DevOps & Code
GitHub
Reads repositories, pull requests, GitHub Actions, security alerts, and repo artifact signals to compute Delivery Health, Technical Debt, IT Modernization, Lifecycle Risk, and Security Readiness from real data.
GitLab
Pulls groups, projects, merge requests, pipelines, deployments, releases, and security findings to feed Delivery Health, Technical Debt, and Security Readiness.
Gitea
Reads repositories, pull requests, releases, and CI-workflow presence from a self-hosted (or gitea.com) Gitea instance — GitHub-style API — to feed Delivery Health (PR lead time) and Technical Debt (legacy-code + test debt).
Vercel
Reads production deployments and projects from the Vercel REST API to feed Delivery Health with real release data — deployment frequency and change-failure rate, the two DORA metrics Vercel can prove.
Atlassian (Jira + Bitbucket)
Jira Cloud delivery analytics (throughput, lead time, open/aging) plus optional Bitbucket pipeline cadence + change-failure rate — feeding Delivery Health.
Azure DevOps
Reads Azure DevOps Boards, Repos, and Pipelines — work-item throughput & lead time, build/deployment frequency, change-failure rate, and repository staleness, CI coverage, and branch-policy coverage — to compute Delivery Health and Technical Debt from real data.
Cloud
Supabase
Authenticates a personal access token against the Supabase Management API and reads each project's security advisors (RLS, exposed tables, auth) plus the Postgres version to feed Security Readiness, Cloud Health, and the Lifecycle (EOL) inventory.
Amazon Web Services
SigV4-signed read-only access to Security Hub (active findings) and Cost Explorer (spend) to compute Security Readiness and Cloud Health (security posture).
Microsoft Azure
Reads Azure Resource Manager + Microsoft Defender for Cloud: resource inventory, secure score, security assessments, and Advisor recommendations to compute Cloud Health and Security Readiness.
Google Cloud
Authenticates a read-only service account (JWT-bearer) to read Cloud Resource Manager + Compute inventory and Security Command Center findings — feeding Security Readiness and Cloud Health.
Oracle Cloud Infrastructure
Signs read-only OCI API calls (HTTP-signature, no SDK) to read Cloud Guard problems, IAM posture, compartments, resource inventory, monitoring alarms, spend, and database-service posture (availability, versions, backups) — feeding Cloud Health, Security Readiness, and the Lifecycle (EOL) inventory.
Datadog
Reads Datadog monitors, SLOs, incidents, and optional usage cost summaries to feed Delivery Health and Cloud Health from aggregate observability signals.
Dynatrace
Reads Dynatrace entities, problems, and SLOs to feed Delivery Health and Cloud Health with aggregate reliability and incident signals.
Elastic
Reads Elastic cluster health plus aggregate alerting and Elastic Security detection summaries where available, without storing raw logs or event bodies.
OpenSearch
Reads OpenSearch cluster health plus aggregate Alerting and Security Analytics summaries where available, without storing raw documents.
Splunk
Reads Splunk server info, saved-search/alert summaries, fired-alert summaries, and optional index counts without exporting raw events.