This page describes how committed use discounts work with Cloud SQL.

What are Cloud SQL committed use discounts?

Committed use discounts (CUDs) for Cloud SQL provide deeply discountedprices in exchange for your commitment to continuously use database instances ina particular region for a one- or three-year term.

Cloud SQL CUDs are ideal for workloads with predictableresource needs. You commit to a consistent amount of usage, measured in cost perhour of equivalent on-demand spending, for a one- or three-year term. Inexchange, you receive a discounted rate for Google Cloud SQL on theapplicable usage your commitment covers.

Important: This page explains the new and improved committed-use discounts (CUDs) program, which applies to any customers who purchase their first CUDs on or afterJuly 15, 2025. Customers can opt in now to get the new CUD experience. For more information, seeImprovements to the spend-based CUDs program.

You can purchase CUDs from any Cloud Billingaccount, and the discount applies to any eligible usage in projects that theCloud Billing account pays for. When you purchase a Cloud SQLCUD, you pay the same commitment fee for the entirety of thecommitment term, even if the price of applicable usage changes. You stillreceive the same discount percentage on applicable usage in the event of a pricechange. The commitment fee is billed monthly.

IMPORTANT:Any overage in usage is charged at the on-demand rate.

For more information about your bill, seeAnalyze the effectiveness of yourspend-based committed use discounts.

What types of usage are Cloud SQL CUDs used for?

CUDs automatically apply to aggregate Cloud SQL instanceusage in a region, giving you low, predictable costs, without the need to makeany manual changes or updates yourself. This flexibility helps you achieve highutilization rates across your commitments, saving you time and money.

Cloud SQL CUDs apply to all Cloud SQL databaseinstance CPU and memory usage in the region in which you have committed,except shared CPU machine types (such as db-f1-micro and db-g1-small).Cloud SQL CUDs apply to usage from all supporteddatabases (MySQL, PostgreSQL, and SQL Server). Cloud SQL CUDsdo notapply to storage, backups, IP Addresses, outbound data transfer, or licensing.

Cloud SQL CUDs automatically apply to bothCloud SQL Enterprise edition and Cloud SQL Enterprise Plus editioninstances within the same region.

Pricing

• 25% discount: You get this by committing to a 1-year term. For the duration of your term, you pay the Cloud SQL CUD 1-year price (consumption model ID 61F8-639B-D89C) as your committed hourly spend amount.
• 52% discount: You get this by committing to a 3-year term. For the duration of your term, you pay the Cloud SQL CUD 3-year price (consumption model ID 52FB-D69D-95BE) as your committed hourly spend amount.

This discount significantly reduces Cloud SQL costs. These discount percentages are the same in every region.

For a list of applicable SKUs, seeCloud SQL CUD Eligible SKUs.

Seecommitted use discount pricing for pricingdetails.

Purchase Cloud SQL CUDs

After your purchase a CUD, you cannot cancel your commitment. Make sure the size and duration of your commitment aligns with both your historical and your expected minimum expenditure on Cloud SQL for PostgreSQL capacity. For more information, seeCancelling commitments.

To purchase or manage Cloud SQL for PostgreSQL committed use discounts for yourCloud Billing account, follow the instructions atPurchasing spend-based commitments.

Example use case

Key points to keep in mind:

• Cloud SQL CUDs apply only to vCPUs and memory.
• Cloud SQL CUDsdo not apply to storage, backups,IP Addresses, network egress, or licensing.
• Cloud SQL CUDs apply to all instances in a givenregion.
• Cloud SQL CUDs are measured indollars per hourlyon-demand commitment.
• Cloud SQL CUDs can be applied to bothCloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition.If you have an existing CUD with a Cloud SQL Enterprise edition instance and want to upgradethe instance to Cloud SQL Enterprise Plus edition, then your existing CUD can be applied to coverall or part of the cost of the newly upgraded instance.

How to calculate an hourly on-demand commitment

When calculating the hourly rate for vCPUs and memory across allinstances in the region where you want to benefit from a CUD, first considerwhether it saves money for your situation. Any usage higher than that limit ischarged at the regular on-demand price.

For example:

• Assume you are running 100 instances in each of two different regions. Theinstances are using 2 high availability (HA) vCPUs with 7.5GB HA RAM, and arelocated in regionus-central1 and Singaporeasia-southeast1. You're interested in buying a 1-year CUD.

In the legacy CUDs program, your commitment amount is the on-demand price instead. For more information about the differences between the legacy and new spend-based CUDs program, seeImprovements to the spend-based CUDs program.

From thepricing table, you can calculate the approximate hourly one-year commitment cost as follows:

• us-central1

  • 100 * 2x HA vCPU * ($0.0826 per vCPU - 25% discount) per hour = ~$12.39 per hour
  • 100 * 7.5GB HA RAM * ($0.0140 per GB - 25% discount) per hour = ~$7.875 per hour
  • For a total of $20.27 per hour in discounted committed use hourly pricing

• asia-southeast1

  • 100 * 2x HA vCPU * ($0.1156 per vCPU - 25% discount) per hour = ~$17.34 per hour
  • 100 * 7.5GB HA RAM * ($0.0735 per GB - 25% discount) per hour = ~$11.025 per hour
  • For a total of $28.37 per hour in discounted committed use hourly pricing

Calculating the monthly cost (730 hours in a month):

• us-central1

  • On-demand pricing = ($26.50 per hour * 730 hours) = $19,345 per month
  • After 25% 1-year CUD discount = ~$14,508 per month
  • For a total savings of ~$4,837 per month

• asia-southeast1

  • On-demand pricing = ($35 per hour * 730 hours) = $25,550 per month
  • After 25% 1-year CUD discount = ~$19,162 per month
  • For a total savings of ~$6,388 per month

Once you make the commitment, you're charged that amount even if you decide tostop or scale down the actual number of vCPUs or RAM during the month.

Final recommendations

When making the decision on whether to purchase CUDs, keep inmind the following considerations:

• Regions: Purchase CUDs for regions. If you're running in multipleregions, calculate and purchase CUDs in each region separately.
• Projects: Determine the consistent baseline vCPU/RAM usage per project.Consider that production loads usually run 100% of the time, while developmentor staging environments are usually run more intermittently.
• Instances: Cloud SQL instances are usually run 24/7, so it's common tobuy CUDs for 100% consumption. If you have instances that are run only forbursts or shorter durations, exclude them from your calculations, and payon-demand rates for those instances.
• Machine types: CUDs are not tied to any machine type, but are just thetotal of vCPUs and amount of memory used in the region.

What's next

• Find CUD costs on thepricing page.
• Learn how to purchase spend-based commitments inCommitted use discounts.