Every GitHub Enterprise conversation starts with the same number: US$21 per user per month (github.com/pricing). It's a real number, and it's also the least interesting one on the bill. For most organizations we work with, the platform licence ends up being roughly a third of what they actually spend on GitHub — the rest is Copilot, security, and compute. This is the honest breakdown, with the math.

Two caveats before the numbers. First, GitHub lists both Enterprise ($21) and Team ($4) with a first-twelve-months qualifier, so treat list prices as an opening position and confirm renewal pricing before a business case depends on them. Second, all figures here are USD list prices as of October 2026 — enterprise agreements negotiate below list, especially on annual commitments.

The platform: $21, and what the $17 jump buys

The gap between Team at $4 and Enterprise at $21 is the most common sticker shock, and it's worth being precise about what sits in it: SAML single sign-on and SCIM provisioning, Enterprise Managed Users, the enterprise account with policies that apply across every organization, audit log streaming, 50,000 Actions minutes a month, and the 99.9% uptime SLA (GitHub's plans). If you need SSO — and at enterprise scale you do — there is no middle tier. The jump is the price of identity and governance, and we've covered what that tier actually is in our plain-English guide to GitHub Enterprise.

One licence covers both deployment models — Enterprise Cloud and Enterprise Server — so where the code lives is an architecture decision, not a pricing one. The cost difference shows up elsewhere, and we'll get to it.

Copilot: the second bill, now metered

Copilot is not included in any GitHub plan. It's a separate seat: Business at $19 per user per month, Enterprise at $39 (Copilot plans). If AI-assisted development is the reason you're buying GitHub Enterprise, your real per-developer platform cost is $40–$60, not $21.

And since June 2026, the Copilot line is no longer flat. GitHub moved Copilot to usage-based billing: premium model usage is metered in AI Credits consumed against published per-model rates, with a monthly credit allowance included in each paid seat and overage billed on top (GitHub blog). Code completions and next-edit suggestions stay unmetered in all plans. The practical consequence:

The Copilot question in 2026 is no longer “what does a seat cost?” It's “what does our usage cost?” — and the answer depends on which models your developers and agents reach for, and how often. Budget it like a cloud service, not like a licence.

The transition's promotional included usage ended on September 1, 2026, so if your Copilot invoices from summer looked comfortable, re-check the autumn ones — that's the first month of steady-state metering for many organizations.

Security: now priced per committer, in two parts

In 2026 GitHub unbundled Advanced Security into two separately purchasable products, priced per active committer rather than per seat: GitHub Secret Protection at $19 per committer per month and GitHub Code Security at $30 (GitHub docs). Two things follow from that.

It's better news than it sounds: you can now buy secret scanning and push protection without paying for the full code-scanning suite, both products are available from the Team plan up, and “per active committer” means read-only users and dormant accounts don't bill. It's also easy to underestimate: $49 per committer per month for both products is more than double the platform licence itself, which is why security scoping — which repos, which committers, which product — is one of the highest-leverage cost decisions in the whole estate.

Compute: the quiet line

Enterprise includes 50,000 Actions minutes monthly on standard hosted runners — generous until a matrix build across four operating systems meets a monorepo. Larger runners, macOS multipliers, and storage bill beyond the allowance, and GitHub's 2026 pricing updates also introduced a small per-minute platform charge on self-hosted runners (around $0.002/min). None of these are big numbers individually; together they're why the Actions line deserves a monthly glance rather than an annual surprise. Confirm the current meters against GitHub's billing docs for your plan.

Cloud vs Server: same licence, different bill

Enterprise Server carries the same $21 licence — what it adds is everything around it: the infrastructure it runs on, backup and DR, and the upgrade obligation, since a Server instance must be upgraded at least annually, forever, to stay in support. That's real operational payroll, not a GitHub invoice, and it's the honest cost difference between the deployment models. When residency or isolation forces Server — as it still does for Canadian data-residency obligations — budget the ops, not just the licence. The full decision is written up in GitHub Enterprise Cloud vs Server.

The worked example

A 50-developer organization on Enterprise Cloud, Copilot Business for everyone, and both security products scoped to its 30 active committers, at USD list:

Platform: 50 × $21 × 12 = $12,600/yr
Copilot Business: 50 × $19 × 12 = $11,400/yr plus metered usage beyond included credits
Code Security: 30 × $30 × 12 = $10,800/yr
Secret Protection: 30 × $19 × 12 = $6,840/yr

That's about $41,600 a year before compute and Copilot overage — and the $21 sticker everyone negotiated over is 30% of it. The budget conversation belongs on the whole stack.

How to pay less, legitimately

Four levers, in the order we'd pull them. Reconcile seats before renewal — the default posture rolls last year's user pool forward, and departed contractors bill like staff. Scope security by committer and repo rather than blanketing the estate; the per-committer model rewards precision. Buy Secret Protection first if budget forces a choice — leaked credentials are the cheaper product and the more common incident. And negotiate the renewal, not just the purchase: list prices carry a first-year qualifier, and annual commitments at enterprise scale routinely land below list.

Budgeting a move to GitHub Enterprise — or auditing what you're already paying for? Licence math is part of every GitHub Enterprise migration assessment we run, and we'll tell you which add-ons your estate actually needs. Book a discovery.