A working framework for CIOs, engineering leaders, and procurement teams negotiating the 2026 GitHub Enterprise renewal. Recover eighteen to thirty two percent against the opening proposal.
A working framework for CIOs, engineering leaders, platform engineering directors, and procurement teams negotiating the 2026 GitHub Enterprise renewal. Recover eighteen to thirty two percent against the opening proposal through user reconciliation, Advanced Security right sizing, Copilot adoption tracking, and a documented GitLab Ultimate exit path.
GitHub Enterprise sits inside the critical path of most modern software delivery operations. The platform hosts source code, automates CI and CD, scans secrets and code, and now ships the Copilot generative coding assistant.
The 2026 commercial discussion sits at a difficult fork. GitHub pushes customers from Enterprise standalone toward bundled Advanced Security and Copilot consumption. Microsoft owns GitHub and routes selective GitHub commerce through the Azure Consumption Commitment vehicle.
The 2026 GitHub Enterprise renewal cycle uses six commercial vectors against the buyer.
This paper sets out the Redress Compliance 2026 GitHub Enterprise renewal negotiation framework. Refined across more than five hundred enterprise software engagements at Industry recognized scale, with over two billion dollars under advisory.
The framework stages the renewal response across user pool reconciliation, Advanced Security right sizing, Copilot adoption tracking, Actions and Codespaces consumption right sizing, MACC drawdown evaluation, Cloud versus Server deployment review, and a documented exit path.
The exit path covers GitLab Ultimate, Atlassian Bitbucket Premium and Data Center, Microsoft Azure DevOps Services, JetBrains Space, and self hosted alternatives like Gitea Enterprise and SourceHut.
The single most valuable 2026 move is documenting the active developer baseline, the Copilot adoption telemetry, and the Advanced Security coverage profile inside the procurement file.
Default 2026 GitHub posture inflates the contracted commitment across every metric. The Microsoft ownership creates additional levers through MACC drawdown that customers without buyer side advisory rarely capture.
Read the related GitHub Enterprise Copilot Negotiation, the GitHub Copilot Business Negotiation, the GitLab Ultimate Negotiation, the Microsoft Services, and the Microsoft Knowledge Hub.
GitHub launched in 2008 as a public Git repository hosting service. Microsoft acquired GitHub in 2018 for USD 7.5 billion. The 2018 to 2026 cycle expanded GitHub from public repository hosting into the full developer platform across source code, CI, CD, security, and now AI assisted coding.
The 2020 to 2022 cycle introduced GitHub Actions for CI and CD, GitHub Codespaces for cloud development environments, GitHub Packages for artifact management, and the first generation Advanced Security bundle covering code scanning, secret scanning, and dependency review.
The 2022 to 2024 cycle introduced GitHub Copilot as the generative coding assistant. Copilot launched in business preview in 2021, in general availability for individuals in 2022, and in business and enterprise tiers in 2023 and 2024.
The 2024 to 2026 portfolio compression unified GitHub Enterprise around the four primary lines. The Enterprise platform itself. Advanced Security with the April 2025 unbundling into Code Security and Secret Protection. Copilot Business and Enterprise. Consumption based Actions, Codespaces, and Packages.
The 2026 commercial discussion folds three structural pressures. List price increases run roughly five to ten percent annually across the GitHub catalog. Advanced Security unbundling pressure compounds at customers consolidating onto GitHub. Copilot upsell pressure runs broadly across the developer pool.
The 2024 to 2026 alternative developer platform vendor adoption rate has steadied. GitLab Ultimate retained measurable enterprise traction at customers seeking documented agent independence from Microsoft. Atlassian Bitbucket Premium maintained share at customers consolidating with Jira and Confluence. Azure DevOps Services retained share at Microsoft installed customers.
The 2026 renewal wave hits the consolidated GitHub Enterprise installed base. Documented commercial uplift compounds across list price increases, Advanced Security unbundling, Copilot upsell, Actions and Codespaces consumption growth, and the multi year commitment.
| Customer profile | Typical 2026 GitHub scope | Annual 2026 commitment |
|---|---|---|
| Mid market | 500 to 2,500 developers on Enterprise, selective Copilot, GHAS on critical repos | USD 0.15m to 0.75m |
| Large enterprise | 4,000 to 12,000 developers on Enterprise, broad Copilot, GHAS portfolio wide | USD 1.1m to 4.2m |
| Upper enterprise | 18,000 plus developers on Enterprise, Copilot Enterprise, full GHAS, Actions, Codespaces | USD 5m to 18m |
| Three year commitment value band | Aggregate term value at upper enterprise scale | USD 15m to 54m |
| SKU or consumption unit | List rate | Negotiated band at upper enterprise scale |
|---|---|---|
| GitHub Enterprise (per user per month) | USD 21 | USD 14 to USD 18 |
| GHAS Code Security (per active committer per month) | USD 30 | USD 19 to USD 25 |
| GHAS Secret Protection (per active committer per month) | USD 19 | USD 12 to USD 16 |
| GHAS full bundle (per active committer per month) | USD 49 | USD 30 to USD 40 |
| Copilot Business (per user per month) | USD 19 | USD 13 to USD 16 |
| Copilot Enterprise (per user per month) | USD 39 | USD 25 to USD 32 |
| Actions minutes overage (Linux 2 vCPU, per minute) | USD 0.008 | USD 0.005 to USD 0.007 |
| Actions larger runners (per minute, varies) | USD 0.016 to USD 0.064 | 20 to 35 percent discount on commit |
| Codespaces compute (per core hour, varies) | USD 0.18 to USD 1.20 | 15 to 30 percent discount on commit |
| Packages storage (per gigabyte month) | USD 0.25 | Bundled at upper enterprise scale |
| Multi year commitment discount | 5 to 12 percent (3 year) | Negotiated separately |
Each industry vertical carries a documented 2026 GitHub Enterprise renewal pattern. Read the GitHub Enterprise Copilot Negotiation, the GitLab Ultimate Negotiation, and the Microsoft Azure ELA Negotiation.
The single largest commercial recovery vector on a 2026 GitHub Enterprise renewal sits inside the user inventory. Every developer account produces documented commit, pull request, and authentication telemetry inside the GitHub Enterprise audit log.
Default 2026 GitHub posture rolls the prior user pool forward without reconciliation against current developer headcount. The pool includes leavers, dormant accounts, bot accounts, service accounts, and contractor accounts past contract end.
The reconciliation lives across the GitHub Enterprise admin console user list, the SCIM provisioning source (Entra ID, Okta, or similar), the Workday or HR source of truth, and the GitHub audit log activity export.
Pull the GitHub Enterprise user list filtered to documented active sign in within ninety days. Compare against the Entra ID or Okta SCIM provisioning source. Reconcile against the Workday or HR active employment status.
That count is the active developer baseline. Compare the active developer baseline against the contracted user pool.
GitHub Enterprise charges per user across all account types. Bot accounts for CI integrations, service accounts for automation, and outside collaborator accounts each count against the contracted pool.
Default 2026 posture leaves bot and service accounts on the per user paid tier. The procurement file should consolidate bot and service accounts onto GitHub Apps with installation level authentication that does not consume user seats.
Outside collaborator accounts cover contractors, partners, and external reviewers. The procurement file should rotate outside collaborators off the contract at engagement end and reuse documented collaborator slots across rotating engagements.
Every 2026 GitHub Enterprise renewal should land at the vendor with this evidence pack already filed inside the procurement record.
GitHub Advanced Security unbundled in April 2025 into two separate SKUs. Code Security covers code scanning, CodeQL, and the broader static analysis surface. Secret Protection covers secret scanning across repositories and push protection.
The 2026 list runs USD 30 per active committer per month on Code Security and USD 19 per active committer per month on Secret Protection. The full bundle runs USD 49 per active committer per month.
The unbundling created documented commercial leverage. Customers can scope Code Security and Secret Protection independently rather than carrying the bundled attach forward.
The Code Security scope test asks three questions per repository. Does the repository contain code shipped to production or to customers? Does the repository sit on the critical security boundary for regulated workloads? Does the repository have documented coverage requirements from internal application security or compliance?
Positive answers across all three justify Code Security attach. The procurement file scopes Code Security to repositories meeting the test. Lower risk repositories run without paid Code Security and rely on the free CodeQL community pack and open source scanners.
Most enterprise environments find Code Security justifies attach on twenty to forty percent of repositories. The broad attach approach across the full repository inventory overspends Code Security by sixty to seventy five percent.
Secret Protection differs from Code Security in scope. The service covers all repositories at the organization level rather than per repository. Push protection blocks commits containing detected secrets before they hit the remote.
Most enterprise environments justify Secret Protection across the full organization regardless of repository risk. The cost of a leaked secret in a low risk repository remains material. Secret Protection therefore carries a different scope discipline than Code Security.
The procurement file should evaluate Secret Protection as an organization wide attach with the active committer counter providing the cost variable. Right sizing then focuses on active committer compression rather than repository scope.
GitHub Copilot has become a strategic line item inside the 2026 GitHub Enterprise renewal. Copilot Business at USD 19 per user per month and Copilot Enterprise at USD 39 per user per month each cover documented developer assistance workflows.
Default 2026 posture pulls Copilot seats broadly across the developer pool. Most customers assign Copilot to every developer without measuring adoption. The contracted seat pool sits at one hundred percent of the developer headcount.
The Copilot adoption telemetry tells a different story. Documented average active usage rates across upper enterprise deployments sit at thirty to fifty percent of assigned seats. Most assigned developers either rarely use Copilot or abandon it after initial exposure.
The GitHub Copilot admin console exposes per user adoption telemetry. Active suggestions, accepted suggestions, daily active users, and weekly active users each produce documented metrics.
The procurement file should pull ninety days of Copilot adoption telemetry per assigned seat. Active users with documented accepted suggestion counts above the active baseline justify continued seat assignment. Inactive or low activity users should rotate off the contracted pool.
The seat compression typically cuts the Copilot line by thirty to fifty percent against the default broad assignment. The compression compounds with the user pool reconciliation across the Enterprise tier.
Copilot Business covers the standard developer assistant. Copilot Enterprise adds knowledge base integration, custom models trained on the customer codebase, and pull request summaries.
The Enterprise tier pays back at upper enterprise scale with documented knowledge base content and active custom model usage. Customers without those workloads find the Business tier matches the developer assistance value at half the cost.
The procurement file should evaluate Enterprise tier adoption against documented knowledge base content, custom model training data, and active developer query patterns. Read the GitHub Copilot Business Negotiation and the GitHub Enterprise Copilot Negotiation.
GitHub Actions provides CI and CD automation with per minute pricing on hosted runners. GitHub Codespaces provides cloud development environments with per core hour pricing on managed compute.
Both services consume against the contracted budget on an overage basis. The 2026 list ships Linux 2 vCPU runner minutes at USD 0.008 per minute with larger runner tiers at USD 0.016 to USD 0.064. Codespaces compute ranges from USD 0.18 to USD 1.20 per core hour depending on the configuration.
The contracted Actions and Codespaces commit grows materially at upper enterprise scale. Documented run rate inflation runs forty to eighty percent annually at customers without consumption discipline.
The Actions optimization framework folds four primary moves. Self hosted runner adoption for high volume pipelines removes the per minute charge entirely. Caching discipline through actions/cache reduces redundant work across pipeline runs. Concurrency control prevents redundant pipeline runs on the same commit. Workflow consolidation merges redundant pipelines.
The procurement file documents the Actions consumption profile across the trailing ninety days. The top ten pipelines by minute consumption typically account for sixty to eighty percent of the total. Optimization focused on those pipelines captures most of the savings.
Self hosted runners on customer infrastructure cap the per minute consumption at the underlying compute cost. The break even runs roughly five hundred thousand minutes per month at upper enterprise scale, after which self hosted runners win cleanly on cost.
Codespaces consumption follows a different pattern. Active developer adoption tends to drive consumption growth. Inactive Codespaces continue to consume storage even without compute usage.
The procurement file documents Codespaces consumption per active developer. The default 2026 posture funds growth without retention discipline. The buyer side counter implements automatic Codespaces hibernation after documented idle thresholds and deletion after documented retention thresholds.
The retention discipline typically cuts Codespaces consumption by twenty five to forty percent against the default funded growth.
Microsoft owns GitHub. The 2026 commercial framework allows documented GitHub Enterprise consumption to draw down the Azure Microsoft Azure Consumption Commitment (MACC).
The MACC drawdown applies to GitHub Enterprise, Advanced Security, Copilot Business and Enterprise, and selective Actions consumption. The drawdown rate matches the MACC drawdown rate for first party Azure services.
The default 2026 posture leaves GitHub Enterprise outside the MACC drawdown vehicle. Customers with multi year MACC commitments should evaluate routing GitHub through the MACC.
The MACC drawdown break even test asks three questions. Does the customer have an active multi year MACC commitment? Does the customer face MACC drawdown shortfall risk in the current term? Does the MACC discount profile beat the standalone GitHub discount profile?
Positive answers across all three justify MACC drawdown evaluation. The procurement file models the MACC drawdown scenario against the standalone GitHub commercial scenario.
The MACC drawdown often beats the standalone GitHub commercial framework at upper enterprise scale. The drawdown provides additional flexibility on commitment timing and the MACC discount tier compresses the per user rate. Read the Microsoft Azure ELA Negotiation.
The MACC sits inside the broader Microsoft Enterprise Agreement framework. The MACC drawdown decision should coordinate with the broader Microsoft EA renewal cycle.
Customers with simultaneous Microsoft EA and GitHub Enterprise renewals should structure both inside a single coordinated commercial discussion. The combined leverage typically compresses both lines by additional five to ten percent beyond the standalone optimization.
The procurement file should align GitHub Enterprise term dates with the Microsoft EA term dates. The aligned dates simplify MACC drawdown management and unlock the combined commercial discussion.
GitHub Enterprise ships in two deployment models. GitHub Enterprise Cloud is the multi tenant SaaS service hosted on GitHub infrastructure. GitHub Enterprise Server is the self hosted appliance running on customer infrastructure.
The 2026 list price runs the same USD 21 per user per month across both models. The deployment selection drives operational and compliance considerations rather than direct pricing impact.
Most enterprise customers run Cloud as the primary deployment with selective Server installations for regulated or air gapped workloads. The Cloud platform receives faster feature delivery and removes the operational burden of appliance management.
Server retains the edge in three documented scenarios. Air gapped environments without internet connectivity require Server. Regulated environments with data residency requirements that GitHub Cloud regions cannot satisfy require Server. Specific compliance requirements around data sovereignty may favor Server.
The 2026 GitHub Cloud regional footprint covers the United States, the European Union (Frankfurt and Amsterdam), and selected APAC regions. The expanded regional footprint reduces the data residency scenarios that previously required Server.
The procurement file should document the specific compliance and operational requirements driving Server selection. Default Server selection without documented requirements adds operational overhead without value.
The 2026 GitHub Enterprise contract supports Cloud and Server in the same agreement. Customers can deploy Cloud for the majority of the developer pool and Server for regulated workloads.
The hybrid deployment requires documented user management discipline. Users should not duplicate across Cloud and Server. The procurement file should map each user to a single deployment model.
The hybrid Enterprise Bridge feature allows selective sharing of resources across Cloud and Server. The bridge simplifies hybrid management but adds documented configuration overhead.
The 2026 GitHub Enterprise commercial discussion carries a documented exit path against the alternative developer platforms. GitLab Ultimate, Atlassian Bitbucket Premium and Data Center, Microsoft Azure DevOps Services, and JetBrains Space each cover documented commercial pressure on the GitHub installed base.
The exit path does not require complete migration. The procurement file files the documented capability to migrate selective workloads against the GitHub commercial position.
GitLab Ultimate provides an integrated DevSecOps platform with source code, CI and CD, security scanning, and the GitLab Duo AI assistant in a single subscription. The platform carries documented agent independence from Microsoft and the GitHub ownership.
The 2026 GitLab Ultimate commercial framework prices the platform at USD 99 per user per month at list with documented enterprise band compression to USD 50 to USD 75. The all in pricing includes the equivalent of GitHub Enterprise plus Advanced Security plus selective Copilot in a single line item.
Customers consolidating their full DevSecOps stack often find GitLab Ultimate compresses the aggregate spend versus the GitHub Enterprise plus GHAS plus Copilot bundle. Read the GitLab Ultimate Negotiation.
Atlassian Bitbucket Premium covers source code hosting integrated with Jira and Confluence. Bitbucket Data Center provides the self hosted equivalent for regulated workloads.
The 2026 Bitbucket commercial framework prices the platform at lower per user rates than GitHub Enterprise. Customers with established Atlassian footprints often find consolidation onto Bitbucket reduces aggregate developer tools spend.
Bitbucket lacks the breadth of the GitHub Marketplace and the depth of GitHub Actions and Copilot. The platform fits customers prioritizing Atlassian consolidation over breadth of integrations.
Microsoft Azure DevOps Services provides the Azure first developer platform. The 2026 framework covers Azure Repos, Azure Pipelines, Azure Boards, Azure Test Plans, and Azure Artifacts.
Microsoft maintains the platform as the alternative to GitHub inside the Microsoft developer tools portfolio. Customers seeking the Microsoft developer platform without the GitHub Enterprise scope find Azure DevOps fits the use case.
Self hosted alternatives include Gitea Enterprise, SourceHut, and the open source GitLab Community Edition. These options cap the per user license cost at infrastructure and operations only but require documented operational capacity.
Across more than five hundred enterprise software engagements, six traps recur in 2026 GitHub Enterprise renewals. Each carries a documented commercial cost. Each has a known corrective move inside the procurement file.
Pull the user list filtered to active sign in within ninety days. Compare against the Entra ID or Okta SCIM source. Reconcile against the Workday active employment status. Convert bot and service accounts to GitHub Apps. Rotate outside collaborators off the contract at engagement end.
The team that walks into the commercial discussion with reconciliation filed walks out with eighteen to thirty two percent recovery. The team that walks in without reconciliation walks out with ten to twenty two percent uplift. The single biggest discriminator across five hundred engagements is whether the active developer baseline existed before the meeting started.
Pull Copilot admin console telemetry per assigned seat. Active suggestions, accepted suggestions, daily active users, and weekly active users feed the adoption metric. Active users with documented accepted suggestion counts above the baseline justify seat retention. Inactive or low activity users rotate off the contracted pool.
The seat compression typically cuts the Copilot line by thirty to fifty percent against the default broad assignment. Evaluate Copilot Business versus Copilot Enterprise against documented knowledge base content and custom model adoption. Most environments fit the Business tier at half the cost of Enterprise.
Run the Code Security scope test per repository against production deployment, regulated workload status, and documented application security coverage requirements. Scope Code Security to repositories with positive answers across all three. Lower risk repositories run without paid Code Security and rely on the free CodeQL community pack.
Keep Secret Protection at organization scope with active committer compression as the lever. The unbundling in April 2025 enables this scoping discipline. Most environments find Code Security attach justifies twenty to forty percent of repositories while Secret Protection covers the full organization.
Run the MACC drawdown break even test. Customers with active multi year MACC commitments, MACC drawdown shortfall risk, and MACC discount profiles beating standalone GitHub should route consumption through the MACC vehicle. Align GitHub Enterprise term dates with the Microsoft EA term dates.
The MACC drawdown often beats the standalone GitHub commercial framework at upper enterprise scale. The drawdown provides additional flexibility on commitment timing and the MACC discount tier compresses the per user rate. The combined leverage on simultaneous EA and GitHub renewals typically compresses both lines by additional five to ten percent.
Map every contracted GitHub workload against the documented competitive equivalent. The strategic DevSecOps consolidation play maps to GitLab Ultimate. The Atlassian consolidation play maps to Bitbucket Premium and Data Center. The Microsoft native alternative maps to Azure DevOps Services. The cost optimization play maps to Gitea Enterprise or self hosted GitLab Community Edition.
The documented exit path is a meaningful commercial leverage vector inside the 2026 GitHub commercial discussion alongside the MACC drawdown evaluation. File the exit path in the first commercial meeting. Reference it at every escalation point through the negotiation cycle. Cap annual uplift at three to four percent with downgrade rights.
GitHub Enterprise is the enterprise developer platform from Microsoft, sold in two deployment models. GitHub Enterprise Cloud is the multi tenant SaaS service hosted on GitHub infrastructure. GitHub Enterprise Server is the self hosted appliance for customers requiring on premises or VPC deployment.
The 2026 list price runs USD 21 per user per month on Enterprise across both models, with separate add ons for Advanced Security, Copilot, Actions consumption, Codespaces, and Packages.
The 2026 list price runs USD 21 per user per month on GitHub Enterprise across Cloud and Server. Negotiated bands at upper enterprise scale compress to USD 14 to USD 18 per user per month at multi year commitment scale.
The Team tier sits at USD 4 per user per month on GitHub.com Team for smaller deployments. The Free tier covers public repositories and basic functionality on GitHub.com.
GitHub Advanced Security (GHAS) unbundled in April 2025 into two separate SKUs. Code Security covers code scanning and CodeQL at USD 30 per active committer per month. Secret Protection covers secret scanning at USD 19 per active committer per month. The full GHAS bundle runs USD 49 per active committer per month at list.
Negotiated bands compress these by twenty to thirty five percent at upper enterprise scale. The unbundling created documented commercial leverage. Customers can scope Code Security and Secret Protection independently rather than carrying the bundled attach forward.
GitHub Copilot Business lists at USD 19 per user per month for the standard developer assistant. Copilot Enterprise lists at USD 39 per user per month with knowledge base integration, custom models, and the broader Enterprise features.
The 2026 negotiated bands compress to USD 13 to USD 16 on Business and USD 25 to USD 32 on Enterprise at upper enterprise scale with documented Copilot adoption. Most environments find Business fits the developer assistance value at half the cost of Enterprise.
Documented opening commercial uplift bands of ten to twenty two percent against the prior contracted GitHub run rate at upper enterprise scale. The 2026 framework folds list price increases, Advanced Security unbundling pressure, Copilot Business or Enterprise upsell, Actions and Codespaces consumption growth, and the multi year commitment uplift.
The uplift hits hardest at customers without documented user pool reconciliation, Copilot adoption tracking, and Advanced Security scope discipline.
Eighteen to thirty two percent against the GitHub Enterprise opening proposal across the contracted user pool.
Recovery requires documented user pool reconciliation, Advanced Security active committer right sizing, Copilot adoption tracking against assigned seats, Actions and Codespaces consumption right sizing, MACC drawdown evaluation, and a documented GitLab Ultimate, Bitbucket Premium, and Azure DevOps exit path.
Microsoft owns GitHub. Enterprise customers with an Azure Microsoft Azure Consumption Commitment (MACC) can apply documented GitHub Enterprise consumption against the MACC drawdown. The 2026 framework allows GitHub Enterprise, Advanced Security, Copilot, and selective Actions consumption to draw down MACC.
Customers with multi year MACC commitments should evaluate routing GitHub through the MACC vehicle. Align GitHub Enterprise term dates with the Microsoft EA term dates to enable coordinated commercial discussions.
The contracted exit path covers documented migration to GitLab Ultimate, Atlassian Bitbucket Premium and Data Center, Microsoft Azure DevOps Services, JetBrains Space, and the self hosted alternatives like Gitea Enterprise and SourceHut.
The documented exit path is a meaningful commercial leverage vector inside the 2026 GitHub commercial discussion alongside the MACC drawdown evaluation and the user, Copilot, and Advanced Security right sizing levers.
The 2026 GitHub Enterprise renewal framework sits inside the broader Redress Compliance Microsoft advisory practice. Engage on a single 2026 GitHub renewal cycle, the coordinated Microsoft EA plus MACC plus GitHub portfolio renewal, or the always on Vendor Shield advisory subscription.
Microsoft Knowledge Hub · Microsoft Services · Microsoft EA Renewal Playbook · Microsoft Azure ELA Negotiation · GitHub Enterprise Copilot Negotiation · GitHub Copilot Business Negotiation · GitLab Ultimate Negotiation · Multi Vendor Negotiation Scorecard · Software Spend Assessment · Vendor Shield
The practice runs four engagement models against the 2026 GitHub Enterprise renewal cycle.
Continue with the GitHub Enterprise Copilot Negotiation, the GitHub Copilot Business Negotiation, the GitLab Ultimate Negotiation, the Microsoft Azure ELA Negotiation, the multi vendor negotiation scorecard, and the complete white paper library.
Read the Microsoft EA Renewal Playbook, the Datadog Enterprise Negotiation, the HashiCorp Terraform and Vault Negotiation, the Atlassian Cloud Enterprise Negotiation, and the Confluent Cloud Negotiation.
The Microsoft EA Renewal Playbook covers the full enterprise Microsoft Agreement framework including the MACC drawdown vehicle that GitHub Enterprise consumption can route through at upper enterprise scale.
Used across more than five hundred enterprise engagements. Independent. Buyer side.
GitHub had opened the 2026 renewal at a USD 3.4m three year commit across 8,200 developers on Enterprise with full GHAS bundle attach, Copilot Enterprise across the full developer pool, and aggressive Actions and Codespaces consumption growth assumptions.
Redress separated the contracted user pool from the active developer baseline. Eight hundred users were leavers, dormant accounts, or bot accounts not yet converted to GitHub Apps. The active developer baseline was 7,400 users after reconciliation.
The Copilot adoption telemetry showed 3,200 active users out of 7,400 assigned seats. The Copilot seat pool compressed to 3,800 with documented adoption headroom. The Copilot Enterprise tier reverted to Business with documented evaluation of knowledge base content adoption.
The GHAS bundle unbundled. Code Security scoped to 280 repositories meeting the three question test out of 1,400 total. Secret Protection retained organization wide. Actions consumption optimized through self hosted runner adoption on the top five pipelines. Codespaces consumption right sized through hibernation policies.
The 2026 renewal closed at USD 2.2m against the USD 3.4m opening proposal. Thirty five percent recovery on the contracted opening commercial proposal across the consolidated GitHub Enterprise footprint. The MACC drawdown vehicle absorbed the consolidated commitment alongside the Microsoft EA renewal.
We work for the buyer. Always. There is no other side of our table.
GitHub Enterprise, GitLab Ultimate, Atlassian Bitbucket, Azure DevOps, JetBrains, HashiCorp, Datadog, and the broader developer tools commercial signals from the Redress Compliance advisory practice.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
