Insights
Velocity, risk, cost, retrospectives, compliance exports, and optional fleet benchmarks for operators and leadership.
Insights at /dashboard/insights is the signed-in analytics hub for engineering leaders and operators. It reads the same Change Passport, gate, merge-policy, and usage evidence as the rest of v4 — not a separate data warehouse.
What you see
| Area | What it answers |
|---|---|
| Velocity vs risk | Daily merges vs high-risk merges over 30- and 90-day windows — is throughput rising while risky merges stay flat or fall? |
| Cost attribution | Critique credits by repository, expensive PRs this month, and estimated BYOK savings vs bundled routing on the same usage |
| Retrospectives | Sprint or date-range summary: merges, linked incidents, checkpoint and merge-policy overrides, and heuristic override quality signals (14-day incident window) — with optional AI narrative and cited evidence |
| Staffing | Projected weekly review load and when added senior reviewer capacity may be needed to hold your risk posture |
| Compliance export | One-click calendar-month bundle: signed outer manifest plus per-passport audit JSON (reviews, merge policy, checkpoint, coverage summary). Same SOC 2 / ISO audit evidence disclaimer as single-passport export — not a certification |
| Fleet benchmarks (opt-in) | Anonymized cohort comparisons (similar stack size and risk tier) when enough teams participate — dry-run policy suggestions, no repo names or secrets exported |
How data stays fresh
Daily rollups update as reviews finish, merge policy and checkpoint events fire, overrides are recorded, usage is metered, and PRs merge. After upgrading, operators can backfill historical daily metrics from existing reviews, gates, and usage so 30- and 90-day charts are useful immediately.
Filter by GitHub App installation when you manage more than one org.
Fleet insights (strictly opt-in)
Fleet mode places your installation in an anonymized cohort. You only see benchmarks when:
- You explicitly opt in from Insights, and
- The cohort has enough participating teams to preserve privacy.
Comparisons might include auth-path block rates or similar aggregates — never raw repo names, patches, or secrets.
Relationship to passports and export
| Need | Where |
|---|---|
| One PR’s full story | Change control → passport detail |
| Single passport audit JSON | Export audit bundle on passport header or queue |
| Month of passports for auditors | Compliance period export in Insights |
| API automation | Connections & Platform API — read:passports and report routes |
Related
- Change control
- Dashboard
- Billing & credits
- BYOK — cost attribution includes BYOK vs bundled savings