For platform and SRE
Scale your judgment across every team.
You cannot review every change in every repo. You can decide what good looks like once, and let each team’s scan hold the line.
Example data. Repos with no team binding are grouped under Unassigned, so the mapping gap shows instead of hiding.
Know which repos nobody scans
PlanPer-team views start at the Plus plan. See pricing.
70 controls, with the evidence behind them
Every control maps to the services it covers. Control status is computed for each team, and the organization answer is the worst of them: a control counts only when every team is covered.
Teams inherit evidence through service ownership. Your backup drills for a shared database count for every team that depends on it.
| Control | checkout | payments | platform |
|---|---|---|---|
| SLO-Tied AlertingRC-001 · detective | – | 2 | – |
| Synthetic MonitoringRC-002 · detective | 1 | – | – |
| Alert Noise ReductionRC-004 · corrective | 9 | 7 | 5 |
| On-Call CoverageRC-005 · preventive | – | – | 2 |
| Incident RunbooksRC-006 · preventive | 4 | – | – |
Example data. A lit row is one failure class that recurs across teams. A lit column is one team with many.
Practices count too
Evidence carries a scope: team, service, or global. A control counts for the organization only when every team is covered.
Not a replacement for you
Run your first scan free.
Install the CLI, scan a repo, and read the findings in your terminal. Your source code stays on your machine.