GitHub Copilot is evolving — and so is the way it's billed
Starting June 1, 2026, GitHub Copilot is moving from Premium Request Units (PRUs) to a new token-based billing model built on GitHub AI Credits. Whether you're a developer using Copilot every day or an admin managing licenses across your organisation, this change affects you — and we want to make sure you're fully prepared.
Join us for a practical, no-jargon walkthrough of everything that's changing and what it means in practice.
📅 May 12, 2026 | 15:00 CET
What we'll cover
- The old model vs. the new model — how PRUs worked, why GitHub is making this change, and what AI Credits are
- What stays free — inline code completions and Next Edit Suggestions are not going anywhere
- The pooling advantage — how shared credits across your organisation can work in your favour
- Live demo — see token usage in real time with the Copilot Token Tracker extension
- Admin controls — budgets, overages, cost-centre settings, and how to use the May Preview Bill
- Your action checklist — exactly what to do before June 1
- Q&A — bring your questions, we'll answer them live
Who should attend?
| If you are… | You'll learn… |
| A developer using Copilot daily | Which features change, which stay free, and how to track your own usage |
| A team lead or engineering manager | How to set expectations with your team and understand usage patterns |
| A GitHub Copilot Business/Enterprise admin | How pooling works, how to configure budgets, and how to avoid surprise invoices |
| Procurement or IT finance | What the cost model looks like, what controls exist, and how overages are governed |
Why attend?
- Plan prices are not going up — but the billing model is fundamentally different
- The new model rewards efficient usage and gives admins far more control
- GitHub is offering promotional extra credits for June, July, and August to help organisations transition
Read more: GitHub Copilot - Going from Premium Request Units to Token Based Billing