What is a good effective savings rate?

There is no single target. ESR depends on how much of your usage is steady enough to commit, the term and payment option you choose (three-year and upfront commitments discount more), and how deep the provider's discount is for each service. Compare ESR with your own trend and with the rate your commitments would give at full utilization. A falling ESR with flat usage usually means commitments are expiring or going unused.

What is the difference between effective savings rate and commitment coverage?

Coverage is the share of eligible usage that a commitment discount applied to. ESR is how much cheaper that usage ended up overall. Coverage can be high while ESR is low, for example when most usage is covered by lightly discounted commitments or when commitments go unused.

Can effective savings rate be negative?

Yes. If unused commitment costs more than the discounts you used saved, you paid more than on-demand prices would have cost, and ESR drops below zero. Google Cloud's CUD analysis report shows this as negative savings.

Does ESR include Spot instances and negotiated discounts?

It depends on the definition you choose. The common definition covers commitment discounts (Reserved Instances, Savings Plans and CUDs) against on-demand prices. Some teams widen it to Spot and enterprise or private pricing to measure all rate optimization. Either works if you state it and keep it consistent.

Commitments & rates

Effective savings rate (ESR)

Effective savings rate (ESR) is net savings as a share of what all commitment-eligible usage would have cost at on-demand prices. Because it subtracts commitment you paid for but didn't use, it is the one rate-optimization number that buying too many Reserved Instances, Savings Plans or committed use discounts can't inflate.

In plain English

Think of a bulk-buy club. Rice by the sack is cheaper per kilo, but only for the rice you actually cook. If a third of the sack spoils, your real discount is smaller than the price tag promised. ESR is the discount on your whole grocery bill after you throw out what spoiled.

Formula and worked example

ESR = net savings ÷ on-demand equivalent cost

On-demand equivalent cost: = what eligible usage would have cost at on-demand prices
Actual cost: = what you paid for that usage, including commitment you didn't use
Net savings: = on-demand equivalent cost − actual cost

Worked example. Northwind Labs runs $100,000 a month of Savings Plan-eligible compute at on-demand prices. It commits $60,000 a month at rates 25% below on-demand and uses $57,000 of that commitment.
Eligible usage at on-demand prices	$100,000
Usage the Savings Plan covered, at on-demand prices	$76,000
Savings Plan commitment paid, including $3,000 unused	$60,000
Uncovered usage, paid at on-demand prices	$24,000
Actual cost	$84,000
Net savings	$16,000
Effective savings rate	16%

Coverage is 76% and utilization is 95%, and both look healthy. The $3,000 of unused commitment is what turns a 19% rate into 16%: had Northwind Labs committed exactly $57,000, it would have paid $81,000 for the same usage.

Why effective savings rate matters

Coverage and utilization each describe one side of a commitment portfolio. Coverage says how much eligible usage a commitment discount touched; utilization says how much of what you bought got used. You can push either one up by doing the wrong thing: buy more and coverage rises, buy less and utilization rises. ESR is the result both are trying to improve, measured in money.

That makes ESR the number finance and engineering can agree on. It turns "we have 76% coverage" into "we pay 16% less than on-demand for this usage", a figure you can compare across AWS, Azure and Google Cloud, across teams, and month to month.

Common mistakes

Leaving out unused commitment. Dividing only the discount you used by on-demand cost overstates ESR. Commitment you didn't use is still part of what you paid.
Changing the baseline without saying so. Some teams divide by all cloud spend, or fold in Spot and negotiated private pricing. The FinOps Foundation lists more than one formula, and the FOCUS specification measures against contracted rather than public prices. Pick one definition, write it down and keep it.
Mixing billed and amortized cost. An all-upfront purchase lands as one large charge in the month you buy it. Use amortized cost, which spreads the fee across the term, or ESR swings wildly from month to month.
Reading one month on its own. Usage dips, expiring commitments and new purchases all move ESR. Watch the trend over a quarter before acting on it.

Where to find it in AWS, Azure and Google Cloud

Where to find Effective savings rate by cloud provider
Cloud	What it is called	Where to find it
AWS	Savings Plans and Reserved Instances	Cost Explorer's Savings Plans and Reservations utilization reports show net savings, not ESR. Calculate ESR from the Cost and Usage Report (CUR 2.0): on-demand equivalent from pricing_public_on_demand_cost, actual cost from the amortized columns (savings_plan_savings_plan_effective_cost, reservation_effective_cost) plus unused commitment.
Azure	Reservations and savings plans	Cost Management's reservation and savings plan reports show utilization, not ESR. Work it out from amortized cost data: price eligible usage at pay-as-you-go rates (PayGPrice × Quantity) and compare it with Cost, which includes unused reservation and savings plan charges. Microsoft's docs say PayGPrice can be empty on reservation rows; take those prices from the Azure Retail Prices API.
Google Cloud	Committed use discounts (CUDs)	Billing → Committed use discounts → CUD analysis shows savings, coverage, utilization and an effective discount (savings ÷ cost at on-demand rates), which is ESR for the commitments in view. Savings turn negative when commitments are underused.

How CloudYali helps

CloudYali Financial Commitments shows effective savings rate next to coverage, utilization, unused commitment and net savings for AWS Reserved Instances and Savings Plans, Azure reservations and savings plans, and Google Cloud CUDs, so you can see which commitments earn their keep and which ones leak.

See the feature Read how it works in the docs

Commitments & rates
Commitment coverage
Commitment coverage is the share of commitment-eligible usage that a Reserved Instance, Savings Plan, Azure reservation or Google Cloud committed use discount paid for, measured at on-demand prices. The rest was billed at full on-demand rates, so low coverage on steady usage is money left on the table.
Commitments & rates
Commitment utilization
Commitment utilization is the share of a commitment you paid for that your usage actually consumed: used commitment ÷ total commitment. Anything below 100% is commitment you paid for and didn't use, so it shows how well a Reserved Instance, Savings Plan, Azure reservation or committed use discount fits real usage.
Commitments & rates
Savings Plan (SP)
A Savings Plan is an AWS or Azure commitment to spend a fixed amount per hour on eligible compute for one or three years. Usage up to that amount is billed at lower rates, and the discount follows your usage across instance sizes and, with the most flexible plans, instance families and regions.
Commitments & rates
Reserved Instance (RI)
A Reserved Instance (RI) is a one- or three-year commitment to a specific kind of capacity, such as an EC2 instance type in a region or an RDS database, in exchange for a lower hourly price. It's a billing discount, not a server, and you pay for every hour of the term whether the capacity runs or not.
Commitments & rates
Committed use discount (CUD)
A committed use discount (CUD) is Google Cloud's commitment discount: you commit to a set amount of resources, such as vCPUs and memory in one region, or to an hourly spend, for one or three years, and pay lower prices on that usage. The commitment is billed every month of the term, used or not.
Billing & cost types
Amortized cost
Amortized cost spreads each commitment fee across the period it covers, so a one-year Reserved Instance or Savings Plan paid up front shows up as a share of the fee every day of the term instead of one large charge on the day you buy it.

Frequently asked questions

What is a good effective savings rate?
There is no single target. ESR depends on how much of your usage is steady enough to commit, the term and payment option you choose (three-year and upfront commitments discount more), and how deep the provider's discount is for each service. Compare ESR with your own trend and with the rate your commitments would give at full utilization. A falling ESR with flat usage usually means commitments are expiring or going unused.
What is the difference between effective savings rate and commitment coverage?
Coverage is the share of eligible usage that a commitment discount applied to. ESR is how much cheaper that usage ended up overall. Coverage can be high while ESR is low, for example when most usage is covered by lightly discounted commitments or when commitments go unused.
Can effective savings rate be negative?
Yes. If unused commitment costs more than the discounts you used saved, you paid more than on-demand prices would have cost, and ESR drops below zero. Google Cloud's CUD analysis report shows this as negative savings.
Does ESR include Spot instances and negotiated discounts?
It depends on the definition you choose. The common definition covers commitment discounts (Reserved Instances, Savings Plans and CUDs) against on-demand prices. Some teams widen it to Spot and enterprise or private pricing to measure all rate optimization. Either works if you state it and keep it consistent.