GitHub Enterprise pricing, five levers that move it.

GitHub Enterprise pricing looks like a flat per user rate, but the real spend sits in Advanced Security, Copilot, and the true up terms most buyers never negotiate.

How does GitHub Enterprise pricing actually work?

GitHub Enterprise prices per user per month on the published rate card, with Advanced Security and Copilot sold as separate add ons that scale on different metrics. The list rates sit on the GitHub pricing page, but enterprise terms are negotiated.

• Enterprise seats: per user per month on GitHub Enterprise, cloud or server, covering the core platform.
• Advanced Security: priced per active committer, a count that moves with delivery cycles.
• Copilot: per user tiers sold separately, with its own enterprise tier.
• Actions and storage: consumption charges that grow silently with CI activity.

The negotiation mistake is treating the seat rate as the deal. In our engagements the add ons carried 50 to 70 percent of total GitHub spend at enterprise scale.

Why does the Advanced Security committer count surprise buyers?

Advanced Security bills on unique active committers, and that population is always larger than the security team's estimate because it includes service accounts, contractors, and occasional committers. GitHub documents the metric in its Advanced Security documentation.

Where the count inflates

• Service accounts: automation identities that push commits count like humans unless excluded.
• Occasional committers: a single commit in the billing window adds a committer.
• Repository scope: enabling security features on all repositories pulls in every contributor.

How to control it

Scope Advanced Security to the repositories that need it, exclude automation identities, and measure the real committer count for ninety days before any quote is accepted. The measured number is routinely 20 to 30 percent below the assumed number.

Should you buy GitHub through the Microsoft relationship?

Routing GitHub through Microsoft contracting is worth evaluating at every renewal, because it opens enterprise agreement style discounting, co terming, and a second negotiation channel when the GitHub account team stalls. Microsoft has owned GitHub since 2018, and enterprise paper can reflect that.

The channel decision is leverage in itself. Pricing both paths and letting each side know the other is being priced moved quotes in most of our engagements.

What negotiation levers work on a GitHub Enterprise renewal?

Five levers move GitHub Enterprise pricing: measured usage cleanup, committer scoping, mixed license tiers, term length, and the Microsoft channel. They compound, and the sequence matters because the cleanup resets the baseline every other lever prices against.

1. Clean dormant seats and inactive committers, then size the renewal on the measured base.
2. Scope Advanced Security to the repositories that carry risk, not the whole estate.
3. Mix tiers where teams do not need enterprise features.
4. Trade term length only for written price protection on seats and add ons.
5. Price the Microsoft channel in parallel and make both sides aware.

Run the cleanup first. A discount negotiated on an inflated seat base is a discount on waste.

Where the common advice on GitHub Enterprise deals is wrong

The standard advice is to negotiate the seat price hard and accept the add ons at list because they are small line items. We disagree. In roughly 12 of the 15 plus GitHub estates Fredrik Filipsson benchmarked in 2024 to 2025, Advanced Security and Copilot together exceeded the core seat spend, and the committer metric grew faster than headcount. The buyer side move is to negotiate the add on metrics, committer scoping, true up treatment, and Copilot tier mix, before touching the seat rate. The seat price is the number GitHub expects you to fight about; the metrics are where the money moves.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

How to use these numbers

Treat the ranges as negotiation benchmarks, not promises. Your estate sets the baseline; the engagement file tells you what disciplined buyers achieved against the same vendor playbook.

GitHub expects the fight on the seat price. The money moves on the metrics.

What to do next

The moves below turn this analysis into a lower invoice at the next renewal.

A sequence you can run this quarter

1. Export seat and committer activity for the last ninety days and flag dormant identities.
2. Measure the true Advanced Security committer population with automation accounts excluded.
3. Map which teams need enterprise features and which can run lower tiers.
4. Price the renewal both standalone and through Microsoft contracting.
5. Negotiate true up treatment per the GitHub billing documentation before agreeing any rate.
6. Write seat and add on price protection into the order for the full term.

White Paper · DevTools

GitHub Enterprise Negotiation

Read it free.

Read the white paper

Frequently asked questions

How much does GitHub Enterprise cost?

GitHub Enterprise lists at a published per user per month rate, with Advanced Security and Copilot priced separately on their own metrics. At enterprise scale the add ons routinely carry half or more of the total spend, so the effective cost per developer is far above the seat rate.

Is GitHub Advanced Security priced per seat?

No. Advanced Security bills per unique active committer, a population that includes service accounts and occasional contributors unless scoped. Measured committer counts run 20 to 30 percent below assumed counts in our engagements once automation identities are excluded.

Can you buy GitHub Enterprise through Microsoft?

Yes. Microsoft owns GitHub and enterprise purchases can route through Microsoft contracting, which opens EA style discounting and co terming with the Microsoft agreement cycle. Pricing both channels in parallel is itself a negotiation lever.

What discount is realistic on GitHub Enterprise?

Effective improvements of 10 to 25 percent against first quote are achievable when usage cleanup, committer scoping, and channel competition run together. The discount follows the measured baseline, not the ask.

How do you reduce GitHub Copilot costs in an enterprise deal?

Tier mixing and activation data drive Copilot savings: license the enterprise tier only where its features are used and hold unused seats out of the renewal. Activation reports showing idle licenses are the strongest evidence in the conversation.

When should you start a GitHub Enterprise renewal?

Six to nine months before expiry, starting with the usage and committer measurement. The measurement window needs ninety days, and the channel comparison needs time to run as real competition rather than a closing week gesture.