Cloud commitment discounts are lower prices that cloud providers offer in exchange for committing to a level of usage for a set term, usually one or three years. Instead of paying on-demand rates by the hour or second, the buyer commits to a specific amount of compute, database or other capacity, or to a level of hourly spend, and pays a reduced rate for it. Each large provider has its own versions, such as AWS Reserved Instances and Savings Plans, Azure Reservations and savings plans, and Google Cloud committed use discounts, with different rules for flexibility, payment and scope.
At a glance
- You commit to a level of usage or hourly spend for a term; the provider charges a lower rate.
- Longer terms and paying more upfront typically earn bigger discounts.
- Commitments are billed whether or not you use them, so they suit steady baseline usage.
- Flexibility varies: some apply across instance types and regions, others to one specific configuration.
- Rightsize before committing, so you do not lock in waste.
What problem it solves
Many workloads run around the clock: production databases, core applications, always-on virtual machines (VMs). Paying on-demand rates for them means paying for flexibility you do not use. Commitment discounts let buyers trade that unused flexibility for a lower price, often without any change to the architecture.
For finance, they are one of the most direct levers on a cloud bill. For engineering, they are a way to lower cost without re-platforming. The trade-off is risk: if usage drops or changes shape, the commitment keeps billing.
How it works
Types of commitment. Broadly, providers offer two styles:
- Resource commitments: a commitment to a specific type of capacity, such as an instance family in a region. These often carry the deepest discounts but less flexibility.
- Spend commitments: a commitment to a level of hourly or monthly spend on eligible services, applied automatically to whatever qualifying usage you run. These tend to be more flexible, sometimes with a smaller discount.
Term and payment. Terms of one or three years are common. Payment may be all upfront, partly upfront or monthly, with larger discounts for paying earlier.
Application. The provider applies the discounted rate to matching usage each hour. Usage above the commitment is billed at normal rates. Commitment not used in a given hour is generally lost for that hour.
Flexibility. Depending on the provider and product, commitments may be exchangeable, convertible, shareable across accounts in an organization, or in some cases resellable or cancellable with conditions. These rules differ widely and change over time.
Managing them. Teams track coverage (how much eligible usage is covered) and utilization (how much of the commitment is used). A FinOps practice usually owns purchasing decisions and reviews them regularly.
Our public cloud solution page covers how commitments fit alongside provider selection and contract negotiation.
When it matters for buyers
- Steady workloads on on-demand pricing. Long-running infrastructure as a service (IaaS) usage is the usual starting point.
- After a migration settles. Wait until usage stabilizes and has been rightsized, then commit.
- Commitments are expiring. Renewal is a chance to re-fit commitments to current usage.
- Before a major change. A planned re-architecture, consolidation or exit should shape how much and how long you commit.
- Alongside a larger agreement. These discounts often interact with a cloud commitment agreement.
Questions to ask vendors
- What commitment options exist for our services, and how do their discounts compare?
- Which options can be exchanged, converted, shared across accounts or ended early, and on what terms?
- How do the payment options (upfront, partial, monthly) change the rate?
- How is coverage and utilization reported, and can we get alerts when commitments go unused?
- Does spend on these commitments count toward our committed spend agreement?
- If a third party manages commitments for us, who carries the risk if usage drops, and how are they paid?
How it differs from a cloud commitment agreement
Cloud commitment discounts are resource- or usage-level: you commit to a particular kind of capacity or hourly spend and get a lower rate on it. A cloud commitment agreement is a contract-level promise to spend a total amount with the provider across its services over a term. The two often coexist; whether purchases or usage under commitment discounts count toward the agreement, and how the two sets of pricing interact, depends on the agreement’s terms. Both resemble a minimum annual commitment: you are paying for predictability with flexibility.