How It Works
Savings Rate divides the total discount amount captured by your commitments (Reserved Instances, Savings Plans, or Committed Use Discounts) by the total on-demand equivalent spend, then expresses the result as a percentage. A Savings Rate of 40% means you paid 40% less than you would have with no discounts active. The figure rises when commitment coverage is high and commitment utilization stays near 100%. It falls when you are paying for commitments you are not fully using, or when a large share of your workload still runs at on-demand rates.
On AWS, the discount instruments are AWS Reserved Instances and Savings Plans. On Azure, they are Reservations and Azure Savings Plans. On GCP, they are Committed Use Discounts. Each works differently, but Savings Rate is the single number that tells you how much real discount you are capturing across all of them.
Why It Matters for Cloud Cost
Savings Rate is the clearest signal of whether your cost optimization program is working. A low Savings Rate means you are leaving substantial discounts uncaptured and paying more than necessary for the same compute. A high Savings Rate that is trending downward usually means your workload has grown faster than your commitment coverage, or that commitments are expiring without being renewed. Finance teams use Savings Rate to benchmark optimization performance quarter over quarter and to set savings targets for budget forecasting. Without tracking it, you have no reliable way to know whether your cloud commitments are delivering value or quietly wasting money through underutilization.
Key Characteristics
- Savings Rate is calculated as total commitment discount divided by total on-demand equivalent spend, expressed as a percentage.
- A higher Savings Rate requires both broad commitment coverage and near-full utilization of every commitment purchased.
- Tracking Savings Rate over time reveals whether workload growth is outpacing your commitment purchasing cadence.
- Commitment underutilization directly suppresses Savings Rate, because you pay for discount capacity you do not consume.
How Usage AI Handles This
Usage AI surfaces Gross Savings Rate as a live metric in its dashboard, updated continuously as Autopilot purchases and adjusts commitments daily. ClearCost provides the underlying visibility layer so finance and engineering teams can see exactly which services and regions are driving the rate up or down.
See how Usage AI saves 30 to 50% on AWS, GCP, and Azure.
Common Questions
1. How is Savings Rate different from commitment utilization?
Commitment utilization measures how much of a specific commitment you have consumed. Savings Rate measures the total discount captured across your entire cloud spend. You can have 100% utilization on a small commitment and still have a low Savings Rate if most of your workload remains uncovered.
2. What is a good Savings Rate benchmark?
This depends on workload type, how predictable your usage is, and which services you run. Usage AI targets 30 to 50% overall savings for customers across AWS, GCP, and Azure, though individual service rates vary based on available discount programs for that service.
3. Why does the Savings Rate fluctuate month to month?
Savings Rate moves when your on-demand equivalent spend changes faster than your active commitments. Rapid infrastructure scaling, service launches, or commitment expirations can all cause the rate to drop without any change in the commitments themselves. Daily commitment adjustment, as provided by Autopilot, keeps the rate stable by rebalancing coverage as usage shifts.