GitHub Enterprise now includes Copilot with no seat charge, and bills every AI request from the first

What GitHub announced on 28 October

At GitHub Universe on 28 October 2026, GitHub said that enterprises working with a GitHub or Microsoft account team can now have GitHub Copilot included with GitHub Enterprise for every licensed user. There is no Copilot seat charge for anyone who holds a GitHub Enterprise Cloud licence.

What replaces the seat is a meter. In the changelog’s words, usage is billed against the enterprise budget from the first request, and "There is no included usage allowance to track or top up." The access carries the same features and model eligibility as Copilot Enterprise, without the monthly AI credits that a Copilot Enterprise seat includes.

The keynote post by Jay Parikh put it more briefly: enterprise customers get all Copilot features without a separate Copilot subscription, and "You pay for the AI credits you use."

The four ways to buy Copilot for a company now

GitHub’s individual plans page states that AI credits draw down at $0.01 each. On that rate, the 1,900 credits in a Business seat are worth $19 and the 3,900 in an Enterprise seat are worth $39: each seat price buys its own value in usage. That equivalence is the key to the arithmetic later in this piece.

Availability

It is available now for GitHub Enterprise Cloud customers with an account team, both for new enterprise accounts and for existing ones that transition. Self-serve customers cannot have it yet; GitHub says the rollout will be staged and dates will be shared in the coming weeks. Organisations on GitHub Free or GitHub Team, and self-service Enterprise Cloud trials, are not eligible. Copilot Business and Copilot Enterprise remain on sale to new and existing enterprises, and nobody is moved automatically.

From seats to budgets: what actually changed

A Copilot Business seat was a fixed monthly price that came with a pooled allowance. The new model removes the fixed price and the allowance together. What a company pays becomes what its developers use, metered from the first credit.

What still works when the budget runs out

This is the most carefully designed part of the announcement and it deserves credit. When the budget is exhausted, code completion and next edit suggestions keep working, because they do not consume credits. Copilot Chat, Copilot code review and the Copilot cloud agent need available budget and stop until there is some. The changelog states it plainly: "An exhausted budget never removes access." The seat stays, and so do the features that do not draw on the meter.

That gives every developer a free floor of inline assistance, and makes the agentic and conversational features the metered layer. It is the same shape Atlassian chose when it kept search and summaries free and began metering Rovo, automation and agents from 3 December: the everyday feature stays unmetered and the expensive one is billed per use.

Why "no seat charge" is the vendor’s framing

It is true that the seat now costs nothing. It is also true that the seat was never really the product. A Business seat at $19 bought 1,900 credits worth $19 at the published rate, so the seat price was largely a prepayment for usage. Removing it removes the prepayment, not the cost of using the tool.

What changes for GitHub is that every licensed Enterprise user is now a potential paying Copilot user without a separate purchasing decision. Revenue scales with use rather than with seats sold. That is a sensible model for a product whose cost to supply varies enormously between a developer who accepts a few completions and one who runs agents all day, and it is the pattern we described in how AI tiers are reshaping renewals. It is not a giveaway.

No floor, and no ceiling unless you set one

Under seats, the minimum and the expected cost were close together and known a year ahead. Under a budget, the minimum is zero and the maximum is whatever the budget allows. GitHub’s budget documentation states that the setting "Stop usage when budget limit is reached" is off by default, and that without it charges keep accruing with no cap. The same page advises enabling it whenever a budget is created. An enterprise that switches and does nothing else has an open meter.

Who pays less, and who pays more

At list prices, and assuming metered credits are billed at the $0.01 GitHub publishes, the comparison for a user who already holds a GitHub Enterprise licence is simple. Under Copilot Business, a team pays the larger of its seat total and its usage. Under the new access, it pays only its usage. The new model cannot cost more at list prices; at worst it costs the same.

A 100-developer enterprise, three usage levels

These are illustrations at published rates, not quotes. Enterprise agreements are negotiated, and a discounted Business seat changes the comparison. Ask the account team for both models priced on your own usage before deciding.

Who comes out ahead

• Enterprises with uneven adoption. Under seats, every licensed developer who rarely opens Copilot Chat still costs $19. Under access, they cost what they use, and they keep completions for nothing.
• Enterprises paying for Copilot Enterprise. Access carries the same features and models as Copilot Enterprise, without the $39 floor.
• Teams that want to trial agents widely. Turning Copilot on for everyone no longer requires a seat purchase per person.

Who comes out behind

• Finance teams that valued a fixed number. A cost that was known at renewal becomes a monthly variable. The saving is real, but it has to be managed to stay a saving.
• Heavy users on Copilot Standalone. Standalone costs $10 plus usage, against $19 including $19 of usage for Business. Per person, Standalone is cheaper only below $9 of monthly usage; above $19 it costs $10 more than Business, every month.
• Mixed estates. GitHub’s documentation says Copilot access cannot be combined with Business or Enterprise seats in the same enterprise, including within individual organisations. An enterprise cannot keep Business for its heaviest users and move everyone else.
• Smaller customers. GitHub Free and GitHub Team organisations are not eligible, and self-serve Enterprise customers have no date.

How to set the budgets before anyone uses it

Because there is no included pool, the configuration has to be in place before the first credit is spent. GitHub’s guidance is to set budgets before first use, using a cost estimate as the baseline and allowing for growth.

Enable paid usage deliberately

With no shared allowance, the "AI credits paid usage" policy in AI Controls must be on for any credit-consuming feature to work. GitHub says it is on by default. Confirm it is on, and confirm who can change it.

Set an enterprise budget, and turn the stop on

The enterprise budget limits total metered charges across the enterprise. It does not cap licence fees. Without the stop setting, reaching it sends alerts and spending continues; with it, users are blocked from credit-consuming features once it is exhausted. Decide which you want and write the decision down, because the person reading the invoice is rarely the person who configured it.

Give each team a cost centre budget

Cost centre budgets limit a team’s metered charges from the first metered use, and can carry the same stop setting. They let a platform team running agents all day have a different limit from a team that mostly uses completions. A cost centre can also be excluded from the enterprise budget, so that a critical team is never blocked by everyone else’s usage; its spending is then capped only by its own budget.

Use user-level budgets for the long tail

User-level budgets cap one person’s consumption per billing cycle and always hard-stop. They come in three forms, and the most specific applies: an individual budget, a cost centre default, and a universal default for every licensed user. A modest universal budget, with individual exceptions for the people who need more, is the simplest way to keep one runaway agent session from consuming a team’s month.

Know what blocked means

Blocked users stay blocked until the next billing cycle, until an administrator raises the budget, or until a budget request is approved. Completions and next edit suggestions continue throughout. Tell developers this in advance, so a blocked chat on the 24th of the month reads as a budget decision rather than an outage.

If you already pay for Copilot Business or Enterprise

Nothing changes unless you ask for it, and the announcement says nothing about the price of the GitHub Enterprise licence itself. Moving is voluntary, existing Business and Enterprise enterprises are not transitioned automatically, and GitHub says contacting the account team does not by itself change access or billing.

What a transition involves

• Timing. Transitions take effect on the first day of a month, confirmed with the account team.
• All or nothing. Because access and Business or Enterprise seats cannot coexist in one enterprise, the whole enterprise moves together.
• Seat assignment still applies. Copilot access must still be assigned to members, teams or organisations, even for users who hold an Enterprise licence.
• Network allowlists. On GitHub.com, Copilot access uses the Copilot Enterprise endpoint. An allowlist that only permits *.business.githubcopilot.com needs *.enterprise.githubcopilot.com added, or access will be interrupted.

How to decide

Export three months of AI credit usage per user and model both options against it. If pooled usage regularly sits below the seat total, access is cheaper at list prices. If it regularly exceeds the pool, the two cost the same and the decision is about predictability and administration rather than price. If you have Business seats at a negotiated discount, the answer depends on the discount, and only your own numbers will settle it.

If you have people outside the Enterprise licence who use Copilot heavily, price them on Standalone separately. At $10 plus usage, a heavy user costs more there than on a Business seat, and the enterprise cannot mix the two.

Does this change the case for the alternatives?

For an organisation already on GitHub Enterprise, it narrows the case considerably. Copilot is now available to every licensed developer without a purchasing decision, and the inline features cost nothing. A competing assistant has to justify a separate contract against a tool that is already switched on.

It does not settle the question for heavy agentic use, where the cost is the usage rather than the seat on every product. That is where the comparison still deserves real work.

• Cursor remains the main editor-first alternative; see Cursor vs GitHub Copilot. Its change of ownership this year is covered in what SpaceX owning Cursor means for teams.
• Claude Code suits teams that work in the terminal and run long agentic tasks; compare it in Claude Code vs GitHub Copilot and check its pricing on the same usage assumptions.
• GitLab Duo is the natural comparison for teams on GitLab, where the platform question decides the assistant question; see GitHub vs GitLab.
• JetBrains AI is the in-house option for teams on JetBrains IDEs such as IntelliJ IDEA.

Other assistants, including Windsurf and Amazon Q Developer, are on the GitHub Copilot alternatives page and in the developer tools category. Whichever you compare, compare the cost of a month of your real usage, not the headline seat price, because every serious option is now metered somewhere.

What to watch next

Three things will decide whether this is as good for buyers as the headline suggests.

• The self-serve dates. GitHub has promised a staged rollout without dates. Until then, the offer is for customers with an account team.
• Credit consumption per feature. The value of a budget depends on what each request costs. New tiers such as the deeper Copilot code review option announced at Universe are worth tracking in the usage report rather than assumed.
• Whether the free floor stays free. Completions and next edit suggestions are unmetered today. That is what makes "no seat charge" mean something, and it is a product decision rather than a contractual one.

None of these is a prediction. Each is cheap to check monthly, and checking is what turns a variable cost into a managed one.

Questions people ask

Is GitHub Copilot free with GitHub Enterprise now?

The seat is. From 28 October 2026, users with a GitHub Enterprise Cloud licence have no Copilot seat charge. Usage is not free: there is no included allowance, so chat, code review and the cloud agent are billed against the enterprise budget from the first request. Code completion and next edit suggestions do not consume credits.

What happens when the Copilot budget runs out?

Code completion and next edit suggestions keep working and the user keeps their seat. Copilot Chat, code review and the cloud agent need available budget and stop until the next billing cycle, a budget increase or an approved budget request. GitHub says an exhausted budget never removes access.

What is Copilot Standalone and how much does it cost?

Copilot Standalone is the same Copilot access for people in an enterprise account who do not hold a GitHub Enterprise licence. It costs $10 per user per month and includes no AI credits, so usage is billed from the first request on top of the $10.

Is Copilot Business being discontinued?

No. Copilot Business at $19 per user per month with 1,900 pooled credits, and Copilot Enterprise at $39 with 3,900, remain available to new and existing enterprises. Existing customers are not moved automatically and can transition when ready through their account team.

Is Copilot access cheaper than Copilot Business?

At list prices, for users who already hold a GitHub Enterprise licence, it cannot cost more. A Business seat at $19 includes $19 of credits at the published $0.01 rate, so Business costs the greater of seats and usage, while access costs usage alone. Negotiated discounts can change this, so model both on your own usage. See GitHub Copilot pricing.

How do I stop Copilot usage costs running away?

Set an enterprise budget and turn on "Stop usage when budget limit is reached", which GitHub documents as off by default. Add cost centre budgets per team and a universal user-level budget, which always hard-stops, with individual exceptions where needed.

When can self-serve GitHub Enterprise customers get Copilot included?

Not yet. As of 29 October 2026 it is available only through GitHub or Microsoft sales for GitHub Enterprise Cloud. GitHub says self-serve rollout will be staged, with dates to follow in the coming weeks. GitHub Free and GitHub Team organisations are not eligible.

Sources

Every price, limit and date above was checked against these pages on the day shown. Where a figure has since moved, the vendor’s own page is the authority and this one is a snapshot.

1. 1GitHub Enterprise now includes access to GitHub Copilot · GitHub ChangelogPrimary. No seat charge, no included allowance, what works on an exhausted budget, Copilot Standalone at $10 and availability.Checked 29 October 2026
2. 2GitHub Universe 2026: Evolving every layer of the stack · The GitHub BlogThe Universe keynote post: Copilot without a separate subscription, paying for AI credits used, and existing plans continuing.Checked 29 October 2026
3. 3What’s changing with GitHub Enterprise and Copilot · GitHub DocsBusiness and Enterprise seat prices and pooled credits, eligibility, the rule against mixing models, transition timing and the network endpoint.Checked 29 October 2026
4. 4Budgets for usage-based billing · GitHub DocsBudget levels, the stop setting and its off default, user-level budgets and what blocked means.Checked 29 October 2026
5. 5GitHub Copilot plans · GitHubThe $0.01 per AI credit rate used for the cost comparisons.Checked 29 October 2026