48.4k Log in Get started
Metric

What is effective savings rate (ESR)?

Definition

Effective savings rate is the discount you actually achieve: realized savings divided by what the same usage would have cost at on-demand rates. It rolls coverage, utilization, and discount quality into one honest number — you can have great coverage and still a poor ESR if commitments are underused or badly scoped.

Formula: ESR = (on-demand-equivalent cost − actual cost) / on-demand-equivalent cost × 100

What data do you need?

  • Actual amortized cost per line item
  • On-demand-equivalent (public) rates for the same usage
  • Pricing model per line to attribute savings to programs
  • Unused commitment cost, which subtracts from realized savings
  • Negotiated discount data where applicable

SQL pattern

ESR by month across commitment programsPostgreSQL
SELECT
  date_trunc('month', usage_date) AS month,
  ROUND(SUM(on_demand_equivalent_usd), 2) AS on_demand_equivalent,
  ROUND(SUM(amortized_cost_usd), 2) AS actual_cost,
  ROUND(
    100.0 * (SUM(on_demand_equivalent_usd) - SUM(amortized_cost_usd))
    / NULLIF(SUM(on_demand_equivalent_usd), 0), 1
  ) AS effective_savings_rate_pct
FROM billing_line_items
WHERE is_commitment_eligible
GROUP BY 1
ORDER BY 1;

Common pitfalls

Counting potential savings from recommendations as savings.→ Recommendations are pipeline; ESR only counts realized discounts on actual usage.
Ignoring unused commitment cost.→ Subtract waste from the savings numerator — paying for unused capacity is negative savings.
Comparing ESR across teams with different workload mixes.→ ESR depends on what services a team uses; compare against each team's own history, not each other.

Where does this metric apply?

This metric commonly uses data from AWS Billing, Google Cloud Billing, Vantage, plus any warehouse models built on raw billing exports at the same grain.

Dashboards

Cloud spend overview dashboardCost allocation by team and tag dashboardCost per customer dashboardCommitment coverage dashboardCost anomaly dashboardKubernetes cost dashboard

Integrations

Cloud cost & FinOps integrationsAWS Billing + MetabaseGoogle Cloud Billing + MetabaseVantage + MetabaseKubecost + MetabaseCloudZero + Metabase

Metrics

Total cloud spendCost per customerCost growth rateCommitment coverage rateUntagged spend rateBudget burn rateCost per service

Analytics

Cloud cost analytics

FAQ

What's a good ESR?
Depends on workload mix — compute-heavy estates with mature commitment programs often reach 25–40%. The more useful signal is the trend: a falling ESR with stable coverage means utilization or scoping is slipping.
Where does the on-demand-equivalent number come from?
CUR 2.0 includes public on-demand pricing fields; otherwise join list-price tables to usage quantities. Keep the source documented — ESR is only as honest as its denominator.