Google Cloud flexible CUDs: spend-based model and 2026 migration
Published and reviewed: 1 October 2026
Scope my cloud cost reviewGoogle Cloud announced wider flexible CUD coverage on 15 July 2025 and reported all billing accounts migrated on 6 February 2026.

On this page
The two dated notes
The Compute Engine release notes of 15 July 2025 say that compute flexible committed use discounts offer expanded coverage: memory-optimized M1, M2, M3 and M4 VMs, compute-optimized H3 instances, Cloud Run services with request-based billing, and Cloud Run functions. To receive it, a Cloud Billing account had to opt in to the new spend-based CUD model. Accounts meeting specific criteria were opted in automatically, and the note said that on 21 January 2026 all remaining accounts would migrate automatically.
The release notes of 6 February 2026 then state that expanded coverage is available to all Cloud Billing accounts, that all of them have been automatically migrated to the new model, and that nobody needs to opt in any more. The opt-in wording of July 2025 therefore describes a historical rollout, not today's procedure.
What the new model changes in your data
Google's spend-based CUD documentation explains the change: under the new model, usage is billed directly at the discounted rate, where the legacy model billed usage at list price and offset it with a credit. The commitment itself is expressed differently: you commit to the discounted spend, the amount you actually pay, where the legacy model used the on-demand value at list price. Reports show net savings under the new model and the gross credit amount under the legacy one.
Consequences for finance reports and exports
A report that compares months before and after a billing account's migration date can show a change in how discounts appear without any change in economics. Write the migration date next to the comparison and explain the change of presentation. The date for your account is shown in a notification on the Billing Overview page of the console, according to Google's documentation, and the 6 February 2026 note says every account has now migrated.
- Check how your export shows commitment fees, utilization offsets and benefit consumption today, and how they looked before.
- Re-run any saving estimate that assumed the legacy credit presentation.
- If an internal procedure still contains an « opt in to the new model » step, replace it with current instructions from the documentation.
Evaluating a commitment under the current model
The documentation states that commitments cannot be cancelled, that you pay the agreed monthly amount for the term, and that unused commitment does not roll over from one hour to the next: eligible usage above the commitment is billed at the standard rate without discount, and usage below it still costs the full commitment. A purchase case therefore needs the low utilization case alongside the expected one. The commitment break-even calculator can test it with your own figures, and the GCP committed use discounts guide lists the coverage and risk questions.
Ask a provider to state which services and machine series your future demand uses, whether they are eligible under the offer as it stands today, and which rate and term the model uses. A generic discount percentage is not a substitute for the rate in your own billing account.
Primary sources
The Compute Engine release notes, which contain both dated entries, and Google's spend-based CUD documentation:
Continue your review
Scope my project with a specialist
Tell us your cloud, your spend band and your priority. A specialist studies them and quotes for the work.
Scope my project