[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-25。"],[[["\u003cp\u003eAlloyDB Committed Use Discounts (CUDs) offer significant savings (25% for one-year and 52% for three-year terms) in exchange for a commitment to consistent usage of database instances.\u003c/p\u003e\n"],["\u003cp\u003eCUDs apply to all AlloyDB database instance vCPU and memory usage across all regions and projects but do not include storage, backups, or network data transfer costs.\u003c/p\u003e\n"],["\u003cp\u003eThe commitment is based on an hourly on-demand cost and is billed monthly, with any usage exceeding the committed amount charged at the on-demand rate.\u003c/p\u003e\n"],["\u003cp\u003ePurchasing a CUD is non-cancelable, so it's important to calculate your expected minimum hourly expenditure on AlloyDB capacity over the one- or three-year term.\u003c/p\u003e\n"],["\u003cp\u003eWhen purchasing a CUD consider the regions, projects and instances you are using to calculate the expenditure across them for the appropriate commitment amount.\u003c/p\u003e\n"]]],[],null,["# Committed use discounts\n\nThis page describes how committed use discounts (CUDs) work with AlloyDB for PostgreSQL.\n\nOverview of committed use discounts\n-----------------------------------\n\n*Committed use discounts (CUDs)* for AlloyDB provide discounted\nprices in exchange for your commitment to continuously use database instances for a one-year or three-year term.\n\nAlloyDB CUDs are ideal for workloads with predictable\nresource needs. You commit to a consistent amount of usage, measured in cost per\nhour of equivalent on-demand spending, for a one-year or three-year term. In\nexchange, you receive a discounted rate for AlloyDB on the\napplicable usage your commitment covers.\n| **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 after **July 15, 2025** . Customers can opt in now to get the new CUD experience. For more information, see [Spend-based CUDs program improvements](/docs/cuds-multiprice).\n\nYou can purchase CUDs from any Cloud Billing\naccount, and the discount applies to any eligible usage in projects that the\nCloud Billing account pays for. When you purchase an AlloyDB\nCUD, you pay the same commitment fee for the entirety of the\ncommitment term, even if the price of applicable usage changes. You still\nreceive the same discount percentage on applicable usage in the event of a price\nchange. The commitment fee is billed monthly.\n| **IMPORTANT:**Any overage in usage is charged at the on-demand rate.\n\nFor more information about your bill, see [Analyze the effectiveness of your spend-based committed use discounts](/billing/docs/how-to/cud-analysis-spend-based).\n\nUsage that qualifies for AlloyDB CUDs\n-------------------------------------\n\nCUDs automatically apply to aggregate AlloyDB instance\nusage across all regions and all projects, giving you low, predictable costs,\nwithout the need to make any manual changes or updates yourself. This\nflexibility helps you achieve high utilization rates across your commitments,\nsaving you time and money.\n\nAlloyDB CUDs apply to all AlloyDB database\ninstance vCPUs and memory usage. AlloyDB CUDs **do not apply** to\nstorage, backups, and network data transfer.\n\nFor a list of applicable SKUs, see [AlloyDB CUD Eligible SKUs](/skus/sku-groups/alloydb-for-postgresql-cud-eligible-skus).\n\nPricing\n-------\n\n- **25% discount**: You get this by committing to a 1-year term. For the duration of your term, you pay the AlloyDB CUD 1-year price (consumption model ID C100-AA7B-33B1) as your committed hourly spend amount.\n- **52% discount**: You get this by committing to a 3-year term. For the duration of your term, you pay the AlloyDB CUD 3-year price (consumption model ID 4920-CA74-2184) as your committed hourly spend amount.\n\nPurchase AlloyDB CUDs\n---------------------\n\nTo purchase or manage CUDs for a Cloud Billing account, follow the\ninstructions at [Purchasing spend-based\ncommitments](https://cloud.google.com/docs/cuds-spend-based#purchasing).\n\nBefore you purchase a CUD, read the [Service Specific Terms](/terms/service-terms)\nregarding committed units.\n\nTo learn more, including how to purchase spend-based commitments, see\n[Committed use discounts](/docs/cuds-spend-based).\n\nExample use case\n----------------\n\nThis example shows you how to calculate your discount and costs for an\n[high-availability (HA)](/alloydb/docs/overview#ha) instance.\n\nKey points to remember:\n\n- AlloyDB CUDs apply only to vCPUs and memory.\n- AlloyDB CUDs **do not apply** to storage, backups, or network data transfer.\n- AlloyDB CUDs apply to all instances.\n- AlloyDB CUDs are measured in **dollars per hourly on-demand commitment**.\n\n### Calculate savings for one and three-year commitments\n\nYou should set your commitment to be your expected minimum hourly expenditure based on the consumption model price, across your projects over the next one or three years.\n\nAs an example, consider an AlloyDB HA primary instance,\nwhich has a leader and a standby node in the `us-central1` region. This\ninstance has 16 vCPUs and 128 GB RAM.\n\nFrom the [pricing page](/alloydb/pricing), you can calculate the\napproximate on-demand cost (no commitment) as follows:\n\n- Combined expenditure in `us-central1` for the leader and standby nodes: 2 \\* ((16 vCPU \\* $0.06608 per vCPU per hour) + (128 GB \\* $0.0112 per GB per hour)) = $4.98 per hour\n- Monthly cost based on on-demand pricing: $4.98 per hour \\* 730 hours = $3,635.40 per month ($43,624.80 per year)\n\nHowever, you receive a discount for a 1-Year commitment. Using the [pricing page](/alloydb/pricing), calculate your discounted 1-Year commitment cost:\n\n- Combined expenditure in `us-central1` for the leader and standby nodes: 2 \\* ((16 vCPU \\* $0.04956 per vCPU per hour) + (128 GB \\* $0.0084 per GB per hour)) = $3.73632 per hour\n- Monthly cost based on on-demand pricing: $3.73632 per hour \\* 730 hours = $2,727.5136 per month\n\nYour 1-Year commitment savings is **$10,894.637** per year.\n\nIf you expect to spend that minimum amount per hour continuously for\nthe next year or more, enter \"`$3.73632`\" as your discounted hourly commitment amount. You can make a commitment for a lower amount, but any expenditure beyond that limit is charged at the on-demand rate.\n| In the legacy CUDs program, your committment amount is the on-demand price instead. For more information about the differences between the legacy and new spend-based CUDs program, see [Spend-based CUDs program improvements](/docs/cuds-multiprice).\n\nSimilarly, you receive a greater discount for a 3-Year commitment. Using the [pricing page](/alloydb/pricing), calculate your discounted 3-Year commitment cost:\n\n- Combined expenditure in `us-central1` for the leader and standby nodes: 2 \\* ((16 vCPU \\* $0.0317184 per vCPU per hour) + (128 GB \\* $0.005376 per GB per hour)) = $2.3912448 per hour\n- Monthly cost based on on-demand pricing: $4.98 per hour \\* 730 hours = $1745.6087 per month\n\nYour 3-Year commitment savings is **$68,032.488** over three years.\n\nAs you can see, a commitment that covers your expected minimum\nAlloyDB usage over the years can lead to significant\nsavings. Read on for our recommendations on choosing the right CUD size\nfor your AlloyDB projects.\n\nRecommendations for choosing a commitment\n-----------------------------------------\n\nWhen making the decision on whether to purchase CUDs, consider the following:\n\n- Regions: AlloyDB CUDs apply across regions. If you have AlloyDB instances in multiple regions, calculate the expenditure across all the regions while making a commitment.\n- Projects: Determine the consistent baseline vCPU/RAM usage per project. Consider that production loads usually run 100% of the time, while development or staging environments are usually run more intermittently.\n- Instances: AlloyDB instances are usually run 24/7, so it's common to buy CUDs for 100% consumption. If you have instances that are run only for bursts or shorter durations, exclude them from your calculations, and pay on-demand rates for those instances.\n\nWhat's next\n-----------\n\nLearn how to purchase spend-based commitments in [Committed use discounts](/docs/cuds-spend-based)."]]
