Private pricing agreements explained.

These agreements move the most money of any single decision in cloud procurement, and they carry the most risk, because the commitment is contractual and the shortfall is owed whether or not you use it. Here is what each provider actually offers, how the discounts stack, and the clauses worth negotiating before you sign.

What exactly is a private pricing agreement?

Public cloud list prices are the same for everyone. A private pricing agreement is the mechanism a provider uses to go below that list for large buyers without publishing the number. In exchange, you commit to spend at least a stated amount over the term. Cross the commitment and you keep the discount; fall short and, in most agreements, you still owe the gap. The discount typically grows with the size and length of the commitment, which is why providers push for a larger number and a longer term.

The important mental model is that the agreement sits above your usage, not inside it. It does not decide which instance runs or which Reservation you buy. It sets a spend floor and a discount rate, then watches your aggregate consumption draw down against the commitment. That separation is why an agreement can stack with every other lever you already pull.

How does each cloud structure its agreement?

The shape is similar across providers, but the mechanics and the traps differ, so treat each one on its own terms.

AWS Enterprise Discount Program. The EDP trades a multi year spend commitment for a discount tier that applies across most AWS services. It stacks on top of Savings Plans and Reserved Instances, so the EDP percentage and the Savings Plan rate both reduce the same bill. AWS Marketplace spend can often count toward the commitment, which matters when you forecast the floor. The risk is committing to a number inflated by one off projects that will not recur.

Azure MACC. The Microsoft Azure Consumption Commitment carries an explicit shortfall clause: unspent commitment at the end of the term is still owed. Azure Reservations, the Azure Savings Plan for compute, and most first party Azure services draw down the MACC, and eligible Azure Marketplace purchases can too. Because the clock is unforgiving, MACC sizing should be the most conservative of any provider.

GCP enterprise agreements. GCP committed spend deals follow the same use it or lose it structure. They sit above spend based and resource based Committed Use Discounts and the automatic sustained use discounts, so the negotiated tier and the CUD rate stack. Watch how BigQuery capacity and premium network tiers count toward the commitment, because they can move the floor materially.

OCI Universal Credits. Oracle sells Universal Credits as an annual flex commitment that draws down as you consume any eligible OCI service. Support Rewards can offset a portion of on premises Oracle support fees as you spend, which changes the true cost of the commitment for Oracle heavy estates. As with the others, the credits are use it or lose it within the term.

How do the discounts stack?

The single most misunderstood point about these agreements is that they do not replace your commitment instruments. They compound with them. A Savings Plan reduces the rate on a workload; the EDP then reduces the resulting bill again. The same is true of Azure Reservations under a MACC, CUDs under a GCP agreement, and Universal Credits drawdown on OCI. So the right sequence is to size your per workload commitments to a risk adjusted forecast first, then negotiate the enterprise agreement on top of the spend that survives that discipline, not on a gross run rate.

Which clauses actually protect the buyer?

The discount tier gets all the attention, but the value of an agreement lives in the terms around it. Negotiate the commitment number down to your defensible floor so the shortfall clause never bites. Push for ramp flexibility so the floor rises with your real adoption curve rather than starting at full height on day one. Ask what counts toward the commitment, because Marketplace spend, first party services, and support drawdown can change whether you clear the floor comfortably or scrape it. Seek the right to true up to a better tier if you grow, without being locked out of renegotiation if you shrink. And confirm what happens at renewal, since the strongest leverage you will ever have is the credible option to move workloads, which evaporates the moment you sign a term that makes leaving expensive.

When is a private pricing agreement the wrong move?

An agreement is the wrong move when your forecast is not defensible. If you cannot separate the stable baseline from variable and one off spend, you cannot size the commitment safely, and a discount on a floor you miss is a penalty. It is also the wrong move when the term length removes your ability to rearchitect or repatriate workloads you already know you want to move. A discount that locks you into a service you are trying to leave is negative value. The test is simple: commit only to spend you would make anyway over the term, at a number you can defend to your board, and treat anything above that as risk you are buying, not savings you are capturing.

Negotiate the agreement from the buyer side

We size and negotiate private pricing agreements across AWS, Azure, GCP, and OCI from your side of the table, with zero provider commissions, so the discount tier and the contract terms both serve you. Our guarantee: we reduce your cloud spend or we reimburse our service fee. Pricing is either a Fixed Fee scoped up front or Gainshare, a share of verified savings with no retainer and no risk.