How DeliveryCompass works

DeliveryCompass reads your GitHub organization’s pull requests and reviews, stores that history, and turns it into team delivery KPIs — merge throughput, lead time, and review responsiveness — on a dashboard and weekly summary. We never write to GitHub.

We import delivery statistics and PR metadata only — we never read, store, or analyze your source code, diffs, or file contents.

What we do

• Connect to your GitHub org with a personal access token (read:org and repo scopes).
• Import repositories, teams, pull requests, and reviews into our database.
• Compute delivery metrics per team after you assign repos to team cards on Teams & repos.
• Show org-wide and per-team KPIs on the dashboard; export a weekly summary for leadership reviews.

We do not use deployments, CI/CD runs, issues, or commit history. Team throughput is derived from merged pull requests only.

Statistics only — no source code

DeliveryCompass is a delivery metrics product, not a code-analysis tool. We import workflow statistics from GitHub so managers can compare teams — without touching your codebase.

What we import:

• Pull request and review metadata (titles, states, authors, timestamps)
• Line counts reported by GitHub on each PR (additions, deletions, changed_files)
• Filenames on merged PRs only — aggregated into file-extension breakdowns (e.g. how much .go vs .ts changed)

What we never import or store:

• Source file contents, patches, or diffs
• Commit messages or commit blobs
• Repository file trees or branch contents

See also the FAQ: Do you read or store our source code?

What we read from GitHub

Resource	GitHub API	Fields we store
Repositories	GET /orgs/{org}/repos	Full name, archived/fork flags, default branch
Teams	GET /orgs/{org}/teams	Team name and GitHub team ID
Team members	GET /orgs/{org}/teams/{slug}/members	Member logins (for team membership labels)
Pull requests	GET /repos/{owner}/{repo}/pulls and PR detail	Number, title, state, author, created/merged/closed timestamps, additions, deletions, changed-file count
Changed files	GET /repos/{owner}/{repo}/pulls/{n}/files	Filename and per-file line counts only (no file contents or diffs); merged PRs only; used for file-type breakdowns
Reviews	GET /repos/{owner}/{repo}/pulls/{n}/reviews	Reviewer login, review state, submitted timestamp

We do not import GitHub’s team–repository links. You assign repos to teams manually in the app so KPI scope matches how your org works.

Archived repositories and forks are skipped during import. Repos the token cannot access are excluded from sync.

GitHub releases and semver tags (v*.*.*) are also imported as optional chart milestone markers on delivery trend charts — not as deployment or CI/CD metrics.

How often we sync

• First import (bootstrap) — runs automatically after you finish setup with a valid token. The worker checks every 60 seconds until bootstrap completes. It imports full PR history for every active (non-archived, non-fork) repository in the org.
• Daily sync — runs every 24 hours for all connected organizations. Refreshes the repository catalog, teams, and pull requests updated in the last ~90 days, then re-imports reviews for those PRs.
• Metrics — recomputed after bootstrap and after each daily sync (7-day and 30-day ranges).
• Weekly summary — generated on Mondays after the daily sync.

Dashboard year views cover the current calendar year and the two prior years. Older imported data stays in the database but is not shown in those views yet.

Create an account, optionally connect a GitHub personal access token, finish setup, then map repositories to teams. Import runs in the background — no sales call and no credit card during the pilot.

Overview dashboard

Organization-wide DORA-style KPIs, overview charts, and team comparison cards on /app/dashboard.

Team analytics

Chart grid, contributor tables, and activity context on /app/dashboard/analytics. See team analytics guide.

• Merge throughput — merged PRs over the selected period
• Lead time — median open-to-merge duration
• Review responsiveness — how quickly reviews happen
• Team productivity score — composite signal for comparison across teams

Weekly summary

Leadership packet with attention callouts — built for staff syncs. Generated Mondays; manual refresh available. Optional Sunday email digest.

Snapshots

Compare any two weekly summaries week-over-week on /app/snapshots.

Teams & repos

Assign repositories to team cards so KPIs reflect how your organization is structured. Unassigned repos stay out of team comparisons until you map them.

Your GitHub token is stored encrypted and is only used for read-only API calls — never as a login credential.

• No writes to repositories, branches, pull requests, or CI/CD workflows
• Read-only API usage with read:org and repo token scopes
• No source code, diffs, or commit content is downloaded or persisted
• Same KPI definitions for everyone in your organization workspace