GitHub Copilot Enterprise pricing: Business vs Enterprise per-seat framework.
Copilot Enterprise lists at $39 per user per month against Business at $19 and Pro at $10. For a 2,000-developer estate that is a $480,000 annual swing that only pays back if a measurable share of developers use the Enterprise-only features. This note sets the decision framework: which developers belong on which SKU, what Enterprise actually delivers, and how to model and negotiate the rollout.
There is no single right SKU. Copilot Business ($19) is the correct default for most developers; Copilot Enterprise ($39) earns its $240/user/year premium only in monorepo-heavy, onboarding-heavy or documentation-rich cohorts. The highest-value move is a mixed rollout — 500 Enterprise plus 1,500 Business cuts 38% off the all-Enterprise default for a 2,000-seat estate — and folding Copilot into the broader Microsoft EA negotiation rather than pricing it standalone.
01 Key findings
The Business-to-Enterprise gap is $240 per user per year. At 2,000 seats that is $480,000 annually ($936,000 all-Enterprise vs $456,000 all-Business) — a spend that must be justified by realised productivity, not provisioned by default.
Enterprise value is concentrated, not universal. Codebase indexing, PR summaries and Knowledge Bases pay back in large monorepos, polyglot estates and onboarding-heavy teams; in single-service teams that know their own code, realised value approaches zero.
A mixed SKU rollout is the cost-optimised default. 500 Enterprise + 1,500 Business delivers 38% saving; a 100-Enterprise pilot + 1,900 Business delivers 49% and 12 months of measured data before wider commitment.
Metered premium requests are the hidden line. Business includes 300 premium requests/user/month, Enterprise 1,000, both at $0.04 overage. A heavy AI-assisted developer can consume 2,000–5,000, adding $50–$150/month per seat.
Bundle beats standalone. Selling Copilot through the Microsoft EA rather than the GitHub team is worth 5–15 points; buyers who negotiate standalone consistently leave 8–14 points on the table.
02 Copilot SKUs & pricing
GitHub publishes four Copilot tiers. Three are enterprise-relevant; Pro is individual-only. The Enterprise-only features are organisation-wide codebase indexing, pull request summaries, and Knowledge Bases (repo-grounded answers).
| SKU | Price / user / month | Completion & chat | Org context | PR summaries | Custom models |
|---|---|---|---|---|---|
| Copilot Free | $0 | Limited (50 completions / 2,000 chats) | No | No | No |
| Copilot Pro | $10 | Unlimited | No | No | No |
| Copilot Business | $19 | Unlimited | No | No | No |
| Copilot Enterprise | $39 | Unlimited | Yes | Yes | Yes (Knowledge Bases) |
03 Business vs Enterprise scorecard
Relative strength across the dimensions that decide the SKU. Five dots = strongest; scoring reflects realised enterprise value, not raw feature count.
04 What Enterprise adds
- Unlimited code completion and Copilot Chat
- Organisation policy and licence management
- Half the cost of Enterprise per seat
- No organisation-wide codebase indexing
- No PR summaries or Knowledge Bases
- Lower premium-request allotment (300/month)
- Codebase indexing — citation-linked, repo-grounded answers
- Automatic PR descriptions & review summaries (saves 15–30 min/dev/week)
- Knowledge Bases ground chat in docs, runbooks and wikis
- Near-zero value in single-service, well-known codebases
- Knowledge Base value collapses without maintained docs
- Fine-tuning is a separate $80k–$250k services engagement, rarely used
Copilot Enterprise requires GitHub Enterprise Cloud, and its features only pay back where org context is used. Most enterprises overprovision Enterprise to the full developer population and pay the $240/seat/year premium for developers who never open codebase indexing, PR summaries or Knowledge Bases. Provision Enterprise to cohorts, not headcount — and measure feature usage before you renew.
05 Rollout cost model
Three scenarios for a 2,000-developer estate, priced at list with no volume discount. The mixed model delivers 38% saving over the all-Enterprise default; the pilot model delivers 49%.
| Scenario | Year 1 cost | Year 3 cost | Notes |
|---|---|---|---|
| All-Enterprise: 2,000 × $39 | $936,000 | $2,808,000 | Most common procurement default |
| All-Business: 2,000 × $19 | $456,000 | $1,368,000 | Most common cost-optimised baseline |
| Mixed: 500 Enterprise + 1,500 Business | $576,000 | $1,728,000 | Recommended default for most enterprises |
| Mixed + pilot: 100 Enterprise + 1,900 Business | $479,000 | $1,437,000 | Test Enterprise value before broad rollout |
Year 1 cost by scenario, relative to the all-Enterprise default:
Sourcegraph Cody Enterprise ($19–$59/user/month) wins on codebase-indexing precision in large monorepos and loses on IDE polish. Where the sole Enterprise justification is codebase indexing, a Sourcegraph plus Copilot Business stack often outperforms Copilot Enterprise alone at lower total cost.
06 Premium-request metering
GitHub introduced metered consumption in late 2024. Premium model requests (GPT-4 Turbo, Claude Sonnet 4, GPT-5) draw from a monthly allotment; the "premium request" abstraction obscures the underlying cost, because a single Claude Opus or GPT-5 query counts as multiple requests.
| SKU | Premium requests included | Overage rate |
|---|---|---|
| Copilot Business | 300 / user / month | $0.04 / request |
| Copilot Enterprise | 1,000 / user / month | $0.04 / request |
| Premium model multiplier | 1× to 50× depending on model | n/a |
A heavy AI-assisted developer can consume 2,000–5,000 premium requests per month, blowing through the Business allotment and adding $50–$150/month per seat. Control it three ways: restrict premium models and force the base-model default; negotiate a fixed organisation-level premium-request pool rather than per-user metering (requires a $1M-plus Copilot commit); and budget premium consumption as a separate line, not an afterthought.
07 Decision framework
Four considerations decide which developers belong on Enterprise. Weight them to each cohort before committing seats.
Codebase shape
Large monorepos and polyglot estates with shifting ownership realise high value from codebase indexing. Single-service teams that know their own code do not — keep them on Business.
Onboarding intensity
High developer turnover and frequent movement between unfamiliar code make org-grounded answers material. Stable, tenured teams see far less benefit.
Documentation maturity
Knowledge Bases only pay back where docs, runbooks and wikis are maintained. For "code is documentation" teams, Knowledge Base value is near zero.
Premium-model appetite
Cohorts that lean on premium models burn the metered allotment fast. Size the premium-request pool and access policy alongside the SKU decision, not after it.
08 Our recommendation
For the broad developer population — single-service teams, stable ownership, well-known codebases. Unlimited completion and chat at half the Enterprise cost. Cap premium-request overage with a base-model default.
For monorepo, polyglot and onboarding-heavy teams that use codebase indexing, PR summaries and Knowledge Bases daily — and only where the documentation to ground them is actually maintained. Provision by cohort, never by headcount.
Start 100 Enterprise + 1,900 Business (49% saving) and measure codebase-index queries, PR-summary acceptance and Knowledge Base use for 12 months before widening. Let usage data, not the procurement default, set the mix.
09 Negotiation levers
Copilot pricing is firmer than other GitHub products because Microsoft positions it as strategic. The realistic levers, strongest first:
| Lever | Mechanism | Typical value |
|---|---|---|
| Microsoft EA bundle | Copilot sold by the Microsoft account team, discounted against the broader EA relationship | 5–15 points |
| Three-year term | Multi-year commit with annual seat-count reset rights to preserve flexibility | 8–12 points |
| Premium-request pool | Shared org-level pool instead of per-user metering | 20–40% of overage risk |
| SKU-mix lock | Right to upgrade / downgrade seats between Business and Enterprise quarterly | Avoids fixed-mix trap |
| Co-term with VS Subscriptions | Align Copilot with Visual Studio Subscription estate | Cross-product discount |
Customers who negotiate Copilot standalone with the GitHub team consistently leave 8–14 points on the table versus folding it into the Microsoft EA.
Cut Copilot spend by 38%
Our AI procurement practice sizes the Business-versus-Enterprise mix, models premium-request exposure, and structures the Microsoft EA bundle.
The Licensing Edge
Weekly AI and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.