Skip to content
Calcrivo

Savings Plan Calculator

Size an AWS Savings Plan hourly commitment, then see covered spend, on-demand overflow, waste and net monthly saving.

Inputs

USD/hour
USD/hour

What the same usage would cost at on-demand list prices.

%

Editable — Compute Savings Plans commonly land near 27% and EC2 Instance Savings Plans higher. Confirm your own rates.

hours

Monthly Cost With the Plan

$4,490.00

Committed Spend (billed regardless)

$3,650.00

Usage Billed at On-Demand

$840.00

Monthly Saving vs All On-Demand

$1,350.00

Commitment Utilisation

100.0%

Flexibility Trade-off

Portable across regions, families, Fargate and Lambda at a smaller discount

Step by step

  1. Values used

    Hourly commitment = 5 USD/hour; On-demand equivalent spend per hour = 8 USD/hour; Savings Plan discount vs on-demand = 27 %; Hours in the billing month = 730 hours; Plan type = Compute Savings Plan — any region, family, Fargate and Lambda

  2. Savings Plan

    discounted need = on-demand spend × (1 − discount); covered = min(commitment, discounted need); overflow at on-demand = (discounted need − covered) ÷ (1 − discount).

  3. Monthly Cost With the Plan

    = 4,490.00

  4. Committed Spend (billed regardless)

    = 3,650.00

  5. Usage Billed at On-Demand

    = 840.00

  6. Monthly Saving vs All On-Demand

    = 1,350.00

  7. Commitment Utilisation

    = 100.0

  8. Flexibility Trade-off

    = Portable across regions, families, Fargate and Lambda at a smaller discount

How it works

A Savings Plan applies discounted rates to usage until your hourly dollar commitment is exhausted, and everything above it falls back to on-demand. Because usage is consumed at the discounted rate, an hourly commitment buys roughly commitment ÷ (1 − discount) worth of on-demand-equivalent usage — and any commitment you do not consume in an hour is simply lost, which is why utilisation matters as much as coverage. Commitments are billed hour by hour and unused dollars never roll over, so over-committing turns a discount into a surcharge; sizing to your steady-state trough is the standard safe play.

Formula

Savings Plan

discounted need = on-demand spend × (1 − discount); covered = min(commitment, discounted need); overflow at on-demand = (discounted need − covered) ÷ (1 − discount).

commitment
Dollars per hour you promise to spend for 1 or 3 years
discount
Savings Plan rate reduction against on-demand list price
discounted need
Your usage repriced at Savings Plan rates

Frequently Asked Questions

How is Savings Plan calculated?

discounted need = on-demand spend × (1 − discount); covered = min(commitment, discounted need); overflow at on-demand = (discounted need − covered) ÷ (1 − discount). A Savings Plan applies discounted rates to usage until your hourly dollar commitment is exhausted, and everything above it falls back to on-demand. Because usage is consumed at the discounted rate, an hourly commitment buys roughly commitment ÷ (1 − discount) worth of on-demand-equivalent usage — and any commitment you do not consume in an hour is simply lost, which is why utilisation matters as much as coverage.

Why does Savings Plan matter?

Commitments are billed hour by hour and unused dollars never roll over, so over-committing turns a discount into a surcharge; sizing to your steady-state trough is the standard safe play.

What values do I need to enter?

This calculator takes 5 inputs: Hourly commitment, On-demand equivalent spend per hour, Savings Plan discount vs on-demand, Hours in the billing month, Plan type. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Should I aim for 100% coverage?

No. Coverage and utilisation pull against each other: commit to your trough of steady usage and let spiky or short-lived capacity run on-demand or on Spot. Most FinOps teams target high utilisation (near 100%) and accept coverage somewhere in the 70–85% range.

You might also need