Research Note · GitHub · Licensing

GitHub Enterprise pricing 2026: Cloud, Server & add-ons.

GitHub Enterprise Cloud lists at $21 per user per month, but a fully loaded developer — base plus Advanced Security ($49) plus Copilot Enterprise ($39) — reaches $109 before discount. This note maps every 2026 line item, the SKU interactions buyers miss, the discount bands by contract value, and the Microsoft EA co-term lever that moves the bill the furthest.

By James Hill-WoodUpdated Sep 202511 min readDeveloper tooling cluster
Bottom line

The $21 base seat is the least of it. Advanced Security and Copilot add-ons, priced per active committer and per seat, are where GitHub bills balloon — and where negotiation and scoping recover the most. The single highest-discount move for Microsoft-heavy buyers is to co-term GitHub inside the Microsoft EA rather than negotiate it standalone.

01 Key findings

  1. A fully loaded developer lists at $109/month, not $21. Enterprise Cloud base ($21) plus Advanced Security ($49 per active committer) plus Copilot Enterprise ($39) is the real per-seat exposure. Negotiated cost typically lands at $65–$85 at $1M-plus annual contract value.

  2. The Advanced Security "active committer" metric is the top overrun. Enabling GHAS on 20 production repos in a 500-developer org often bills 350–420 committers, not the 80–100 who maintain them. Scoping repos or negotiating a flat commit is the fix.

  3. Copilot Enterprise rarely justifies double Copilot Business. Business delivers roughly 80% of the value at 49% of the price for single-repo teams; reserve the $39 Enterprise tier for the 20–30% who use codebase indexing and PR summaries.

  4. Consumption services hide six-figure leakage. Disabled Codespaces auto-suspend, GitHub-hosted runners for high-volume CI, and Packages egress at $0.50/GB each produce surprise bills that dwarf seat cost.

  5. Microsoft EA co-term is the highest-discount lever. GitHub is Microsoft-owned; folding it into the EA renewal adds 5–15 points of discount for buyers with material EA spend, versus a standalone GitHub negotiation.

02 GitHub 2026 list prices

GitHub publishes list prices openly and updates the page quarterly. The $21 base is straightforward; complexity comes from the add-ons and consumption-based services below.

SKUList priceMetric
Enterprise Cloud$21 per user / monthMonthly active user
Enterprise Server (self-hosted)$21 per user / monthProvisioned user
Team (mid-market)$4 per user / monthProvisioned user
Advanced Security add-on$49 per committer / monthUnique active committer
Copilot Business$19 per user / monthProvisioned user
Copilot Enterprise$39 per user / monthProvisioned user
Codespaces compute (4-core)$0.18 per hourCompute-hour
Actions Linux (standard)$0.008 per minuteMinute, after free tier
Actions Windows / macOS$0.016 / $0.08 per minuteMinute
Packages storage / transfer$0.25 per GB / $0.50 per GBStored GB / outbound GB

03 Cloud vs Server vs Data Residency

Enterprise comes in three deployment forms — Enterprise Cloud (multi-tenant SaaS on github.com), Enterprise Server (self-hosted VM), and Enterprise Cloud with Data Residency (single-tenant, EU region). All three carry the same $21 list. The differences are operational and contractual.

CapabilityEnterprise CloudEnterprise ServerEC + Data Residency
Hostinggithub.com multi-tenantCustomer VM on-prem/cloudSingle-tenant EU region
Data residencyUS only (standard tier)Customer-controlledEU (Germany)
CodespacesNativeSelf-hosted runners onlyNative
Operational burdenLow (GitHub manages)High (customer manages infra)Low
EU AI Act fitLimited (US residency)Full controlBuilt for EU compliance

Enterprise Server is now niche — concentrated in defence, sovereignty-bound financial services, and legacy private-cloud mandates. For new buyers, Enterprise Cloud is the default; Data Residency answers EU sovereignty without the operational burden.

04 Advanced Security & Copilot add-ons

The add-ons are where per-seat cost triples. Advanced Security (GHAS) closes the gap to dedicated AppSec vendors; Copilot is the most aggressively priced upsell GitHub has launched. The per-developer stack, list, at full loading:

Base seat
$21
+ Copilot Business
$40
+ Copilot Ent
$60
Fully loaded
$109
Negotiated
~$75
Add-on SKUPriceWhat you get / who it fits
Advanced Security (GHAS)$49 per committer / moSecret & code scanning (CodeQL), dependency review, security overview
Code Security (tier)$30 per committer / moCode + secret scanning only; 39% cheaper for pre-production protection
Copilot Business$19 per user / moCompletion, chat, CLI — 80% of the value for single-repo teams
Copilot Enterprise$39 per user / moAdds org context, PR summaries, custom models, Knowledge Bases
Copilot premium requests$0.04 each above 300/moHeavy users add $40–$120/mo per seat in metered usage
The active-committer trap

An active committer is any user who pushed to a GHAS-enabled repo in the past 90 days, counted per organisation. Enabling GHAS on one critical repo can bill every developer who touched it that quarter. For high-contractor-churn orgs, cost runs 30–60% above steady-state headcount. Scope GHAS to a smaller repo set or negotiate a flat-rate commit instead of the floating committer model.

05 Consumption costs: Codespaces, Actions, Packages

Metered services are the second source of overrun. They start inside generous free tiers, then scale linearly with usage that engineering — not procurement — controls.

ServiceIncluded on EnterpriseOverage rateHidden cost
CodespacesPay-as-you-go$0.18/hr (4-core), $0.07/GB storageDisabled auto-suspend → idle compute bills
Actions minutes50,000 minutes / moLinux $0.008, Windows $0.016, macOS $0.08GPU larger runners $0.16/min misconfig
Packages50 GB storage$0.25/GB storage, $0.50/GB egressImage pulls: 200 GB/day = $3,000/mo egress
Architectural fixes

Default Codespaces auto-suspend at 30 min idle. For CI above 500K monthly minutes, self-hosted runners on AWS/Azure Spot cut Actions compute 60–80%. Mirror frequently-pulled images to a cloud-native registry (ECR, ACR, Artifact Registry) and keep GitHub Packages as source of truth to eliminate ~90% of egress.

06 Discount bands and the EA lever

GitHub sales discounts are tiered by annual contract value. Realistic bands observed in advisor-led negotiations, 2024–2026:

Annual contract valueBase seatCopilotAdvanced Security
$50K – $250K0–5%0–5%0–5%
$250K – $1M5–15%5–10%5–10%
$1M – $3M15–25%10–18%10–20%
$3M – $10M25–35%18–28%20–30%
$10M+35–45%28–40%30–40%
Highest-value tactic

The Microsoft EA co-term lever: GitHub is fully owned by Microsoft and routinely co-sells with the Microsoft account team. Folding GitHub Enterprise into the Microsoft EA renewal — rather than negotiating it standalone — adds 5–15 percentage points of discount and is the single highest-discount 2026 move for customers with $5M-plus EA spend. Force one joint commercial conversation, not the two separate negotiations Microsoft prefers.

07 Seat-counting and audit traps

Enterprise Cloud bills on monthly active users — anyone who logged in or performed any action, including read-only browsing. Two traps inflate the count:

Service accounts & bots

CI service accounts, deploy bots and automation users are billable as active users. A pipeline with 12 service-account commits per day consumes 12 active-user slots. Consolidate automation into a small set of dedicated service accounts — typical finding is 8–15% of paid seats are automation or dormant.

Cross-organisation membership & the 90-day window

A user in two enterprise organisations is billed once by each — consolidate multi-BU estates into a single account with internal repos per BU. Separately, the GHAS 90-day committer window keeps billing a one-time contributor for a full quarter; a flat-rate GHAS commit eliminates this leakage.

08 Buy framework

Four considerations should shape the GitHub commitment before signing. Weight them to your estate.

Factor 01

Microsoft EA position

Material EA spend creates a structural co-term advantage. Time the GitHub renewal to the EA and negotiate them jointly — worth 5–15 discount points.

Factor 02

Add-on scope

Model GHAS active committers and Copilot Enterprise adoption before committing. Scope GHAS to critical repos and split Copilot tiers by actual usage.

Factor 03

Consumption profile

High-volume CI, heavy Codespaces or large Packages egress change the maths. Right-size runners and auto-suspend before locking a commit.

Factor 04

Commit structure

Prefer flat-rate GHAS commits over the floating committer model, and avoid over-committing metered spend that engineering can optimise away.

09 Recommendations

Co-term the EA
When Microsoft-heavy

Do this when you carry $5M-plus Microsoft EA spend. Align the GitHub renewal to the EA and force one joint negotiation for 5–15 extra discount points.

Right-size add-ons
When GHAS/Copilot dominate

Do this when add-ons exceed base seat cost. Scope GHAS to critical repos on a flat commit, and reserve Copilot Enterprise for the 20–30% who use org context.

Audit consumption
When CI/Packages are heavy

Do this when metered spend is unexplained. Self-host high-volume runners, enforce Codespaces auto-suspend, and mirror Packages to a cloud-native registry.

Run a benchmarked GitHub negotiation

We coordinate GitHub timing, add-on scoping and the Microsoft EA co-term to land 2026 terms you can defend.

Request vendor negotiation →

The Licensing Edge

Weekly vendor and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.