GitHub Shifts Copilot to Usage-Based Pricing Model Amid Rising AI Costs

GitHub has announced that its popular AI coding assistant, GitHub Copilot, will transition to a usage-based billing system starting June 1, 2026, marking a significant shift from its existing subscription model.

Under the new structure, all Copilot plans will rely on “GitHub AI Credits,” a metered system based on how much users interact with AI models. Instead of counting fixed “premium requests,” usage will now be calculated using tokens consumed during inputs, outputs, and cached interactions, aligning costs more closely with actual usage.

The change reflects growing demand for more advanced AI workflows, including agent-based coding tasks that consume significantly more compute resources than earlier features. GitHub said the move will provide a more flexible and scalable pricing model as developers increasingly rely on AI for complex coding tasks.

While core features such as code completions and next-edit suggestions will remain unlimited, most advanced capabilities will draw from users’ AI credit balances. Developers and organisations will also have the option to purchase additional credits if they exceed their monthly allocation.

"To help customers prepare, we are also launching a preview bill experience in early May, giving users and admins visibility into projected costs before the June 1 transition. This will be available to users via their Billing Overview page when they log in to github.com," Mario Rodriguez, GitHub Chief Product Officer, said in a blog post.

The shift comes amid broader industry pressure to manage the high infrastructure costs of generative AI, as companies balance growing adoption with sustainable business models. The move signals a wider trend toward consumption-based pricing in AI tools, where costs are increasingly tied to actual usage rather than flat subscriptions.

For developers, the update could mean greater flexibility—but also more variability in monthly costs as AI becomes more deeply embedded in everyday coding workflows.

"We are also introducing pooled included usage across a business, which helps eliminate stranded capacity. Instead of each user’s unused included usage being isolated, credits can be pooled across the organisation," Rodriguez added.

This means administrators will gain new budget controls, allowing them to set spending limits at the enterprise, cost centre, and individual user levels.

Once the included usage pool is exhausted, organisations can decide whether to permit additional usage at standard rates or enforce a spending cap.