GitHub Pre-Purchase Plans: the rise of AI consumption pricing

Microsoft is introducing two new GitHub Pre-Purchase Plans that allow organizations to purchase GitHub consumption in advance at reduced rates.

At first glance, this seems like a logical extension of familiar constructs such as Azure Reserved Instances, Azure Savings Plans, and Microsoft Azure Consumption Commitments.

The true meaning, however, lies deeper.

GitHub is increasingly evolving from a traditional licensing product into a consumption-driven platform where AI usage, automation, and development capacity determine the final bill.

For CIOs, FinOps teams, cloud governance specialists, software asset managers, and procurement departments, this fundamentally changes how GitHub budgets must be planned, managed, and controlled.

The introduction of GitHub Pre-Purchase Plans shows where enterprise software is heading in a broader sense: a world where AI consumption is becoming more important than user licenses.

From seat-based licensing to AI consumption pricing

For years, GitHub was financially relatively simple.

Organizations primarily paid for GitHub Enterprise, GitHub Team, and GitHub Copilot. The number of users largely determined the costs, and budgets were relatively predictable.

That model changes rapidly.

AI functionality creates new consumable units independent of the number of developers. Examples include GitHub AI Credits, GitHub Actions, Codespaces, Advanced Security, and future AI agents that perform development work independently.

As a result, GitHub is shifting from a predictable licensing model to a platform where actual usage is becoming increasingly important.

We are now seeing the same development in Microsoft Copilot Credits, Azure AI Services, SAP AI Units, and other AI-driven software platforms.

The central question therefore changes from:

How many users do we have?

to:

“How much AI consumption do we expect?”

That seems like a small difference.

In reality, it changes the way software is budgeted, managed, and optimized.

What are GitHub Pre-Purchase Plans?

Microsoft introduces two separate models.

The first model is the GitHub AI Credits Pre-Purchase Plan. This variant focuses specifically on AI Credits and is intended for organizations that want to purchase AI capacity in advance for GitHub Copilot, AI agents, and future AI functionalities.

The second model is the broader GitHub Pre-Purchase Plan.

This allows organizations to place multiple GitHub services under a single commitment structure, including GitHub Enterprise, GitHub Copilot, GitHub Actions, GitHub Codespaces, GitHub Advanced Security, and GitHub AI Credits.

Organizations purchase GitHub Commit Units (GCUs) in advance, which are consumed over a period of twelve months.

Depending on the size of the commitment, discounts can amount to approximately fifteen percent.

The introduction of these plans is closely linked to the rapid growth of GitHub Copilot within enterprise organizations. As more developers use AI functionality, it is becoming increasingly difficult for organizations to accurately predict future costs.

GitHub Pre-Purchase Plans are therefore not just a new discount mechanism. They are also a tool with which Microsoft is moving organizations increasingly towards consumption-driven software budgeting.

Why Microsoft is doing this

Microsoft positions the new plans as an instrument for budget certainty.

From a customer perspective, that makes sense. Organizations gain more predictability regarding future GitHub costs and can more easily incorporate AI consumption into their budgeting process.

From Microsoft's perspective, however, there is more at play.

GitHub follows the same commercial logic we previously saw with Azure, Microsoft 365, and other cloud platforms. By having customers commit to a specific consumption level in advance, greater revenue certainty is created and future consumption becomes more predictable.

Commitment models offer suppliers several advantages:

predictable revenue
longer customer retention
better forecasting
more consumption growth
stronger platform dependency

We are already familiar with that mechanism from Azure Reserved Instances, Azure Savings Plans, Enterprise Agreements, and other cloud commitments.

The introduction of GitHub Commitments therefore fits within a broader development in which software vendors are increasingly shifting their revenue model from licenses to consumption.

For organizations, this is not necessarily negative. However, it does mean that the quality of forecasting is becoming increasingly important for the final financial result.

GitHub is becoming a FinOps issue

Many organizations still view GitHub as a developer tool.

That picture is becoming increasingly inaccurate.

The introduction of GitHub Copilot, GitHub AI Credits, Actions, Codespaces, and other consumption-based services is causing GitHub to increasingly acquire characteristics of a cloud platform. Costs are no longer determined solely by the number of users, but increasingly by actual usage.

As a result, responsibility for GitHub is also shifting within organizations.

While GitHub used to fall primarily under the responsibility of development teams, nowadays more and more disciplines are becoming involved in decision-making, governance, and cost management.

Increasingly, we see involvement from:

CIO Office
Development Leadership
FinOps
　
Software Asset Management
Security
Cloud Governance
Enterprise Architecture

That is a logical consequence of the growing financial impact of AI-supported software development.

Organizations must manage not only licenses, but also AI Credits, GitHub Actions, agent workloads, security scans, build workloads, and other forms of platform consumption.

GitHub thereby becomes part of the same financial governance domain as Azure, AWS, and other consumption platforms.

Why GitHub Copilot accelerates the growth of GitHub Commitments

The introduction of GitHub Pre-Purchase Plans is closely linked to the rapid adoption of GitHub Copilot within enterprise organizations.

Whereas GitHub costs used to depend largely on the number of users, AI functionality is creating new forms of consumption that are much more difficult to predict.

As organizations make greater use of GitHub Copilot, AI Credits, AI agents, and automated development processes, the need for more budget control arises.

GitHub Commitments are therefore not only a new discount mechanism. They also offer a response to the growing financial uncertainty brought about by AI consumption.

The biggest financial pitfall: unused commitments

The commitment model offers clear advantages.

Lower rates, greater budget predictability, and simpler financial planning make such structures attractive to many organizations.

At the same time, a known risk arises.

Underutilization.

An organization that commits €500.000 and ultimately realizes only €350.000 in GitHub consumption loses a large part of the expected financial benefit.

We have seen this pattern for years with Azure Reservations, Azure Savings Plans, Enterprise Agreements, Oracle ULAs and other cloud commitments.

The discount only has value when the underlying usage is correctly predicted.

That ultimately makes forecasting more important than the discount itself.

GitHub and Azure: the risk of stacking commitments

One of the most underestimated risks of the new GitHub Commitments is the creation of multiple parallel commitments within the same software landscape.

Many organizations already have various commitment structures in place today.

Think, for example, of Azure Commitments, Azure Savings Plans, Azure Reserved Instances, Microsoft Copilot Credits, and GitHub Commitments.

Individually, these structures can be financially attractive. After all, every supplier presents them as a way to obtain a discount and make budgets more predictable.

The risk arises when these commitments are assessed jointly.

An organization may have simultaneously committed to Azure capacity, GitHub consumption, and AI workloads, while actual usage falls short of expectations.

We call this phenomenon commitment stacking.

The problem is not that a single commitment is misjudged. The problem arises when multiple commitments are simultaneously based on optimistic growth expectations.

For CIOs and FinOps teams, the challenge therefore shifts from optimizing individual contracts to managing the entire commitment portfolio.

The question is no longer which discount is available.

The question becomes how much future consumption is actually realistic.

It is precisely there that a new governance challenge arises for enterprise organizations.

How do you predict GitHub usage?

Before an organization makes a GitHub commitment, insight into future consumption is needed.

An effective approach begins with analyzing historical usage of GitHub Actions, Codespaces, security scans, and Copilot adoption.

Next, organizations must model AI growth scenarios. AI usage often grows much faster than traditional software adoption. As a result, forecasts based solely on current usage frequently prove to be too conservative.

It is also important to distinguish between pilots and production use. Many organizations extrapolate pilot results directly to the entire organization, leading to inaccurate predictions.

In addition, FinOps reporting is essential. AI consumption must be made transparent at the team, department, and cost center levels.

Finally, consumption forecasting requires continuous evaluation. A commitment should never be based on a one-off estimate.

Why GitHub Pre-Purchase Plans are relevant for CIOs, procurement, and FinOps

The introduction of GitHub Pre-Purchase Plans affects various stakeholders within the organization.

For CIOs, it is primarily about predictability. As AI functionality becomes a larger part of software development, there arises a need for control over future costs and governance surrounding AI consumption.

For procurement teams, the focus is shifting to contract terms. The amount of the discount is only one part of the negotiation. Much more important are flexibility, reporting, modification options, and conditions for underutilization.

A new responsibility is emerging for FinOps teams. GitHub is increasingly becoming a platform whose usage must be actively monitored, analyzed, and optimized.

Software Asset Management teams are also taking on a new role. Whereas software governance revolved around users, devices, and licenses for years, there is now a need for insight into AI consumption, platform usage, and future growth.

GitHub is thereby evolving from a development tool into a business-critical consumption platform.

What does this mean for contract negotiations?

Many organizations will focus primarily on the offered discount.

That is rarely the most important negotiation variable.

Strategic conclusion

GitHub Pre-Purchase Plans are not standalone price changes.

They provide a clear indication of the direction in which Microsoft, GitHub, and the broader software market are developing.

The rise of GitHub Copilot, AI Credits, agentic development, and consumption-based pricing models makes the financial management of software more complex than ever.

For CIOs, FinOps teams, and procurement organizations, the question is no longer how many licenses are needed.

The question is how much consumption will actually take place.

The challenge is shifting from license management to consumption management.

Organizations that have insight into their future GitHub consumption can benefit from the new commitment models.

Organizations that look solely at the discount run the risk of making the same mistakes that were previously evident with cloud commitments, Enterprise Agreements, and other consumption-based contract structures.

And that is precisely where the greatest cost savings or the biggest financial surprises will arise.

GitHub is changing from a licensing product to a consumption platform. Is your organization prepared for this?

As GitHub Copilot, AI Credits, and other consumption-based services become a larger part of the IT landscape, the challenges surrounding forecasting, governance, and contract management are also increasing.

BeSharp Experts helps CIOs, procurement teams, and FinOps organizations assess GitHub Commitments, Microsoft contracts, and AI consumption models.

Prevent new AI pricing models from leading to the same financial surprises that many organizations previously saw with Azure Commitments, Enterprise Agreements, and other consumption-based contracts.

Phone number

GitHub Pre-Purchase Plans: why Microsoft is changing GitHub from a licensing product to a consumption platform