What Are Google Cloud Committed Use Discounts

What are Google Cloud committed use discounts, and what do they cost you in flexibility? Google Cloud committed use discounts, or CUDs, give you lower pricing in exchange for committing to a steady level of usage or spend over a one or three year term, as of June 2026. They come in two main forms, they sit alongside automatic sustained use discounts, and like any commitment they trade a discount for lock in. This guide explains how they work from the buyer side.

What are Google Cloud committed use discounts, in plain terms

Google Cloud committed use discounts are agreements to use or spend a defined amount on Google Cloud for one or three years in return for a reduced rate. The longer the term and the larger the commitment, the deeper the discount, but the more usage you lock in. Because the commitment runs for the full term, the central buyer question is whether your real usage will stay above the committed level for the whole period.

There are two principal types. Resource based CUDs commit you to a quantity of compute resources, such as vCPU and memory in a region, and apply across instance types in that family, which gives useful flexibility. Spend based CUDs commit you to an hourly dollar amount of spend on eligible services and apply more broadly. We compare the two in detail in our guide to resource based versus spend based CUDs explained.

Sitting underneath both is the sustained use discount, which Google applies automatically to certain resources the longer they run in a month, with no commitment required. CUDs and sustained use discounts do not double stack on the same resource, as of June 2026, so understanding how they interact is part of reading the real discount.

How CUDs differ from AWS and Azure commitments

Buyers coming from AWS or Azure often assume CUDs behave like an Enterprise Discount Program or a Microsoft Azure Consumption Commitment. They do not, quite. A resource based CUD commits to capacity rather than a total dollar figure, and it flexes across instance types in the family, which is more forgiving than a fixed dollar commitment when your shape of usage shifts.

Spend based CUDs are closer to a dollar commitment, but they are expressed as an hourly spend rate on eligible services rather than a single multi year number. Automatic sustained use discounts have no real equivalent on the other providers, because they reward steady usage without any commitment at all. For a full cross provider view, see our guide on how GCP CUD discounts compare to AWS and Azure.

Large enterprises can also negotiate custom private pricing and workload agreements with Google that go beyond standard CUDs. These behave more like the private pricing agreements on AWS and Azure, and they are where the real negotiation happens at scale.

The buyer risks inside a CUD

The first risk is overcommitment. If you commit to more usage or spend than you sustain, you still pay for the committed level, so the discount you chased can turn into waste. Size CUDs to the floor of your usage, not the average and never the peak. We cover this in sizing GCP CUDs to avoid overcommitment.

The second risk is the term itself. A three year CUD deepens the discount but removes flexibility and future leverage for the full period. If your architecture or your workloads may change, a one year term or a smaller commitment can be the more valuable choice even at a shallower rate. The third risk is coverage gaps, where bursty or seasonal workloads sit above your committed baseline and pay full rate anyway.

The fourth risk is assuming CUDs and sustained use discounts add together. They do not double stack on the same resource, as of June 2026. Model the real blended discount, including how spot or preemptible capacity and Marketplace spend fit, before you decide the commitment is worth it.

How to approach a CUD as a buyer

Start with your usage data. Identify the stable baseline that runs continuously, commit to that, and let everything above it stay flexible on demand, sustained use discounts, or spot capacity. This keeps the discount where it is safe and avoids paying for committed capacity you do not use. Prefer resource based CUDs where you want instance flexibility, and spend based CUDs where your services vary but your spend floor is steady.

Weigh the term against your forecast. A one year commitment costs a few points of discount but preserves the freedom to re sized or re architect. For large spend, open the conversation about custom private pricing, because standard CUDs are the starting point, not the ceiling. Bring a credible alternative, since a multicloud option or a plan to optimize first changes how Google engages.

Treat the whole thing as a negotiation, not a checkout. The published CUD rates are a default. Sizing, term, the mix of resource based and spend based commitments, and any private pricing are all on the table when the numbers are large enough to matter.

A practical way to start with CUDs

If you are new to committed use discounts, start small and let data lead. Pull at least a few months of usage and identify the compute that runs continuously, the steady but variable layer above it, and the truly interruptible work. Those three layers map cleanly to three instruments: committed use discounts for the stable base, sustained use discounts for the steady remainder, and spot or preemptible capacity for the interruptible tail.

Commit only the base layer at first, and prefer a one year term while you learn how your usage behaves under commitment. The discount is slightly shallower than a three year term, but you keep the freedom to re size as you gain confidence. You can always deepen and extend commitments later, once the data shows the floor is real and durable.

Resist the urge to commit to the average or the forecast. Both sit above the true floor, and the gap between them is exactly where overcommitment lives. The conservative base you can defend with history is worth more than the aggressive number that chases a deeper headline rate and forfeits value when usage dips.

Sources, method, and as of date

The program mechanics and ranges on this page reflect publicly available provider documentation and our buyer side negotiation experience, as of June 2026. AWS, Microsoft, and Google revise their programs frequently, so treat every figure as a point in time reference and confirm the current terms directly with the provider before you act.

This page is commercial negotiation advisory, not legal, tax, or accounting advice. We are independent and buyer side, with no reseller margin and no hyperscaler incentive, and we are paid only by the buyer. For interpretation of any commitment contract or program term, engage your own legal counsel.

Size your Google Cloud commitment before you sign it.

A CONFIDENTIAL COMMITMENT REVIEW BEFORE YOU SIGN