GitHub Enterprise now includes Copilot: when it costs less

GitHub announced on Oct. 28, 2026, that enterprises working with a GitHub or Microsoft account team can now get Copilot included with GitHub Enterprise Cloud, with no Copilot seat charge for licensed users. Users without an Enterprise license can get the same access as Copilot Standalone for $10 a month. The decision is whether moving off Copilot Business or Copilot Enterprise seats lowers your bill, because the new model drops the included AI credits and meters usage from the first request.

The catch is the allowance. A Copilot Business seat costs $19 a month and includes 1,900 AI credits; Copilot Enterprise costs $39 and includes 3,900. Under the new "Copilot access" model, there is no seat charge for Enterprise Cloud users and no included credits. Teams that use less than their pooled allowance save money. Teams that already burn through it pay about the same, and the switch adds budget work either way.

What changed with GitHub Enterprise and Copilot?

GitHub Enterprise Cloud licenses can now carry Copilot at no extra seat cost, with all AI usage billed against the enterprise budget. GitHub's changelog says Copilot access "has the same features and models as Copilot Enterprise but does not include monthly AI credits per seat," and that "AI usage is metered from the first request against your enterprise budget."

The GitHub Docs comparison sets the three options side by side:

Scroll sideways to see all 3 columns.

Billing model	Seat charge per user per month	Included AI credits
Copilot Business	$19	1,900 per user, pooled
Copilot Enterprise	$39	3,900 per user, pooled
Copilot access with a GitHub Enterprise Cloud license	$0	None
Copilot access as Copilot Standalone (no Enterprise Cloud license)	$10	None

One AI credit equals $0.01, according to GitHub's usage-based billing docs. So the 1,900 credits in a Business seat are $19 of usage, the same as the seat price.

How Copilot access billing works

Every request that consumes credits is charged from the first use, and your budgets are the only ceiling. Under Business and Enterprise, usage draws from the pooled allowance first, and spending limits apply only after the pool is exhausted. Under Copilot access, GitHub's billing docs say "spending limits apply from the first metered use."

Not everything is metered. Inline code completions and next edit suggestions are not billed in AI credits and keep working with a $0 budget. Copilot Chat, Copilot code review, and Copilot in the cloud need available budget. GitHub's billing docs also list Copilot CLI, Copilot Spaces, Spark, and third-party coding agents as credit-consuming features. The changelog states that "an exhausted budget never removes access": the seat and the unmetered features stay.

Is Copilot included with GitHub Enterprise cheaper than Copilot Business?

For users who already hold an Enterprise Cloud license, Copilot access never costs more than Business or Enterprise seats at list prices, and it saves money whenever your team uses less than its pooled allowance. This is BaristaLabs arithmetic from GitHub's published prices, not a GitHub statement:

• Licensed users vs Copilot Business. Business costs $19 per user plus any usage beyond the pool. Copilot access costs only the usage. If your team's average monthly usage is below 1,900 credits per user, you save the difference. At or above that level, the two cost the same.
• Licensed users vs Copilot Enterprise. The same logic applies with a $39 seat and 3,900 credits, so light Enterprise users save up to $39 per user a month.
• Standalone users vs Copilot Business. $10 plus usage beats a $19 Business seat only when average usage stays below 900 credits ($9) per user. Above 1,900 credits, Standalone costs $10 per user more.
• Standalone users vs Copilot Enterprise. Standalone is cheaper below an average of 2,900 credits ($29) per user, and $10 more above 3,900.

An illustrative example: 20 developers with Enterprise Cloud licenses on Copilot Business get a pool of 38,000 credits ($380) a month. If they use 25,000 credits, Business costs $380 and Copilot access costs $250. If they use 50,000 credits, both come to $500. GitHub's docs add that account-specific pricing and migration terms come from your account team, so treat these list-price figures as a starting point.

Who can switch, and what the move requires

Right now, only enterprises with a GitHub or Microsoft account team can move. GitHub Docs say self-serve customers are "currently unavailable," with dates promised "in the coming weeks," and the model is not open to organizations on GitHub Free or GitHub Team or to self-service Enterprise Cloud trials. Copilot Business and Copilot Enterprise stay on sale, and nobody is moved automatically.

The docs list several constraints worth reading before a sales call:

• One model per enterprise. You can mix Enterprise Cloud users and Standalone users, but you "cannot combine Copilot access with Copilot Business or Copilot Enterprise seats in the same enterprise, including in individual organizations."
• Seats still need assigning. Enterprise Cloud users do not get Copilot automatically; owners assign it to members, teams, or organizations.
• The paid-usage policy must stay on. The "AI credits paid usage" policy is enabled by default, and with no included allowance, disabling it blocks every credit-consuming feature.
• Firewall allowlists may need an update. Copilot access uses the Copilot Enterprise endpoint, so an allowlist that permits only *.business.githubcopilot.com needs *.enterprise.githubcopilot.com added.
• Timing. Transitions take effect on the first day of a month.

Why it matters for engineering leads

BaristaLabs' reading: the new model rewards teams with uneven Copilot use. Under seats, every license prepays $19 or $39 of usage whether or not the developer touches Chat or the cloud agent. Under Copilot access, light users who mostly rely on completions cost close to nothing, while heavy agent users cost what they consume. The price of that flexibility is that budgets stop being optional. GitHub's docs say user-level budgets "always enforce a hard stop," which makes them the main tool for keeping one long agent session from setting the month's bill.

It also changes who your Copilot users are. Enterprise Cloud seat holders who never had Copilot because of the $19 to $39 cost can now get it for the price of their usage. If you already route Copilot budget increase requests through an approver, that process becomes the main control. Teams that limit which models Copilot users can reach will find model policy matters more when every request is metered, and the lesson from Copilot dynamic workflows and credit limits applies here too: a paused task does not reset the budget.

Run the numbers before you call your account team

BaristaLabs recommends a short cost check before requesting a transition, following the method in GitHub's docs:

1. Pull last month's real usage. Use your AI usage dashboard or export, and count the usage covered by your pooled allowance, not only the overage you paid for. GitHub's docs call this out explicitly.
2. Split your users. Count who holds an Enterprise Cloud license ($0 seat) and who would need Copilot Standalone ($10 each).
3. Compare totals. Add the estimated metered usage and Standalone charges, then compare them with your current seat charges plus overage.
4. Draft budgets before the switch. Set enterprise, cost-center, and user-level budgets from that estimate, since spending limits apply from the first request.
5. Check the allowlist and the policy. Add the enterprise endpoint if needed and confirm the paid-usage policy is enabled.

If you manage your own subscription, run the same numbers now so you can decide quickly when self-serve access opens. Small teams already prepaying self-serve Copilot seats have the most to compare.

Sources and scope

• GitHub changelog, GitHub Enterprise now includes access to GitHub Copilot, Oct. 28, 2026.
• GitHub Docs, What's changing with GitHub Enterprise and Copilot billing, retrieved Oct. 28, 2026 (prices, eligibility, transition steps).
• GitHub Docs, Usage-based billing for organizations and enterprises, retrieved Oct. 28, 2026 (AI credits, metered features, budgets).

The sources give list prices only. They do not state account-specific discounts, the self-serve launch date, or the price of a GitHub Enterprise Cloud license itself, so the savings figures above assume you already pay for those licenses.