GitHub Enterprise Editions and Seat Pricing
GitHub Enterprise licensing starts with the platform seat, but the seat is deliberately the cheapest component. GitHub Enterprise Cloud (GHEC) lists at $21 per user per month, billed at $231 per user per year, and that covers the hosted platform, organisation management, SAML single sign-on and audit logging. GitHub Enterprise Server — the self-hosted edition — is licensed under the same per-user model but settles metered add-ons through a linked GHEC account. The figure most enterprises budget against is this $21 seat. The figure they actually pay is two to four times higher once security and AI are layered on.
The reason matters for procurement. GitHub's commercial design pushes the platform seat to a low headline number and recovers margin through consumption add-ons — Advanced Security, Copilot, and GitHub Actions minutes — that each meter on a different basis. A licensing position that only counts seats will understate true cost by a wide margin, and our engagement data shows GitHub Enterprise bills routinely overshoot the original budget by 28% to 65% within 18 months as those add-ons stack. Understanding each meter is the precondition for controlling the bill.
The Per-Committer Advanced Security Trap
GitHub Advanced Security (GHAS) is the single most misunderstood charge in GitHub Enterprise licensing. It is not billed per seat. It is billed per active committer — any developer whose commit has been pushed, within the last 90 days, to a repository where an Advanced Security feature is switched on. The 90-day window means a contractor who pushed one commit a quarter ago still consumes a licence today.
As of April 2025, GitHub split the old unified $49 GHAS product into two separately-billed components: Code Security at $30 per committer per month and Secret Protection at $19 per committer per month. Enable both across the estate and you are back to $49 per committer — but many enterprises now buy them separately, which is a genuine saving when only secret scanning is required. The metered model carries no licence cap and "no overage state": spend simply rises as the feature is enabled on more repositories. Turn GHAS on at the organisation level across 600 repositories and every active committer touching any of them is billed, whether or not that repository needed scanning.
The most common GHAS overspend is structural, not negotiated: Advanced Security enabled organisation-wide rather than on the repositories that hold production or sensitive code. Scoping GHAS to the repositories that actually require it — not the whole estate — is frequently a 20–30% reduction in security spend on its own.
Copilot Business vs Enterprise: Right-Sizing the Tier
GitHub Copilot is now the fastest-growing line in most developer-tooling budgets, and the choice between tiers is where the money is. Copilot Business is $19 per user per month. Copilot Enterprise is $39 — and, critically, it requires GitHub Enterprise Cloud, so its effective cost is closer to $60 per developer once the GHEC seat is included. Copilot Enterprise adds knowledge bases, pull-request summaries and priority access to new models, but most engineering teams capture the bulk of the day-to-day productivity benefit on Business.
Right-sizing the Enterprise tier down to the population that genuinely uses the differentiated features is one of the largest single savings available in a GitHub estate; in one engagement, a technology company cut combined GitHub Enterprise and GHAS spend by $680K a year through a mix of active-committer caps, self-hosted runner architecture, and exactly this Copilot Business-versus-Enterprise right-sizing. A further change is coming: from 1 June 2026 all Copilot plans move to usage-based billing, where each plan includes a monthly allotment of GitHub AI credits and consumption is metered on input, output and cached tokens. That shift makes seat-tier discipline and credit-allotment forecasting even more important, because variable token consumption replaces the predictable flat seat fee. The same dynamic plays out across Microsoft's wider AI portfolio — our analysis of Azure OpenAI Service pricing and enterprise terms covers the token-based commercial model in detail.
Routing GitHub Through Your Microsoft EA
Because GitHub is a Microsoft company, GitHub Enterprise can be purchased through a Microsoft Enterprise Agreement amendment rather than standalone from GitHub's sales team. This is not automatic, and GitHub's direct sales motion will not volunteer it — you have to explicitly request that GitHub pricing be routed through your EA relationship manager. When it works, EA-routed GitHub pricing typically runs 15–25% better than a standalone GitHub negotiation, because it draws on the leverage of the broader Microsoft commercial relationship and the same quarter-end incentives that drive every Microsoft renewal.
The mechanics connect directly to the rest of your Microsoft estate. Identity for GitHub SSO usually flows through Entra ID, so the entitlement model interacts with your Entra ID licensing tiers; and where teams run pipelines across both platforms, the licensing overlaps with Azure DevOps licensing. Treating GitHub, Azure DevOps and Entra as one developer-platform negotiation — rather than three separate purchases — is exactly the integrated approach set out in our advanced Microsoft licensing guide, and it is where the leverage compounds. For a deeper view of the Microsoft commercial relationship, see the Microsoft vendor intelligence hub.
The Negotiation Levers That Cut GitHub Spend
Four levers move GitHub Enterprise cost reliably. First, negotiate a fixed monthly cap on active-committer billing — converting an uncapped consumption charge into a predictable, budgetable number is often worth more than a headline discount. Second, scope Advanced Security to the repositories that require it rather than the whole organisation. Third, right-size Copilot tiers and forecast the post-June-2026 AI-credit allotment before committing seats. Fourth, route the whole purchase through the EA. Across our portfolio these moves produce a median identified saving of 24% on the combined GitHub bill.
GitHub spend rarely gets the same scrutiny as a core Microsoft 365 or Azure renewal, yet it grows faster than either. If your GitHub Enterprise, Advanced Security and Copilot lines are climbing without a clear cap, request a confidential briefing and we will benchmark your current terms against comparable enterprises. For the wider playbook on the Microsoft commercial relationship, download the Microsoft Enterprise Agreement Guide.