GitHub Enterprise Renewal Negotiation Guide

Pricing structures and available terms vary by plan and contract. Confirm the current terms with the vendor before negotiating.

How GitHub Enterprise pricing is structured

Core GitHub Team and Enterprise subscriptions have per-user pricing. Enterprise includes additional administrative controls; security features and eligibility depend on the plan and add-ons. GitHub Actions minutes and artifact/cache storage have included allowances for eligible plans, with extra usage billed under their own rules. GitHub Packages has separate billing rules. Review each product independently.

For engineering-heavy organizations, Actions minutes can be a volatile cost line — a change in CI pipeline design, test suite growth, or a shift to running more jobs in parallel can meaningfully increase minute consumption without anyone deciding that as a budget choice. It accumulates the way cloud infrastructure costs do: gradually, as a byproduct of engineering decisions made for reasons unrelated to cost.

What to check before renewing

• Seat count against the assigned roster. Review offboarding and usage with engineering owners rather than assuming all provisioned users need an ongoing paid seat.
• Actions minutes and runner usage. Compare the trend against organic CI growth and possible inefficiencies such as redundant jobs or failed workflow triggers.
• Artifact, cache and Packages storage. Review the separate billing rules and retention settings for each rather than treating them as one storage allowance.
• Enterprise-tier features actually in use. Check which security, audit and governance features are included on your plan, and whether your team uses them.

Where the real leverage is

• Address Actions minutes waste before negotiating the baseline. Redundant workflow triggers, overly broad CI matrices (testing against more environment combinations than the product actually ships to), and missing caching are common, fixable sources of excess minute consumption — cutting these reduces the actual usage number before any negotiation conversation, the same principle as seat right-sizing.
• Negotiate seats and usage add-ons as one renewal, not separately. Ask whether a bundled quote for seats, Actions and storage offers a better fit than isolated line-item requests after the fact.
• If core GitHub and GitHub Copilot renew near each other, request a combined quote. They are distinct products with different billing; confirm whether aligned dates or terms actually improve the offer.
• Artifact and storage retention policy as a free lever. Setting a retention policy that automatically cleans up old build artifacts and container images reduces storage costs without any negotiation at all — worth doing regardless of where the renewal conversation lands.

A worked example

Illustrative scenario: an engineering team with 180 developer seats sees Actions minutes rise 60% year over year while headcount grew about 15%. Redundant CI jobs and missing dependency caching explain part of the difference. Fixing those workflows changes the forecast before any commercial discussion; actual rates and allowances depend on the plan.