Microsoft's GitHub shifts to metered AI billing amid cost crisis
GitHub is transitioning GitHub Copilot from a request-based to a usage-based billing model effective June 1, 2026, due to unsustainable AI inference costs. The change introduces GitHub AI Credits, a virtual currency tied to token consumption, to better align user costs with actual resource usage. While subscription prices remain unchanged, users will receive monthly credit allotments and can purchase overages. Unlimited access will still apply to basic features like code completions and Next Edit Suggestions.
- ▪GitHub is replacing its request-based billing for Copilot with a usage-based model tied to token consumption starting June 1, 2026.
- ▪The new system uses GitHub AI Credits, where 1 credit equals $0.01, to measure and charge for input, output, and cached tokens.
- ▪Subscription prices remain the same, but users will get monthly AI Credit allowances, such as 1,000 for Copilot Pro and 3,900 for Pro+.
- ▪Users who exceed their credit limit can set an overflow budget or wait for the next billing cycle to regain full access.
- ▪Basic Copilot features like code completions and Next Edit Suggestions will remain unlimited on paid plans.
Opening excerpt (first ~120 words) tap to expand
AI + ML 29 Microsoft's GitHub shifts to metered AI billing amid cost crisis 29 The all-you-can-eat AI buffet is coming to an end Thomas Claburn Tue 28 Apr 2026 // 00:31 UTC Microsoft is closing the AI buffet offered to GitHub Copilot customers, acknowledging that it can’t sell AI like Red Lobster's Endless Shrimp. The US seafood restaurant's all-you-can-eat shrimp promotion led the company to bankruptcy in 2024 and while Microsoft is nowhere near so financially overextended, the software giant's code hosting biz has decided it no longer wants Copilot to operate at a loss. GitHub is therefore shifting Copilot from request-based billing to usage-based billing on June 1, 2026.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Theregister.
Discussion
0 commentsMore from Theregister
