Microsoft GitHub Enterprise Licensing: What to Negotiate Before You Sign

GitHub Enterprise Cloud vs GitHub Enterprise Server: Pricing and Deployment Differences

Microsoft offers GitHub through two distinct deployment models, and understanding the pricing architecture of each is critical before negotiating your contract. This distinction often creates the first major negotiation opportunity—many organizations sign the wrong product type without realizing the cost implications.

GitHub Enterprise Cloud (GHEC)

GitHub Enterprise Cloud is GitHub's cloud-hosted SaaS offering, managed entirely by GitHub/Microsoft. It operates on a per-seat licensing model at $231 USD per user per year (list price as of March 2026), though volume discounts bring this closer to $180-200 per seat in real negotiations. This includes unlimited public and private repositories, advanced security features (when purchased separately), and GitHub Copilot integration.

GHEC is the default choice for most new customers because:

• No infrastructure overhead: GitHub manages all servers, patches, and uptime SLAs (99.9% uptime guarantee)
• Built-in compliance: FedRAMP Moderate, SOC 2 Type II, HIPAA, PCI DSS ready
• Instant scaling: Add or remove seats with no infrastructure provisioning
• Integrated Microsoft ecosystem: Native Microsoft Entra ID (Azure AD) integration, seamless with Microsoft 365 and Azure

GitHub Enterprise Server (GHES)

GitHub Enterprise Server is self-hosted software you deploy in your own data center or cloud infrastructure. Pricing is based on named user licenses, typically $3,975 USD per 20-user license block per year (list price), meaning a 100-user deployment costs $19,875 annually just for software—before counting infrastructure, backup, support, and operations staff.

GHES is chosen primarily for:

• Data sovereignty: Code stays entirely on your infrastructure, never transits to Microsoft datacenters
• Air-gapped deployments: No internet connectivity required for operation
• Custom integrations: Webhooks, API-level access, and full control over authentication
• Legacy compliance: Organizations with outdated regulatory frameworks requiring on-premises code storage

The Real Cost Comparison

A 500-user organization comparing Cloud vs Server sees dramatically different total cost of ownership:

This comparison reveals why GitHub Enterprise Cloud dominates new deals—the operational overhead of Server makes Cloud cost-effective for nearly all organizations under 2,000 users. The negotiation here isn't Cloud vs Server; it's whether Server is genuinely required. In 80% of cases where customers request Server, Cloud with enhanced security and compliance options is actually the better choice.

GitHub Teams vs GitHub Enterprise: The Feature and Cost Comparison

Before negotiating an Enterprise contract, you must first validate that Enterprise is actually what your organization needs. GitHub Teams and Enterprise target different operational scales, and moving to Enterprise without understanding the feature delta wastes budget.

GitHub Teams Pricing and Features

GitHub Teams is GitHub's mid-market offering at $44 USD per seat per year (list price). It includes:

• Unlimited public and private repositories
• Team management and access controls
• Branch protection rules
• Code owners and required reviews
• GitHub Pages hosting
• Basic CI/CD via GitHub Actions (2,000 minutes/month included)

For a 100-person development team where everyone commits code, GitHub Teams costs $4,400 annually. This is sufficient for most small-to-medium startups and isolated development teams within larger enterprises.

GitHub Enterprise Cloud: The Feature Expansion

GitHub Enterprise Cloud (GHEC) at $231/seat/year (5.2x the cost of Teams) adds:

• Organization-wide governance: Centralized policy enforcement, custom roles, and audit logging for compliance teams
• Enterprise account management: Multi-organization support, shared billing, and provisioning APIs
• Advanced security features: Secret scanning (native), dependency management, code scanning (requires GHAS add-on)
• IP allowlists: Restrict organization access to specific IP ranges
• Audit logs: 90-day retention with export capabilities for SOC 2 and HIPAA compliance
• Priority support: 15-minute response time for critical issues (vs. 24+ hours for Teams)
• GitHub Actions minutes: 50,000 minutes/month included (vs. 2,000 for Teams)

When to Choose Enterprise

Upgrade to Enterprise when:

• Compliance is required: You need audit logs, IP restrictions, and regulatory reporting (financial, healthcare, government)
• Multiple teams, one organization: You're consolidating 5+ separate GitHub accounts/organizations into one enterprise for unified billing and policy
• Your annual GitHub spend exceeds $50,000: Enterprise discounts make per-seat costs competitive with Teams at scale
• Security scanning is non-negotiable: Advanced Security (GHAS) is required and Enterprise licensing makes it cost-effective

Many organizations stay on Teams because their teams remain autonomous and compliance overhead is minimal. There's no shame in this—it's the right choice for 60% of development organizations.

GitHub Copilot Business vs GitHub Copilot Enterprise: $19 vs $39 Per User

GitHub Copilot, Microsoft's AI-powered code suggestion engine, is now the fastest-growing line item in GitHub contracts. As of March 2026, Copilot adoption is driving 30-40% of net new GitHub revenue. Understanding the licensing tiers is essential because overspending on Copilot seats while underspending on deployment is a common pattern.

GitHub Copilot Business: $19/user/month ($228/year)

Copilot Business is the baseline AI code suggestion product, available to any organization with GitHub Enterprise or GitHub Teams. It provides:

• Real-time AI code completion in VS Code, JetBrains IDEs, Visual Studio, and Neovim
• Multi-language support: Python, JavaScript, TypeScript, Go, Ruby, Java, C#, C++
• Prompt-to-code generation (write a comment, Copilot writes the function)
• Organization-level policy controls (disable for specific languages, require approval for suggestions)
• No code retention by GitHub (unlike free Copilot, which Microsoft uses for model improvement)
• Includes 120 code search queries per month
• Basic usage telemetry and seat management via API

GitHub Copilot Enterprise: $39/user/month ($468/year)

Copilot Enterprise is the premium tier, available only to GitHub Enterprise Cloud customers, with significant enhancements:

• Copilot Chat: Interactive multi-turn conversations about code (not just autocomplete)
• Repository context: Copilot learns your codebase's patterns, dependencies, and architecture to give smarter suggestions
• PR summaries: Auto-generate pull request descriptions and review comments
• Codebase search: 2,000 code search queries per month (vs. 120 for Business)
• Knowledge base integration: Copilot references your internal documentation, architecture decisions, and best practices
• Advanced security policy enforcement: Block suggestions containing patterns matching your secrets regex
• Custom models (coming Q2 2026): Fine-tune Copilot on your organization's code for better suggestions

Copilot Pricing Reality Check

For a 200-engineer organization where 80% of engineers use Copilot actively:

• Copilot Business tier: 160 users × $228 = $36,480/year
• Copilot Enterprise tier: 160 users × $468 = $74,880/year
• Difference: +$38,400/year (104% increase)

The ROI calculation depends entirely on productivity gains. GitHub's own studies show 35-45% faster code completion and 25-30% more code written in the first hour with Enterprise vs Business. For high-velocity teams doing repetitive scaffolding (data pipelines, CRUD APIs, test suites), Enterprise pays for itself. For teams doing novel algorithmic work, the gains are marginal.

Seat Counting Traps: How GitHub Counts Active Users vs Provisioned Seats

GitHub's seat licensing model is more nuanced than most enterprise software, and this nuance creates the single biggest negotiation trap. Understanding how GitHub measures "active" users is the foundation of renegotiating your contract downward.

The Two Seat-Counting Models

GitHub Enterprise Cloud uses "concurrent login" seat counting: if a user has logged in at any point during the calendar month, that user consumes one seat. It doesn't matter if they committed once or 1,000 times—one login = one seat for that month.

GitHub Enterprise Server uses "named user" seat counting: you assign seats to specific individuals at contract time, and they remain assigned until you manually remove them—even if they never log in.

This creates different negotiation opportunities for each:

GitHub Enterprise Cloud: The Active User Negotiation

Most organizations provision 20-30% more Cloud seats than they actually use because:

• Contractor onboarding: Contractors, interns, and temporary developers are provisioned month-to-month. If you have 50 contractors cycling through annually, some months you might have 60 provisioned; other months, 20.
• Cross-functional access: Product managers, designers, DevOps engineers, and security teams often have GitHub access but don't commit code regularly. They consume seats by accessing repositories or reading pull requests.
• Service accounts: CI/CD automation, Dependabot, security scanning bots, and monitoring tools all need GitHub users. Each consumes a seat.
• Organizational overhead: IT administrators, compliance auditors, and security engineers need org-level access.

The negotiation leverage: Audit your actual monthly active user data for the last 12 months. If your contract specifies 500 seats but your peak month averaged 380 active users and your average month was 320, you're paying for 180 unused seats (36% waste).

Bringing historical active user reports to Microsoft's sales team shifts the conversation from list price ($231/seat) to "what's a fair price for our actual consumption?" At this point, discounts jump from 15-20% to 30-40% off list.

GitHub Enterprise Server: The License Right-Sizing Trap

GHES licensing traps are different because named users are locked in at contract start. Common mistakes:

• Over-provisioning for growth: You contract for 300 named users because you're planning to hire 60 engineers next year. But you only hire 20, and you're stuck paying for 80 unused seats.
• Not removing departed employees: License seats don't automatically free up when someone leaves. IT must manually remove them, and many organizations don't. Over 3 years, 20-30% of named users are inactive.
• Not leveraging true-ups: GHES allows mid-year true-ups if you exceed your initial seat count. But this also means you can reduce your renewal count based on what you actually used.

The negotiation leverage for GHES: Analyze your GHES usage logs. Bring Microsoft evidence that fewer named users were actually active. For multi-year agreements, you can renegotiate the named user count at renewal based on average historical usage.

Advanced Security (GHAS): The Per-Committer Pricing Model and Overbuying Trap

GitHub Advanced Security (GHAS) is where most organizations massively overbuy. The pricing model creates a perfect storm of misunderstanding and overspend.

How GHAS Pricing Works

GHAS is not per-user; it's per active committer per month. An "active committer" is anyone who has committed code to a private repository in the last 30 days. Pricing is $45 USD per active committer per month ($540/year list price).

This means:

• Your 200-seat GitHub Enterprise Cloud has only 60 active committers (product, backend, infra teams). GHAS costs 60 × $540 = $32,400/year, not $200 × $540 = $108,000/year
• Contractors who commit for one sprint and then leave don't continue consuming GHAS licenses
• Non-technical team members (designers, PMs, ops) with GitHub access don't consume GHAS licenses
• Service accounts and bots that commit code DO consume GHAS licenses (a gotcha)

The Overbuying Pattern

Most organizations adopt GHAS using one of three models, all of which result in 25-40% overspend:

Model 1: "Just enable it for everyone" (Most common)

Enable GHAS on all private repositories. This results in paying for all engineers in your GitHub organization, including non-committers. Cost: 200 users × $540 = $108,000/year. Actual active committers: 60. True cost should be: $32,400/year. Overspend: $75,600 (233% waste).

Model 2: "License all development teams"

You license GHAS for anyone in the "engineering" organization group (product, backend, infra, QA teams). This includes SDETs, QA engineers, and automation specialists who don't commit frequently. Overspend: 20-35%.

Model 3: "Per-repository licensing"

Enable GHAS only on critical repositories (service repos, libraries, SDKs). This is correct but incomplete—you miss scanning your secondary systems and eventually end up with scattered GHAS coverage.

Right-Sizing GHAS at Contract Negotiation

During contract renewal or new purchase:

1. Pull 12 months of GitHub audit logs showing which users have committed to private repositories each month
2. Calculate your true active committer count (average across 12 months)
3. Add 20% buffer for contractor churn and summer interns
4. Present this to Microsoft as your licensing need

Example: You have a contract for 100 GHAS licenses at $540/committer. Your actual average active committers: 65 (12-month average). New deal: 78 licenses (65 × 1.2 buffer) at $45/committer × 12 months = $42,120/year vs. $54,000/year. Savings: $11,880 (22%).

GitHub Actions Minutes: Included vs Overage Pricing and Optimization

GitHub Actions is the CI/CD system built into GitHub. Most organizations don't realize they're overpaying for Actions minutes—either by provisioning excessive minutes or by not optimizing their workflows.

Included Actions Minutes by Plan

• GitHub Teams: 2,000 minutes per month included (then $0.008 per minute overage)
• GitHub Enterprise Cloud: 50,000 minutes per month included (then $0.008 per minute overage)
• GitHub Enterprise Server: 50,000 minutes per month included (no overage charges)

How to Estimate Your Needs

Minute consumption varies wildly by organization:

• Small startup (20 engineers, 1 service): 100-300 minutes/month. Team plan is sufficient.
• Mid-market (100 engineers, 5-10 services): 8,000-15,000 minutes/month. Enterprise Cloud included minutes cover 50% of needs.
• Large enterprise (500+ engineers, 50+ services): 50,000-200,000 minutes/month. Enterprise Cloud included minutes often insufficient.
• Data-heavy workloads (ML, analytics, data pipelines): 200,000-500,000 minutes/month. Massive overage costs.

Overage Cost Reality

A 200-engineer fintech company with 5 microservices and daily tests:

• Enterprise Cloud includes 50,000 minutes/month
• Actual consumption: 120,000 minutes/month
• Overage: 70,000 minutes × $0.008 = $560/month = $6,720/year
• This is completely hidden in most organizations and only discovered during cost analysis

Negotiation and Optimization Strategy

Step 1: Audit your actual consumption. GitHub provides minute usage in: Settings → Billing and Plans → Usage. Export 12 months of data.

Step 2: Identify optimization opportunities. Common wins:

• Self-hosted runners: For compute-intensive workflows, use self-hosted GitHub Actions runners (VMs you own). These consume zero GitHub-hosted minutes.
• Workflow optimization: Split parallel jobs, cache dependencies, and exit early. A 10-minute workflow running daily uses 300 minutes/month. Optimize to 5 minutes and save 150 minutes/month.
• Conditional execution: Don't run expensive workflows (integration tests, security scans) on every commit. Run full suite only on main branch.
• Matrix job reduction: Testing across 10 different Node versions multiplies minute consumption. Test against 3 versions instead.

Step 3: Negotiate with Microsoft. Present your 12-month consumption data. If you're consistently spending $500-1,000/month on overages, this is negotiation leverage. Microsoft can include additional minutes in your Enterprise Cloud contract at a lower rate than the per-minute overage price ($0.008/minute).

Real example: A customer with $8,000/year in Actions overages negotiated to have 100,000 additional minutes/month included in their Enterprise Cloud contract at a cost of $3,000/year—a 63% savings while actually increasing capacity.

GitHub Enterprise and Microsoft EA: Direct vs EA Licensing and Pricing Differences

This section addresses one of the most frequently bungled decisions: whether to buy GitHub directly from GitHub/Microsoft or through a Microsoft Enterprise Agreement (EA).

Direct GitHub Licensing

When you negotiate directly with GitHub sales, you receive a GitHub-specific contract with:

• Per-seat pricing for GitHub Enterprise Cloud ($180-220/seat after discount, vs $231 list)
• GHAS pricing ($35-40/committer/month after discount, vs $45 list)
• Copilot licensing ($15-18/user/month for Business, vs $19 list)
• 3-year multi-year discounts (additional 10-15% off)
• True-up terms allowing mid-contract growth
• Separate billing line items for each GitHub product

Microsoft Enterprise Agreement Licensing

If your organization has a Microsoft EA covering Windows, Office, Azure, Dynamics, or other Microsoft products, GitHub can be bundled into that agreement. This creates:

• Consolidated billing across all Microsoft products
• EA-level discounts that may be higher or lower than direct GitHub pricing depending on your EA size
• True-up rights tied to your EA true-up (typically once per year)
• Simplified contract administration (one EA vs multiple point contracts)

Direct vs EA: Which Is Cheaper?

This depends entirely on your EA profile:

EA Advantage scenarios (EA is cheaper):

• Your organization has a large EA (>$5M annual commit) with strong negotiated discounts
• You're already purchasing massive Azure or Microsoft 365 volume and have leverage
• You value consolidated billing and simplified contract administration

Direct Advantage scenarios (Direct is cheaper):

• Your EA is small (<$1M) and doesn't have special GitHub pricing
• Your EA discounts are modest and GitHub sales can beat them
• You want to negotiate GitHub separately without being constrained by EA terms

Real comparison: A 200-seat enterprise customer:

• Direct GitHub contract: 200 seats × $190/seat × 3 years = $114,000 (22% off list)
• Through small EA (list pricing): 200 seats × $231/seat × 3 years = $138,600 (no discount)
• Through large EA (30% EA discount): 200 seats × $231/seat × 0.7 × 3 years = $96,900

In this scenario: Direct saves $24,600 vs small EA. Large EA saves $17,100 vs direct.

The Right Approach

Before committing to EA licensing of GitHub:

1. Get a direct offer from GitHub sales with your actual seat count, products, and desired term
2. Get a quote from your Microsoft EA account manager with GitHub products included
3. Compare total cost of ownership including true-up terms and multi-year discounts
4. Consider admin overhead: EA licensing means GitHub sits in your EA, not standalone. This has overhead for billing and contract management.

GitHub vs Azure DevOps vs Jira: Using Competitive Tooling as Negotiation Leverage

Microsoft doesn't operate in a vacuum. GitHub competes with Azure DevOps (Microsoft's own on-premises alternative), Jira (Atlassian), Bitbucket, and GitLab. Savvy negotiations use this competitive landscape as leverage.

Azure DevOps (Microsoft's Own Alternative)

Azure DevOps is Microsoft's unified platform for Git repos, CI/CD pipelines, test management, and agile tracking. It's included free with Azure subscriptions (up to 6 users) and costs $7/month per additional user through Azure.

In negotiations, mentioning Azure DevOps is a credible threat because:

• It's a Microsoft product (so Microsoft owns the relationship either way)
• It's significantly cheaper ($7/user/month vs $231/user/year for GitHub Enterprise)
• It integrates natively with Azure, Microsoft Entra ID, and Microsoft tooling

The weakness: Azure DevOps is dated and has slower adoption of new features. Most engineers prefer GitHub's UX, security features, and open-source friendliness.

Negotiation angle: "We're evaluating Azure DevOps because of cost. What special pricing can GitHub offer to keep us on your platform?"

GitLab

GitLab is the closest GitHub competitor, offering similar features at similar or lower pricing. GitLab Premium is $228/year per user (nearly identical to GitHub Enterprise Cloud) but has been gaining market share, especially in organizations wanting self-hosted options.

Negotiation angle: "We're evaluating GitLab's self-hosted Premium plan. If GitHub can match their pricing, we'll stay." This is credible because GitLab is a genuine alternative.

Atlassian Jira + Bitbucket Stack

Some organizations use Atlassian's stack instead of GitHub:

• Bitbucket (Git hosting): $7-14/user/month depending on features
• Jira (issue tracking): $10-15/user/month
• Total: $17-29/user/month = $204-348/year, roughly GitHub's price

But Atlassian's stack is less integrated, and migration costs from GitHub are high. Use Jira comparison carefully—it's not as credible as GitLab because it's actually a different product category.

Smart Competitive Negotiation

When negotiating GitHub pricing, the most effective approach:

1. Identify your genuine alternatives: GitLab self-hosted, Azure DevOps, or current vendor inertia
2. Get competing quotes: A GitLab quote showing they're 30% cheaper is credible. A vague mention of "exploring alternatives" is not.
3. Lead with the business case: "We've evaluated 3 platforms. GitHub is our preference, but we need pricing within $X per seat to justify it to our CFO."
4. Let Microsoft respond: Don't threaten; let Microsoft sales team figure out your true reservation price

Proven Negotiation Tactics for GitHub Enterprise Contracts

Armed with the product and pricing knowledge above, here are the specific tactics that consistently deliver results in GitHub Enterprise negotiations:

Tactic 1: Anchor on Seat Count Reduction

The most reliable negotiation lever is seat count. If you can prove that your current contract includes 30% phantom seats, Microsoft has to address it.

The play:

1. Export your GitHub audit log showing monthly active users for 12 months
2. Calculate your average, peak, and minimum active user counts
3. Calculate the "waste" (provisioned seats - actual active users)
4. Present to Microsoft sales: "Our contract specifies 500 seats, but we've averaged 340 active users. We're paying for 160 phantom seats."
5. Propose: "We'll lock in a 3-year contract for 400 seats (340 average + 20% buffer) if you reduce the price to $180/seat."

This works because it moves the conversation from "what's the list price?" to "what's fair for your actual consumption?" and typically unlocks 25-35% discounts.

Tactic 2: Separate GHAS and Copilot Licensing

Many organizations bundle all GitHub products at one price, creating incentive misalignment. Instead:

The play:

1. Negotiate GitHub Enterprise Cloud seats separately (per user)
2. Negotiate GHAS separately (per active committer)
3. Negotiate Copilot separately (per user, with tiering for Business vs Enterprise)

This prevents you from overpaying for products you don't fully use. A customer doing this saved $34,000/year by correctly licensing GHAS to 45 active committers instead of 200 seats.

Tactic 3: Negotiate Multi-Year with Exit Flexibility

3-year agreements give Microsoft 10-15% additional discounts beyond year-1 pricing. But most organizations lock in without exit flexibility.

The play:

1. Negotiate a 3-year deal at $180/seat
2. Include a "true-up right": the ability to reduce seat count by up to 20% at each anniversary
3. This protects you if your company downsizes or consolidates teams

Microsoft typically accepts this because it's low-cost risk for them, but it protects you significantly.

Tactic 4: Push Migration Credits if Coming from Competitors

If you're migrating from Bitbucket, Azure DevOps, or GitLab, Microsoft offers migration services and sometimes credits to cover migration costs.

The play:

1. Document your migration effort: "Migrating 120 repositories, retraining 80 engineers, updating CI/CD pipelines"
2. Quantify the cost: "Internal estimate of $50,000-75,000 in engineering time"
3. Ask Microsoft: "What credits or discounts can you offer to offset the migration effort?"
4. Microsoft often provides 10-20% year-1 discount or free consulting to justify the switch

Tactic 5: Volume Discount Stacking

If you have a Microsoft EA, GitHub can be discounted both under EA terms AND under GitHub-specific volume discounts.

The play:

1. Get separate quotes from GitHub sales and your EA account team
2. Ask your EA account manager: "Can GitHub get an exception from standard EA pricing because we're committing to a large seat count?"
3. Ask GitHub sales: "If we bundle this into our EA, will you beat the EA pricing with a GitHub-specific volume discount?"
4. Play them against each other slightly—this often unlocks an extra 5-10% discount

Tactic 6: Time Your Negotiation to Renewal + Budget Cycle

The best time to negotiate GitHub pricing is:

• 60-90 days before contract renewal (Microsoft wants to renew before contract lapse)
• Q4 (Microsoft's fiscal year-end drives urgency)
• During your company's annual budget cycle (you can tie GitHub to your software budget negotiation)

Negotiating in Q1 with a renewal date 18 months away gives Microsoft no urgency. Negotiate in November with a December renewal and Microsoft feels the pressure.

Typical Savings and What to Target: 20-35% Off List

Based on NoSaveNoPay's negotiation data across 60+ GitHub Enterprise contracts, here are the realistic savings targets:

Year 1 Baseline: 20-25% Off List

For a new GitHub Enterprise Cloud contract with standard discounting:

• GitHub Enterprise Cloud: List $231/seat → Negotiated $174-185/seat (20-25% discount)
• GHAS: List $45/committer/month → Negotiated $32-36/committer/month (20-25% discount)
• Copilot Business: List $19/user/month → Negotiated $14-16/user/month (15-25% discount)

For a 500-seat organization with 100 active GHAS committers and 200 Copilot users:

• Enterprise Cloud: 500 × $179.50 = $89,750
• GHAS: 100 × $34/month × 12 = $40,800
• Copilot: 200 × $15/month × 12 = $36,000
• Total Year 1: $166,550
• List price would be: $219,300
• Savings: $52,750 (24%)

Enhanced Negotiation: 28-35% Off List

When you implement the tactics above (seat count reduction, multi-year, migration credits):

• GitHub Enterprise Cloud: $155-165/seat (28-33% off)
• GHAS: $28-31/committer/month (31-38% off)
• Copilot Business: $12-14/user/month (26-37% off)
• Copilot Enterprise: $32-35/user/month (15-20% off, less discounting available)

Same organization with enhanced negotiation:

• Reduced to actual 420 active users (from over-provisioned 500)
• Enterprise Cloud: 420 × $160 = $67,200
• GHAS: 100 × $30/month × 12 = $36,000
• Copilot: 200 × $13/month × 12 = $31,200
• Total Year 1: $134,400
• List price for actual consumption: $176,940
• Savings: $42,540 (24%)
• Savings vs. original 500-seat proposal: $99,100 (42%)

Multi-Year Impact

Most GitHub Enterprise contracts are 3 years. Here's the cumulative savings:

• Year 1 discount: 24% (as above)
• Year 2 discount: 22% (typically 2% less as Microsoft tightens terms)
• Year 3 discount: 20% (further tightening)
• Total 3-year savings: $114,500 (estimated)

For organizations spending >$150,000/year on GitHub, this is often the largest single IT vendor negotiation opportunity.

Key Takeaways

• GitHub Enterprise Cloud vs Server: Cloud is cheaper for 99% of organizations because Server's infrastructure overhead ($250K+/year) dwarfs the license savings.
• Enterprise vs Teams: Upgrade to Enterprise only if compliance is required or GHAS is essential. Most organizations overpay for unnecessary Enterprise features.
• Copilot tiers: Start with Copilot Business ($19/user) and upgrade only power users to Enterprise ($39/user). Hybrid approach saves 40-50% while capturing 80% of value.
• GHAS licensing: Calculate actual active committers, not all enterprise seats. Most organizations overbuy GHAS by 30-40%.
• Seat counting: Audit monthly active users for 12 months. Phantom seats (over-provisioning) are your biggest negotiation lever.
• Actions minutes: Optimize workflow efficiency and self-host runners for large jobs. Hidden overage costs often exceed $5K/year.
• Direct vs EA: Get competing quotes. EA licensing isn't always cheaper; GitHub direct negotiation often wins.
• Negotiation timing: Negotiate 60-90 days before renewal, ideally in Q4. This maximizes Microsoft's urgency.
• Realistic target: 20-25% first-year discount with good process. 28-35% with seat count reduction + multi-year + migration credits.