Skip to main content

GitHub Resets Copilot Pricing as AI Compute Costs Surge

The development community saw this one coming: GitHub will transition its Copilot service to a usage-based billing model on June 1, replacing its existing system of fixed subscriptions supplemented by premium request limits. As reported last week, GitHub suspended new sign-ups for several of its Copilot subscription tiers as it faced a surge in demand from agentic coding workflows.

To address that, under GitHub’s new pricing model, customers across individual, business, and enterprise tiers will receive a monthly allocation of AI credits, which are consumed based on token usage. This includes input, output, and cached data processed by underlying models. Once those credits are exhausted, users can purchase additional capacity at published rates.

The change leaves base subscription prices intact. Individual plans remain priced at $10 per month for Pro and $39 for Pro+, while business and enterprise tiers continue at $19 and $39 per user per month, respectively. Each plan’s monthly fee is mirrored in the value of credits provided.

In short, the pricing change responds to higher compute demands as AI drives far higher usage patterns.

Lightweight vs Intensive Workloads

The shift replaces a system that bundled access to AI features with loosely defined usage caps. That structure, built around premium request units, did not differentiate between lightweight interactions and more intensive workloads. As Copilot has expanded beyond inline code suggestions into longer, multi-step workflows, the mismatch between pricing and compute cost has widened.

GitHub has indicated that the product’s evolution into a more autonomous coding platform is key to the decision. Copilot now supports extended sessions that can operate across entire repositories, creating far higher inference costs than earlier use cases. In this context, a flat pricing model has become difficult to sustain.

The move should be no surprise, given the growing tech industry trend toward metered AI services. Providers, out of financial necessity, are linking pricing to token consumption as generative AI workloads scale in complexity. Similar adjustments have been observed across competing platforms, where vendors are recalibrating limits and access to manage infrastructure strain.

For enterprise customers, the new model introduces additional financial controls. Organizations can pool unused credits across teams, reducing inefficiencies associated with per-user allocations. Admins can define spending thresholds at various levels, including individual users and cost centers, and determine whether usage can exceed those limits.

To ease the transition, GitHub will provide temporary increases in credit allocations for business and enterprise customers during the rollout period. A billing preview tool, scheduled for release in May, will allow users to estimate costs under the new system before it takes effect.

The update also removes fallback mechanisms that previously allowed continued usage at reduced capability after limits were reached. Going forward, access will be governed strictly by available credits and administrative policies. Certain features, like code completions and editing suggestions, will remain exempt from credit consumption.

For individual users, the transition will occur automatically for monthly subscribers. Those on annual plans will retain the current pricing structure until renewal, at which point they will be moved to the new system or given the option to convert earlier with prorated adjustments.

For GitHub, tying pricing directly to usage positions Copilot for long-term scalability. But for some heavy-duty AI developers, it will likely result in higher usage costs.



from DevOps.com https://ift.tt/yWAUjip
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more