GitHub Licensing Guide
GitHub Enterprise licensing. The 2026 buyer guide.
GitHub Enterprise looks simple and rarely is. Seats are per user, but Copilot and Advanced Security layer cost on top. Here is the model and the buyer side moves.
GitHub Enterprise looks simple and rarely is. Seats are per user, but Copilot and Advanced Security layer cost on top. Here is the model and the buyer side moves.
GitHub Enterprise is licensed per user, but Copilot, Advanced Security, and Actions minutes layer consumption on top and dormant seats accumulate quietly across a large estate.
GitHub Enterprise looks simple to license and rarely is. Seats are sold per user, but Copilot, Advanced Security, and Actions minutes layer consumption on top, and inactive seats accumulate quietly across a large developer estate.
Buyers overpay by leaving dormant seats live and by switching on add ons estate wide. This guide covers the model, the leaks, and the buyer side moves at renewal.
GitHub Enterprise is licensed per user, in either the cloud or self managed form. The base seat covers the platform, and most cost growth comes from add ons.
GitHub Enterprise Cloud is hosted by GitHub, while GitHub Enterprise Server runs in your own environment. Both price per user. The editions are described on the GitHub Enterprise page.
A seat is consumed by any user who is a member of the enterprise. Published seat pricing sits on the GitHub pricing page, and billing mechanics are documented in the GitHub billing docs.
Copilot adds a separate per user subscription on top of the seat, and it is the fastest growing line on most GitHub bills. It is licensed in Business and Enterprise tiers.
Copilot Business and Copilot Enterprise add per user fees with different feature sets. The tiers are described on the GitHub Copilot page.
Copilot is often bought for all developers and actively used by a fraction. Measure real usage before renewing the full seat count.
Spend leaks through dormant seats, estate wide add ons, and uncapped Actions minutes. Each is easy to fix once measured.
Where GitHub Enterprise spend leaks
| Leak | Cause | Buyer side fix |
|---|---|---|
| Dormant seats | Leavers and inactive members | Quarterly seat reconciliation |
| Copilot over buy | Bought for all, used by some | License Copilot by active use |
| Advanced Security | Enabled estate wide | Scope to repositories that need it |
| Actions minutes | Uncapped CI runs | Set budgets and runner policy |
The largest single leak is usually Copilot bought for the whole organization. Usage data almost always supports a smaller, renewable count.
GitHub Advanced Security is valuable but priced per committer. Enabling it estate wide rather than by repository scope inflates the committer count.
Negotiate on a clean seat count and measured add on usage, timed to the renewal. The published seat price is firm, so the leverage is in count accuracy and add on scope.
Remove leavers and inactive members before the renewal count is set. A quarterly reconciliation keeps the baseline honest.
Treat Copilot and Advanced Security as separate negotiations with their own usage cases. Do not let them ride along on the seat renewal unexamined.
The common advice is to license Copilot for every developer because the productivity upside justifies near universal coverage. We disagree. In the GitHub estates we reviewed across 2024 and 2025, actual Copilot engagement clustered well below the licensed seat count, often in the 40 to 60 percent range of assigned users. The reason is that adoption is uneven and habit driven, not automatic. The buyer side move is to license Copilot to demonstrated active use, review it each quarter, and expand the count as adoption proves out, rather than paying for universal coverage that the usage data does not support.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The GitHub seat price is fixed. The savings live in the seat count and in licensing Copilot to use, not to hope.
White Paper · Microsoft
The 12 month buyer side framework we use with Fortune 500 clients to cut the standard Microsoft EA uplift. Read it free.
GitHub Enterprise is licensed per user, in either the cloud hosted or self managed server edition. The base seat covers the platform, and most cost growth comes from add ons like Copilot and Advanced Security.
Add ons drive most growth, especially Copilot and Advanced Security, along with uncapped Actions minutes. The base per user seat is comparatively stable.
Copilot is a separate per user subscription in Business and Enterprise tiers, layered on top of the seat. It is often bought for all developers but actively used by a fraction.
Not at first. Actual engagement usually sits at 40 to 60 percent of assigned seats, so license to demonstrated use, review quarterly, and expand as adoption proves out.
GitHub Advanced Security is priced per committer. Enabling it estate wide rather than scoping it to the repositories that need it inflates the committer count and the bill.
The biggest leaks are dormant seats from leavers and Copilot bought for the whole organization. Both respond to a quarterly reconciliation against real activity.
The published seat price is fairly firm, so the leverage is in count accuracy and add on scope rather than headline discount. Clean the count before the renewal.
Begin a quarter ahead. That leaves time to reconcile seats, pull Copilot usage, and scope Advanced Security before the count is set.
The seat reconciliation checklist, the Copilot adoption model, and the add on scoping template the buyer side uses on GitHub Enterprise renewals.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Developer tooling spend rarely fails on price. It fails on seats nobody reconciled and add ons nobody measured.
