Copilot analytics
Seats, adoption and per-user activity — surfacing idle licences you're billed for but no one is using.
About FinOpsAid
We meter the GitHub spend that no invoice itemizes.
FinOpsAid is a FinOps console for GitHub. It takes the usage GitHub throws away in 100 days — Copilot seats, AI credits, Actions minutes, Codespaces, storage, and self-hosted runner fleets — keeps it in a versioned warehouse, attributes it to teams, forecasts it, and reconciles every signal against the billed dollars. The cost your invoice leaves as one lump, turned into numbers you can act on this week.
The principle
A usage signal is not a dollar. We reconcile; we never conflate.
ai_credits_used is a single daily per-user hint — never an invoice. Money comes from the billing API, and it lags the signal by a few days by GitHub's design. Most tools quietly merge the two and call it a dashboard. FinOpsAid keeps them separate: we meter the signal, anchor it to the billed truth, and show you the gap — and we label every estimate as an estimate, every time.
What we cover
Every corner of GitHub spend, in one place
GitHub Actions & runners
Workflow minutes and self-hosted runner fleets, with idle runner cost modelled from your own infra rates.
Codespaces & storage
Idle and oversized Codespaces flagged from the nightly snapshot; Actions artifacts, packages and LFS itemised by category.
AI credits & cloud LLMs
GitHub AI credits plus Anthropic, Vertex AI, Azure OpenAI and Bedrock spend — token usage reconciled against each provider's bill.
Team & repo attribution
Cost mapped to teams and repositories — the attribution GitHub won't give you — with budgets and month-over-month forecasts.
A versioned warehouse
History is never overwritten (SCD2). Exports to CSV, Excel and JSON, and k-anonymity-gated benchmarks against an anonymised cohort.
How we handle your data
100% read-only. Your source code is never stored.
FinOpsAid connects through a GitHub App that requests read-only scopes only — no seat changes, no permission edits, no code pushes. We read metadata and metrics, not file contents, so your source is never stored. Because only Read is granted, writing back to GitHub is technically impossible, not just a policy we promise. Access is revocable at any time from your org's GitHub App settings.