GitHub will start charging Copilot users based on their actual AI usage

2026-04-28 · Source: AI - Ars Technica · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Emerging Technologies & Innovation · Depth: Fundamental Awareness, short

Summary

GitHub is transitioning its Copilot AI service to a usage-based billing model, effective June 1, to better align pricing with actual computing costs and ensure financial sustainability. Currently, subscribers receive a fixed allocation of "requests" and "premium requests," which GitHub states does not reflect the varied backend costs of different AI tasks. The new system will provide monthly "AI Credits" matching the subscription payment, with additional usage charged based on token consumption (input, output, cached tokens) at varying API rates, similar to OpenAI's GPT models which range from $4.50 to $30 per million output tokens. Simple AI suggestions like code completion will remain free, but Copilot code reviews will incur costs via GitHub Actions minutes. This change follows reports of nearly doubled week-over-week costs for Copilot since January, partly due to agentic AI assistants consuming massive tokens.

Key takeaway

For CTOs and VP of Engineering evaluating AI tool subscriptions, you should anticipate a broader industry shift towards usage-based billing for AI services. Review your teams' current GitHub Copilot usage patterns with the "preview bill" tool to forecast future costs and adjust budgets, especially for workflows involving agentic AI or extensive code reviews, to avoid unexpected expenses.

Key insights

AI service providers are shifting to usage-based billing to manage escalating inference costs and ensure sustainability.

Principles

• Pricing must align with actual compute costs.
• Token consumption dictates AI service expenses.

Method

GitHub's new model allocates monthly AI Credits matching subscription fees, with overage billed per token based on model sophistication and input/output/cached token usage.

In practice

• Forecast costs using GitHub's "preview bill" tool.
• Monitor token consumption for AI-driven workflows.

Topics

• GitHub Copilot
• Usage-Based Billing
• AI Credits
• Token Consumption
• GitHub Actions

Code references

• orgs/community

Best for: CTO, VP of Engineering/Data, AI Engineer, Director of AI/ML, AI Product Manager, Tech Journalist

Related on AIssential

• The Subsidy Ended: What Tool-Using Agents Actually Cost — GitHub Copilot shifted to usage-based billing, linking costs directly to AI model and token consumption.
• Microsoft's GitHub shifts to metered AI billing amid cost crisis — GitHub Copilot is shifting to usage-based billing to manage escalating AI inference costs.
• Cobrança de tokens no GitHub Copilot aumentará custos em até 150 vezes — GitHub Copilot's new token charges will drastically increase costs, impacting user economics.
• AI costs how much? GitHub Copilot users react to new usage-based pricing system. — GitHub Copilot's shift to usage-based billing reveals significant AI inference costs previously absorbed by providers.
• ‘What a joke’: Github Copilot’s new token-based billing spurs consternation among devs — GitHub Copilot's new token-based billing model, effective June 1, significantly raises costs for many users, prompting debate over usage efficiency and Microsoft's role.
• Changes to GitHub Copilot Individual plans — Agentic AI workflows significantly increase compute demands, necessitating pricing model adjustments.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by AI - Ars Technica.