Sustained Use Discounts and How They Stack With CUDs

Sustained use discounts and how they stack with CUDs is one of the most misunderstood parts of Google Cloud pricing, and the confusion costs buyers money. Sustained use discounts apply automatically to eligible resources the longer they run in a month, with no commitment, while committed use discounts give a deeper rate in exchange for a one or three year commitment, as of June 2026. The key fact is that they do not double stack on the same resource. This guide explains the interaction so you can model the real discount before you commit.

Sustained use discounts and how they stack with CUDs

A sustained use discount is automatic. For eligible resources, Google increases the discount the longer the resource runs within a billing month, rewarding steady usage without any commitment or contract. You do nothing to earn it beyond running the workload, and you keep full flexibility to change or stop it at any time.

A committed use discount is the opposite trade. You commit to a quantity of resources or an hourly amount of spend for one or three years, and in return you receive a deeper, predictable rate. The discount is larger than a sustained use discount, but you accept lock in and the risk of paying for committed usage you do not consume.

Here is the rule that matters. CUDs and sustained use discounts do not double stack on the same resource, as of June 2026. When a resource is covered by a committed use discount, the committed rate applies and the sustained use discount does not add on top of it. Sustained use discounts apply to eligible usage that a CUD is not already covering. So the two are best understood as covering different layers of your usage, not multiplying on the same one.

Why the no double stack rule changes your math

Buyers often estimate the value of a CUD by adding it to the sustained use discount they already receive. That overstates the benefit, because the committed rate replaces the sustained use discount on the covered resource rather than adding to it. The real gain from a CUD is the difference between the committed rate and the sustained use discount you would have received anyway, not the difference from full list price.

This matters most for steady, always on workloads, which are exactly the workloads that already earn strong sustained use discounts automatically. The incremental benefit of committing them can be smaller than it first appears, so the lock in must be justified by that incremental gain, not by the gross discount off list. Always compare the committed rate to the realistic baseline, which includes sustained use discounts.

Model it resource by resource. For each layer of usage, ask what discount it would earn with no commitment, then what the committed rate would be, and commit only where the incremental saving justifies the term lock in. This is the difference between a CUD that pays for itself and one that simply moves an existing discount into a contract.

Layering CUDs, sustained use discounts, and flexible capacity

The efficient structure treats your usage as layers. The stable baseline that runs continuously is a candidate for a committed use discount, because you are confident it will persist for the term. The variable layer above the baseline is better left to sustained use discounts, which reward steady usage automatically without locking you in.

The most variable and interruptible workloads can run on spot or preemptible capacity, which is cheaper still and carries no commitment, though it can be reclaimed. We cover the full picture in combining CUDs, sustained use discounts, and spot VMs. The point is that no single discount mechanism is right for the whole estate. The savings come from matching each layer to the right instrument.

Sizing the committed layer is the discipline that ties it together. Commit only to the floor you will sustain, let sustained use discounts cover the steady remainder, and push the truly variable work to flexible capacity. Our guide to sizing GCP CUDs to avoid overcommitment walks through finding that floor from your usage data.

What this means for your negotiation

When Google or a reseller presents a CUD discount off list price, translate it into the incremental gain over your sustained use discount baseline. That translation is where buyers either protect value or give it away, because the headline number always looks larger than the real benefit. Insist on seeing the math against your actual usage, not against list.

At scale, the conversation widens to custom private pricing and workload agreements, which can blend committed and flexible spend on better terms than standard CUDs. Sustained use discounts remain part of the baseline you measure any private pricing against, so they stay relevant even in a bespoke deal.

The buyer who understands the no double stack rule negotiates from the real number. The buyer who does not overpays for a commitment that mostly replaces a discount they already had. Modeling the blended discount before you sign is the whole game, and it is exactly what an independent buyer side review delivers.

A worked example of the blended discount

Suppose an always on workload already earns a meaningful sustained use discount automatically each month. A reseller presents a committed use discount as a large reduction off list and frames it as additional savings. The framing is misleading, because the committed rate replaces the sustained use discount on that workload rather than adding to it.

The real benefit is the gap between the committed rate and the sustained use rate the workload would have earned anyway. That gap is usually a fraction of the discount off list. If the incremental gain is small, the one or three year lock in may not be worth it for that workload, and the money is better protected by staying flexible.

Do this calculation for every layer of usage before committing. Where the incremental gain over the sustained baseline is large and the usage is durable, commit. Where it is small or the usage is uncertain, do not. Negotiating from the blended number, not the list number, is how buyers keep the value that the headline discount tries to give away.

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.

Model the real blended discount before you commit.

A CONFIDENTIAL COMMITMENT REVIEW BEFORE YOU SIGN