Cloud Savings Plan Coverage Calculator
Estimate monthly savings plan coverage, unused commitment exposure, and the effective blended discount applied to eligible compute spend.
For FinOps forecasting; reconcile with provider billing exports before taking action.
Examples
- Eligible spend $125,000, $120/hr commitment, 730 hours, 28% discount ⇒ 70.08% coverage, $87,600 covered, $37,400 uncovered, $0 unused commitment
- Eligible spend $80,000, $60/hr commitment, default hours, no discount ⇒ 54.75% coverage, $43,800 covered, $36,200 uncovered, $0 unused commitment
FAQ
What counts as eligible compute spend?
Include EC2, Fargate, or Azure compute usage priced per hour that the savings plan applies to. Exclude storage, data transfer, and services without savings plan coverage.
How should I set the blended discount percentage?
Use the weighted average of your savings plan discount rates. For example, mix 1-year no-upfront and 3-year partial-upfront commitments according to how much spend each protects.
Why do I see unused commitment?
Unused commitment arises when the savings plan commitment exceeds actual eligible usage. Investigate seasonality or right-size by exchanging the plan if your provider supports it.
Can I run this for partial months?
Yes. Override the hours in the billing period with the exact number of hours covered by your report, such as 336 hours for a 14-day sprint review.
Additional Information
- Coverage ratio equals committed spend divided by eligible spend, capped at 100%.
- Unused commitment appears when the hourly commitment exceeds eligible spend during the billing window.
- Discount percentage reflects the weighted savings plan benefit relative to total eligible spend.