Blog
How engineering teams see and control AI spend
How to reduce GitHub Copilot costs: seats, credits and budgets
A Copilot bill has two parts, the seat fee and the AI credits on top. Here are the levers GitHub gives you for each part, and the order to pull them in.
How to forecast which developers will go over their AI budget
GitHub and Anthropic tell you when a developer hits a budget, not when they are about to. Here is a simple month-end forecast per developer that names the overspender while you can still act.
How to build an unused GitHub Copilot seats report per team
GitHub shows when each Copilot user was last active, but not which team pays for the idle seats. Here is how to turn the activity data into a per-team report you can act on before the next billing cycle.
How to track GitHub Copilot and Claude spend per developer
One developer can cost you a Copilot seat, a Claude seat and Claude API usage, and each one reports in a different place. Here is which source covers which path, and how to add them into one number per person.
How to see GitHub Copilot cost per user
Under usage-based billing, a Copilot seat price is only the floor. Here is where GitHub shows each user's AI credit use, what each report leaves out, and how to turn it into a cost per person.
Per-developer AI spend tracker: how to build one from GitHub and Anthropic data
GitHub Copilot and Claude Code both report usage per person, but in different units, on different delays and behind different keys. Here is how to join them into one row per developer.