Docs: Microsoft plans to eventually move GitHub Copilot from request- to token-based billing, as the week-over-week cost to run it has nearly doubled since Jan.
Edward Zitron /Ed Zitron's Where's Your Ed At:
Context & Ripple Effects
GitHub Copilot had already illustrated the strain in flat-rate AI subscriptions: 2023 reporting said the service was losing money per user, while this coverage points to sharply rising inference costs in early 2026.
The subsequent GitHub announcement set a June 1 transition to monthly AI Credits, and later coverage recorded developer complaints over depleted caps and higher bills. This report is the cost rationale linking Copilot's infrastructure economics to that pricing change.
First-order effects
- Microsoft and GitHub can shift Copilot's heaviest users from a largely predictable subscription cost to metered AI-credit or token spending, better aligning revenue with usage.
- Developers and teams that use Copilot intensively face less certain monthly spend and must monitor consumption once the new billing model arrives.
Second-order effects
- Engineering organizations may ration premium AI interactions, set internal usage controls, or move particular workloads to lower-cost tools when token charges become visible.
- Competing coding-assistant providers will be pressured to make their own pricing and limits clearer, balancing attractive flat-rate offers against the risk of absorbing escalating inference costs.
Third-order effects
- If token metering spreads, AI coding assistants are likely to be sold less like conventional SaaS seats and more like software subscriptions with variable compute charges.
- The episode points to a broader test of whether AI product adoption can support durable margins without transferring more infrastructure-cost volatility to customers.
The trend: Generative-AI vendors are moving from subsidized flat subscriptions toward pricing models that expose the cost of compute-intensive usage.