Wain AI/Tech Blog

AI news and trends worldwide, updated nearly every day

GitHub Adds "Copilot Access" to Enterprise Cloud Licenses - $0 Seat Charge, Metered From the First Use, Starting With Enterprises That Have an Account Team

GitHub Adds "Copilot Access" to Enterprise Cloud Licenses - $0 Seat Charge, Metered From the First Use, Starting With Enterprises That Have an Account Team

On October 28, 2026, GitHub announced "Copilot access," which gives users holding a GitHub Enterprise Cloud license Copilot with no seat charge. Users without a license pay $10 per month. There is no per-seat AI credit allowance, and usage counts against the enterprise budget from the first request. For now, only enterprises working through an account team are eligible.

On October 28, 2026, GitHub used its Changelog to announce a new arrangement in which Copilot comes bundled with GitHub Enterprise licenses 1. The documentation calls it “Copilot access.” Users who hold a GitHub Enterprise Cloud license pay no Copilot seat charge, and users without that license get the same access as “Copilot Standalone” for $10 per user per month 2.

What disappears is the monthly AI credit allowance that is built into Copilot Business and Copilot Enterprise seats. Every AI request, starting with the first, is metered against the enterprise’s budget 1. GitHub frames the change as moving from two things to track, the number of seats paid for and the AI usage of those seat holders, to one: usage against the enterprise budget. Right now it is open only to enterprises served by a GitHub or Microsoft account team, and no date has been given for enterprises that buy through self-serve.

How the Three Billing Models Compare

Here is the comparison table from the documentation, reorganized 2. All prices are in US dollars.

Billing modelSeat charge per userIncluded AI credits
Copilot Business$19 a month1,900 per user per month (pooled)
Copilot Enterprise$39 a month3,900 per user per month (pooled)
Copilot access$0 for Enterprise Cloud license holders; $10 a month (Copilot Standalone) for unlicensed usersNone

An AI credit is a billing unit worth $0.01. In Business and Enterprise, each user’s allowance goes into a shared pool at the billing-entity level, and unused credits do not roll into the next month 3. Under Copilot access, metered usage is charged from the first use whether a user comes in through an Enterprise Cloud license or through Standalone 2. GitHub says the $10 Standalone fee pays for administrative functions: identity and access, policy, security, and admin controls.

Features and models match Copilot Enterprise, within whatever policies and spending controls administrators set 2. For the wider Copilot price structure, our comparison of AI coding tool pricing covers the Business and Enterprise seat prices and the move to AI credits.

What Still Works When the Budget Runs Out

The Changelog sums up how budget and features relate in three points 1.

  • Code completion and next edit suggestions continue to work even when no budget is left
  • Copilot Chat, Copilot code review and Copilot in the cloud can only be used while budget is available
  • Running out of budget does not take access away; the seat stays, and so do the features that need no budget

In the existing Business and Enterprise plans, too, neither code completions nor next edit suggestions are billed in AI credits 3. The difference lies in features that do consume AI credits, such as Chat and agents. Because Copilot access has no included allowance, usage that a seat’s allowance used to absorb is now billed on a metered basis from the very first request.

Who Can Use It, and When

Availability is rolling out in stages. The current conditions are as follows 2.

  • Enterprises that have a GitHub or Microsoft account team: available on GitHub Enterprise Cloud from October 28, 2026. Their sales team can help either create a new enterprise account under this model or convert an existing one
  • Enterprises that manage their own subscription (self-serve): not available yet. GitHub says it will open access in stages and announce dates in the coming weeks, and existing subscriptions are not affected
  • GitHub Free and GitHub Team organizations, and Enterprise Cloud trials started through self-service: not eligible

Moving is optional; enterprises currently using Copilot Business or Copilot Enterprise will not be switched over automatically. Both plans can still be bought by new and existing enterprises 1. For now, self-serve enterprises will keep using Business or Enterprise.

What to Check Before Considering a Move

The documentation lays out concrete steps for deciding on and preparing for a transition 2.

The two models cannot be mixed in one enterprise. The billing model covers the entire enterprise, so Copilot access cannot sit alongside Business or Enterprise seats within one enterprise, and splitting by organization is not allowed either. The two forms of Copilot access, through an Enterprise Cloud license and through Standalone, can be used together.

Estimate costs including what the allowance currently absorbs. The documentation asks enterprises to estimate the cost of their usage with no allowance, counting usage that the pooled allowance now covers and not just today’s overage charges. Then multiply the number of users who would end up on Standalone because they lack an Enterprise Cloud license by $10, add that to the metered usage estimate, and compare the result with the current monthly bill. Usage data can be drawn from sources such as the AI usage report, which breaks down tokens by model. GitHub asks customers to confirm account-specific pricing and transition terms with their account team.

Seats still have to be assigned. Copilot access does not turn Copilot on for developers by itself. Enterprise owners still have to hand out seats, per member, per enterprise team or per organization, and that includes users with an Enterprise Cloud license.

Review two settings first. One is an AI Controls policy named “AI credits paid usage.” It is on by default and has to stay on for features that consume credits to work. The other is the network allowlist: on GitHub.com, Copilot access is served from the Copilot Enterprise endpoint, so an allowlist that only covers *.business.githubcopilot.com needs *.enterprise.githubcopilot.com added, or access will be cut off.

Existing enterprises request a transition through their account team, and the switch becomes effective on the 1st of a month. Contacting the team changes neither access nor billing, and it does not lock in a transition date.

The Unit of Management Moves From Seats to Budget

Until now, Business and Enterprise worked by having customers pay published rates for usage beyond the AI credit allowance included in the seat charge, provided additional usage was allowed 3. In August, GitHub had also announced billing changes such as seat prepayment. Copilot access can be seen as adding a separate option alongside that structure: drop the seat charge (or reduce it to the $10 Standalone fee for unlicensed users) and bill on usage.

Whether it comes out cheaper likely depends on how usage is spread. In an enterprise where most developers mainly use completions, losing the seat charge matters more, while in one where many developers lean on Chat and agents, usage that the pool used to absorb lands directly on the bill. GitHub’s documentation, too, asks customers to include the portion covered by the allowance when estimating. Enterprises with an account team will want to run the numbers on recent usage before deciding, and self-serve enterprises will be waiting for the dates GitHub says it will share in the coming weeks.

Sources

  1. GitHub Enterprise now includes access to GitHub Copilot - GitHub Changelog (October 28, 2026)
  2. What’s changing with GitHub Enterprise and Copilot billing - GitHub Docs
  3. Usage-based billing for organizations and enterprises - GitHub Docs

We publish the latest AI news nearly every day.

Subscribe via RSS Get new posts the moment they go live.

Search other keywords →