The three hyperscaler commitment programmes — AWS Enterprise Discount Programme, Azure Microsoft Consumption Commitment, GCP Committed Use Discounts — and the negotiation choices that determine three-year cloud cost. Written by the cloud advisory practice.
The hyperscaler commitment programmes — AWS Enterprise Discount Programme, Azure Microsoft Consumption Commitment, Google Cloud Committed Use Discounts — share a common commercial architecture and differ in important details. The buyer who negotiates one without understanding the architecture across all three gets a worse outcome than the buyer who treats them as variations on a single framework. This guide sets out that framework and shows where the three programmes diverge in ways that matter for the buyer.
This is the cross-cut for buyers with active commitments to more than one hyperscaler, or for buyers preparing a first commitment whose downstream implications they want to understand. It is also the right reference for buyers whose third-party software (Databricks, Snowflake, ServiceNow, Salesforce on hyperscaler) consumes against the hyperscaler commit.
The framework is divided into eight sections. The opening sections set out the three programmes side-by-side. The middle sections cover commit shape, pooled vs scoped consumption, the marketplace mechanics that interact with third-party software contracts, co-sell economics and the growth-rate test. The closing sections cover renewal posture and a worked example.
This is not a cloud architecture primer. We assume readers understand the basics of compute, storage, network, database and platform-services consumption, and that the buyer has a FinOps capability of some kind. We also have vendor-specific deep-dive papers for AWS EDP and Google Cloud commit strategy — this framework sits above them in the cross-cloud layer.
The lead author runs the cloud advisory practice at SoftwareContractNegotiation. The practice has supported more than seventy hyperscaler commit negotiations since 2018, across all three major hyperscalers. The paper draws on engagement data anonymised for confidentiality. Independent firms such as Redress Compliance are referenced where their published analysis informs a specific decision.
AWS Enterprise Discount Programme, Azure MACC, GCP CUD — what is common across the three and what differs.
Flat, ramped and back-loaded commits across the three programmes, and the workload patterns each shape rewards.
Account-wide pooled commits versus service-scoped commits, and the flexibility-versus-rate trade-off at each.
How third-party software (Databricks, Snowflake, ServiceNow on hyperscaler) retires against the hyperscaler commit through the marketplace channel.
The hyperscaler co-sell motion, its effect on third-party pricing, and the leverage that the co-sell incentive creates for the buyer.
The forecast-vs-actual growth test that the hyperscaler applies, the over-commit and under-commit penalties, and the defensible forecast posture.
The renewal conversation, the carry-over rules across the three programmes, and the leverage at the end of the term.
A complete redacted engagement — multi-cloud commit shape, marketplace routing, third-party software retirement and the three-year net outcome.
The commit shape, marketplace mechanics and renewal posture are set in the six weeks before signature. If a hyperscaler commit closes within that window, the work starts now. The first conversation is free of charge and free of obligation.