GitHub Copilot Enterprise pricing [2026]: seats, AI credits, and the September cliff

The most famous Copilot deployment just got a new meter

In January 2024, Satya Nadella stood on a Microsoft earnings call and made GitHub Copilot’s biggest customer announcement to date: Accenture would roll the tool out to 50,000 developers. It capped a very public arc. GitHub’s own customer story had already showcased 12,000 Accenture developers on Copilot, and a randomized controlled trial GitHub ran with Accenture, 450 developers using Copilot against a 200-developer control group, reported an 84% increase in successful builds.

For two and a half years, everyone could do that deployment’s math in their head. Seats times price. At Enterprise list rates, 50,000 developers is $1.95 million a month, $23.4 million a year, and the number was boring in the best way: it did not move unless headcount did. (Nobody outside Accenture knows their actual contract, so treat that as list-price arithmetic, not a leaked invoice. The point survives either way.)

Then June 1, 2026 happened, and the math stopped being math you can do in your head.

GitHub moved every Copilot plan to usage-based billing. Premium requests are dead. In their place: GitHub AI Credits, where one credit equals one cent, consumed by token usage across input, output, and cached tokens at each model’s listed rates. The seat still costs $39. But now it includes $39 of credits, the credits pool across the organization, agentic workflows drink from that pool at a rate no seat count predicts, and anything beyond the pool bills on top.

Same product. Same sticker. Completely different bill. And GitHub said the quiet part in its own FAQ discussion: “Users with intense agentic usage will likely see an increase in costs.”

Developers translated immediately. As one put it in the reaction Visual Studio Magazine rounded up: “You will get less, but pay the same price.” One r/GithubCopilot thread is titled “The new Copilot pricing makes zero sense.” It makes perfect sense, actually. It just makes a different kind of sense than a seat price does, and that’s the whole problem.

What are the GitHub Copilot Enterprise plans and prices in 2026?

Here are the paid organizational tiers:

Both figures come straight from GitHub’s announcement: seat prices did not change on June 1, and code completions plus Next Edit Suggestions stay included without touching credits. Individual plans (Pro, Pro+, and the newer Max tier) run on the same credit logic at smaller scale; if you’re comparing the whole ladder including personal tiers, our GitHub Copilot cost guide covers every plan, so we won’t re-walk that ladder here.

One disambiguation before anything else, because the search data says people genuinely mix this up: copilot enterprise pricing can mean two entirely different Microsoft products. This article covers GitHub Copilot, the coding assistant. Microsoft 365 Copilot (the Office one) and Copilot Studio are separately priced products, and if that’s what you’re pricing, start with our Copilot Studio pricing guide instead. Even Accenture illustrates the confusion: alongside its GitHub Copilot rollout, it began rolling out Microsoft 365 Copilot to roughly 743,000 employees in April 2026, the largest Copilot deployment Nadella has cited. Same brand name. Different product. Different bill.

What are GitHub AI Credits, and how do they actually burn?

A GitHub AI Credit is one cent of AI usage. Every chat message, agent session, and code review consumes credits based on tokens processed (input, output, and cached) priced at the listed rate of whichever model handled the work.

That last clause is where budgets go to get surprised. The silent multiplier isn’t the model list price; it’s the shape of the work. Agent sessions re-read repositories, retry failed steps, and carry context windows that would embarrass a novel, and every one of those tokens meters. A quick completion is nearly free. A long agentic session can consume more compute than a month of autocomplete. Under the old premium-request system, both looked like “requests.” Under credits, they cost what they cost.

To make that concrete with illustrative math: take a frontier model priced around $3 per million input tokens and $15 per million output. A single ambitious agent session that chews through 4 million input tokens (repository context, retries, re-reads) and produces 400,000 output tokens costs about $12 plus $6, so roughly $18, or 1,800 AI Credits.

One session. Nearly half of one Enterprise seat’s monthly $39 allotment, burned in an afternoon by one engineer who was, to be fair, being extremely productive. Now multiply by a platform team that runs ten of those a week, and notice that the same team on autocomplete-only usage would have consumed almost nothing. That spread between the lightest and heaviest user is the entire story of usage-based Copilot, and no seat count anywhere in your contract predicts it.

Two mechanics that decide whether your forecast survives September (a third, Copilot code review consuming GitHub Actions minutes on top of credits, is covered with the other hidden costs in our full Copilot cost guide):

Why did GitHub do this? Because Copilot stopped being an autocomplete tool. It’s an agentic platform running long, multi-step coding sessions, and those sessions consume radically different compute than a tab-complete. GitHub’s framing in its community FAQ is candid: the product “is not the same product it was a year ago.” On the economics, they’re right, and it’s the same shift every AI tool is making. Flat-rate AI subscriptions are dying industry-wide because token costs are real; the same logic drives per-token pricing at OpenAI, Anthropic, Google, and usage tiers in Claude Code. June 2026 is simply the month AI coding officially became a metered utility.

What happens to Copilot credits on September 1, 2026?

Direct and time-sensitive: the training wheels come off. To smooth the transition, GitHub gave existing Business and Enterprise customers promotional included usage for June, July, and August 2026: 3,000 credits per Business seat and 7,000 per Enterprise seat. Standard allotments are 1,900 and 3,900 credits, since a credit is a cent. So on September 1, Enterprise pools shrink 44% and Business pools shrink 37%, with no change to the seat price and no change to how your engineers work.

Which means most Enterprise admins have not yet seen their real bill. June, July, and August usage has been landing on a subsidized pool. September is when actual consumption meets actual allotments, right as teams return from summer and agentic usage climbs. If your organization adopted agent workflows enthusiastically over the summer, the first honest invoice arrives in early October, about the same week as planning season.

The preparation is unglamorous and takes an afternoon: pull June and July usage from GitHub’s billing reports, recompute it against standard (non-promotional) credit levels, and find out today whether you’re a within-pool organization or an overage organization. While you’re in there, sort usage by team and flag your top ten consumers, because September’s conversation goes very differently when it opens with “we know exactly where the credits go” instead of “we’re looking into it.” GitHub has said usage reports were made available specifically so customers could prepare.

The organizations that skip this step will discover their category from the invoice. In CloudZero’s 2026 AI ROI research, a survey of 260 finance leaders fielded in June 2026, 29% said limited visibility into AI spend had already forced them to reallocate budget to cover overruns.

Copilot Enterprise vs. Business: which one, and when?

GitHub Copilot Enterprise vs. Business used to be a features question. It still is, but the credit math added a wrinkle worth understanding before you assign tiers.

The features case for Enterprise: codebase-aware chat grounded in your repositories, Copilot integrated across github.com, and knowledge-base capabilities Business doesn’t get. Teams living in large, mature codebases feel the difference; a 20-person startup mostly won’t.

The credit wrinkle: Enterprise seats contribute $39 per user to the pooled credits, Business seats contribute $19. So the tier decision now also sets the size of your usage cushion. An organization of heavy agentic users on Business hits overage territory at roughly half the consumption an Enterprise pool absorbs, which means some teams will find Enterprise’s bigger included pool quietly narrows the effective price gap. Run your own usage against both pools before assuming Business is the cheap option; for genuinely heavy users, it sometimes isn’t.

Mixed assignment is allowed and usually right: Enterprise seats for the platform teams living in agent workflows, Business for everyone else. The pool doesn’t care about job titles, but your CFO will care that the blended rate matches reality.

How should engineering leaders budget for Copilot now?

The honest answer: the way you budget for cloud infrastructure, because that’s what this is now. Seat-based tools get budgeted once a year with a headcount multiplier. Metered tools need drivers, ranges, and someone watching the meter. Four principles that survive contact with usage-based reality:

Forecast drivers, not invoices. Your Copilot cost drivers are now: number of active users, share of usage that’s agentic versus completion, model mix, and context size habits. The roadmap matters too; rolling out agent-based code review to 500 more engineers is a cost event, and it belongs in the forecast the day it’s planned, not the month it’s billed.

Budget the pool, then watch its distribution. The pooled design means your real exposure is concentration: a handful of power users or one enthusiastic automation can dominate consumption. Whoever owns the budget needs to see usage by team and by workflow, not just the org-level total GitHub’s invoice shows.

Set the overage trigger in writing. Decide now what happens when consumption crosses the included pool: who gets notified, at what threshold, and what the approved response is (rebalance model defaults, cap agent concurrency, or deliberately fund the overage because the productivity math supports it). An overage with strong per-engineer economics is a success signal; an overage nobody can explain is a leak. The trigger’s job is telling those apart before finance asks.

Treat September 1 as a fiscal event. Put it on the calendar next to renewal dates. Recompute August usage at standard allotments. Walk into Q4 knowing the number instead of meeting it.

None of this is exotic. It’s the discipline cloud spend taught the industry over a decade, now arriving at the AI coding line item on a compressed schedule, with less tooling and higher velocity.

What does usage-based Copilot pricing mean for engineering budgets?

Watching this from a platform that’s metered usage-based spend for a decade: June 1, 2026 was the day AI coding tools stopped being SaaS and became infrastructure, and most companies’ tooling hasn’t noticed yet.

A seat-priced tool needs a spreadsheet once a year. A metered tool needs telemetry, attribution, and forecasting, and Copilot is now one meter among several. The realistic enterprise stack in 2026 runs GitHub Copilot next to Claude Code or Cursor, direct API usage against OpenAI and Anthropic, and Amazon Bedrock or Azure OpenAI workloads in the cloud bill, each with its own billing model, none visible from the others’ consoles.

The Copilot question (“what will our token consumption cost above the pool?”) is the same question in five uniforms, answering it per-tool in five dashboards is why, in our 2026 research, most finance leaders reported holding back AI investment for lack of spend data. Not for lack of budget. For lack of visibility.

That’s the problem CloudZero exists for. One financial control plane ingests all of it: Copilot spend beside Bedrock, OpenAI, Anthropic, and the cloud bills underneath, with GitHub itself as a native connector.

Dimensions attribute AI coding spend to the teams, initiatives, and products it served, so “who drank the credit pool” has an answer with a name on it.

Anomaly detection on hourly data catches the runaway agent the day it starts recursing, not on the invoice.

Budgets with triggers turn the September cliff from a surprise into a threshold you already wrote a response for. And the part that closes the loop: the AI Hub surfaces those cost answers inside the coding agents themselves, Copilot included, so the engineer mid-session and the finance leader mid-forecast are reading the same meter. Duolingo’s engineers describe what changes when this visibility exists in our case study: cost stops being finance’s private anxiety and becomes a normal engineering metric.

The bigger picture, and the reason we’d make this argument even if we sold nothing: the companies that win the AI coding era won’t be the ones that capped their engineers’ usage hardest or negotiated the cleverest seat discount.

They’ll be the ones that can see, per team and per workflow, what the tokens bought, because that’s the only position from which “should we spend more on this?” has an honest answer. GitHub just made Copilot’s costs legible at the token level. The remaining work is making them legible at the business level, and that part was never GitHub’s job.

See your whole AI coding spend in one place: book a demo today.

Frequently asked questions about GitHub Copilot Enterprise pricing

Author Spotlight

Lyne Carolyne

Lyne Carolyne has several years of experience in AI and cloud economics and brings that understanding into the content she creates. Outside work, she's an avid explorer.