Metering the invisible
The GitHub spend
no one is metering.
Copilot seats, AI credits, Actions minutes, Codespaces, storage, and self-hosted runner fleets — snapshotted nightly, attributed to teams, forecast, and reconciled against the bill. The telemetry GitHub throws away in 100 days, kept and turned into dollars.
- 19 connectors
- SCD2 warehouse — history is never overwritten
- MoM / YTD forecasts & CSV·Excel·JSON export
- k-anonymity-gated benchmarks
Where it leaks
Money escapes through the gaps GitHub leaves uncounted.
None of these show up as a line item. Every one is a number we can put on the table this week.
Signal vs. billed
A usage signal is not a dollar. We meter the signal, anchor it to the billed truth, and show you the gap.
ai_credits_used is a single daily per-user number — a hint, never an invoice. Money comes from the billing API. Most tools quietly conflate the two and call it a dashboard. We don't. We reconcile; we never conflate.
How it meters
A pipeline that assumes GitHub's history is already disappearing.
Metrics retain roughly a year, reports about a hundred days. What we don't capture tonight is gone. So we capture all of it — nightly, versioned, attributed.
See it in action
The intelligence, on screen — not a slide deck.
Real dashboards from the demo workspace. Every modeled figure is labeled an estimate; every number carries an as-of date.



















We hold billing, per-developer, and permissions data for many tenants. The guardrails are the product.
Get started
Meter one month of your GitHub bill — free.
Explore the live demo, or connect a read-only GitHub App and give us a nightly sync. We'll hand you the idle seats, the runner burn, and the credit drift in a week. No write access. No PATs.