Current limitations

DeliveryCompass is in an early-access pilot. These are the product boundaries you should expect today — what is not supported yet, and where the UI may not match how large enterprises usually run shared tooling.

• One organization per account. Each login is tied to a single organization workspace. You cannot switch between multiple orgs in one session.
• No shared workspaces. There is no invite flow, no teammate logins, and no role-based sharing inside an organization. One account owns the workspace.
• Org names are first-come. If someone already registered your GitHub organization name, your account is placed in a private sandbox workspace. You can finish setup, but you will not see that organization’s data.
• Email + password login only. GitHub is used for data import, not for signing in to DeliveryCompass.

• GitHub only. Metrics are built from GitHub pull requests and reviews. We do not connect to GitLab, Bitbucket, Jira, Linear, or CI/CD systems.
• Personal access token required. You provide a PAT with read:org and repo scopes. OAuth or GitHub App install for customer login is not available in the pilot.
• PR workflow metrics only. No issues or commit graphs. GitHub releases and semver tags appear as optional chart milestone markers after sync — not pipeline status or deploy frequency from CI/CD. Team throughput is based on merged pull requests.
• No source code import. Statistics and PR workflow metadata only — we never download or store file contents, diffs, or commit content.
• Read-only. DeliveryCompass never creates or modifies repositories, pull requests, reviews, or settings in GitHub.

• Manual team–repo mapping. GitHub’s team-to-repository links are not imported. You assign each repository to a team card on Teams & repos.
• One team per repository. A repository can belong to at most one team for KPI scope. Moving a repo reassigns it.
• Archived repos and forks are excluded. They are not included in ingestion or team comparisons.
• Unassigned repos have no team KPIs. Repositories you have not mapped to a team are synced but excluded from team-level comparisons until assigned.
• GitHub team membership is informational. We import team names and members from GitHub, but team metrics are driven by which repos you mapped, not by GitHub membership alone.

• Daily sync, not real-time. GitHub data is refreshed about once every 24 hours. Dashboard numbers can be up to a day behind the latest merges and reviews.
• Limited year views. The dashboard year picker covers the current calendar year and the two prior years. Older imported history is stored but not exposed in those views yet.
• Weekly summary on Mondays. The exportable weekly packet is generated after the Monday daily sync, not on demand throughout the week.
• Bootstrap takes time. The first full import runs in the background after setup. Large organizations may wait minutes to hours before all historical PRs appear.

• Not Jira, Linear, or a sprint board. We do not track issues, story points, or roadmaps.
• Not CI/CD or DORA deployments. Metrics come from GitHub pull requests — not pipeline runs or release frequency from your deploy system.
• Not real-time. Data refreshes about once per day; see data freshness.
• Not a replacement for 1:1 judgment. KPIs support coaching conversations; they do not rank individuals for compensation decisions.

Many teams start with spreadsheets and ad-hoc GitHub API scripts. DeliveryCompass makes sense when you want consistent definitions, team comparisons, and a weekly leadership handout without maintaining ETL and dashboard code. A full BI stack may still be right if you need cross-tool analytics beyond GitHub PRs. See choosing delivery metrics for a category comparison.

• Free early-access pilot. No payment or subscription management in the product yet.
• No automated coaching. We surface comparative KPIs and attention signals; we do not generate performance review recommendations or manager action plans.
• Not a project-management replacement. DeliveryCompass complements your existing rituals — it does not replace sprint boards, roadmaps, or incident tooling.
• No threshold alerting. There are no Slack or email alerts when metrics cross thresholds. You can opt into a weekly Sunday digest and manage preferences on your profile.
• Export is lightweight. Weekly summary supports on-screen review and copy-friendly output — not scheduled PDF delivery or branded report packs.

See How it works for what the product does support today.