GCP committed use discounts: coverage and utilization risk
Reviewed: 20 October 2026Get a quote for my projectGCP committed use discounts reduce rates for eligible usage under a commitment. Review the applicable commitment family, coverage and utilization risk against the demand that remains after planned workload changes.

On this page
- Gcp committed use discounts: Two families of commitment and what each one locks
- Check the current instrument and purchase options
- Coverage review: five checks before any purchase
- A conservative hourly sizing scenario
- Access and data to prepare
- What the review should deliver
- Official sources
- Common questions about Google Cloud commitments
Gcp committed use discounts: Two families of commitment and what each one locks
| Aspect | Resource-based CUD | Spend-based CUD |
|---|---|---|
| Unit of commitment | vCPUs, memory, GPUs, Local SSD disks and sole-tenant nodes on Compute Engine; premium OS licences are committed separately | A minimum eligible spend, usually evaluated hourly; Flexible Savings Plans use a monthly entitlement window |
| Scope of use | A region and a machine series; shared across projects or limited to one project depending on the CUD scope | Eligible usage under the Cloud Billing account, with service, product and location rules specific to the instrument |
| Services | Compute Engine only | Compute flexible commitments span eligible Compute Engine, GKE and Cloud Run usage; other instruments have their own covered products. Hyperdisk Exapool announced eligibility for spend-based CUDs in October 2026 (check the current spend-based CUD documentation for confirmed scope). |
| Cancellation | Documented as impossible once purchased | No self-service cancellation or billing-account reassignment; contact Cloud Billing Support for purchase mistakes or a requested move, without assuming approval |
| If usage drops | You keep paying the discounted price every hour until the end date | Underutilization depends on the instrument entitlement window; review eligible demand and overage rules in the selected offer |
The current Google Cloud commitment overview distinguishes resource-based commitments, compute flexible commitments, service-specific offers and Flexible Savings Plans. The latter use a monthly entitlement window rather than the standard hourly model. Select the instrument before applying an hourly utilization calculation.
Check the current instrument and purchase options
Google has updated commitment coverage and billing representation. Read the current service documentation and inspect the purchase options available for the billing account. Existing commitments can remain active after an offer stops accepting new purchases.
- Confirm the instrument, service scope and entitlement window.
- Distinguish existing commitments from offers available for a new purchase.
- Record the billing representation used by the utilization query.
- Keep the current product terms and dated estimate with the approval.
Coverage review: five checks before any purchase
- Inventory. List active commitments from the Committed use discounts page of the console, which offers aggregated and instance-level views, and keep an export of the list.
- Scope. Confirm whether each resource-based commitment is shared across the billing account or tied to a project. Read the actual sharing configuration rather than inferring it from a default.
- Representation in billing data. Inspect the current export schema and the tables used for coverage and utilization. Reconcile fees and eligible usage before interpreting the dashboard.
- Post-optimization demand. Rightsizing, a GKE redesign or a region move can reduce eligible use. Model the demand after those changes in the selected instrument’s entitlement window: usually hourly for standard CUDs, monthly for Flexible Savings Plans. Do not use a monthly average as proof of hourly consumption.
- Flexibility value. Compute flexible commitments allow switching between eligible machine series and regions. Resource-based commitments do not. Decide whether that flexibility is worth a different price for your roadmap.
A conservative hourly sizing scenario
For an hourly spend commitment, a lower stable baseline is one conservative candidate, not a universal optimum. In a fictitious example, eligible usage valued at commitment rates ranges from 8 to 14 currency units per hour. A commitment of 10 is partly unused below 10, while excess usage is charged at the applicable on-demand rates. A commitment of 8 is fully used within that observed window, but future demand may fall lower. Compare the total paid cost under several commitments and demand cases before deciding; the hourly example does not apply to monthly Flexible Savings Plans.
Choose the observation window with the workload owners: include month-end and seasonal peaks, and exclude a one-off migration period.

Access and data to prepare
Separate cost review access from export administration and purchase authority. The Cloud Billing access documentation identifies the relevant roles; the billing export guide explains the setup and data availability conditions. Confirm the least-privilege role for each required action.
Prepare the purchase history, the list of projects under each billing account, the planned changes by project for the next twelve months and the name of the person allowed to sign a purchase.
Want your commitments reviewed against your own billing account? Request a quote for this review.
What the review should deliver
- A table of each commitment with type, service, term, hourly or monthly amount, scope and end date.
- Utilization and coverage by commitment, plus the eligible spend that no commitment covers, from your exports.
- The scenarios used for future demand and their owners.
- A purchase recommendation written as a decision for your team to take, with the downside case shown.
Official sources
Official documentation used for this page.
- docs.cloud.google.com/docs/cuds
- docs.cloud.google.com/docs/cuds-spend-based
- docs.cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts
- docs.cloud.google.com/compute/docs/release-notes
- docs.cloud.google.com/billing/docs/how-to/export-data-bigquery
- docs.cloud.google.com/billing/docs/how-to/billing-access
Common questions about Google Cloud commitments
Should an old purchase procedure be reused unchanged?
Check the current instrument, covered products and purchase options for the billing account. Historical procedures can describe an earlier billing model or an offer no longer available for new purchases.
Can we state one discount for all CUDs?
No. Product, term, machine series and region change the rate. Use the price shown for the specific purchase, dated, and keep it with the decision record.
Can a commitment be cancelled if our plans change?
The documentation for both resource-based and spend-based commitments says they cannot be cancelled. For a configuration error on a spend-based commitment, it points to Cloud Billing Support.
Related workload decisions
Continue the review with bigquery pricing. Each guide addresses a separate decision within the same cloud cost boundary.
Continue your review
- FinOps consulting: cloud cost review and implementation scope
- Request a scoped FinOps quote
- How your request is handled: from enquiry to proposal
- GCP cost optimization consulting: scope and evidence
- Azure reservations vs savings plan: model the commitment
- Kubernetes cost optimization consulting for EKS, AKS and GKE
Launch my project
Share the decision you need to make and get a quote scoped to it.
Launch my projectFor GCP committed use discounts vs sustained use discounts, Google documents sustained use discounts as automatic discounts for eligible Compute Engine usage over the billing month. They are different from buying a commitment. Check machine-family and discount-combination eligibility instead of adding both discounts to the same usage assumption.