Commitment break-even calculator

Is a cloud commitment worth it?

Reserved Instances, Savings Plans, and Committed Use Discounts lock you in for 1 or 3 years. Enter your spend and see the utilization you need to actually come out ahead, across AWS, Azure, and GCP.

$
%
Pre-filled with a typical rate. Paste your provider-quoted rate for an exact answer.
100%
A commitment is paid whether you use it or not. This is the honest variable.
Enter your on-demand spend
to see your break-even point and savings.
Stop guessing your utilization. nable reads your real bill and tells you which commitments you'd actually use, by account and service. Free, runs locally.
Get nable free

How the break-even works

A Reserved Instance (AWS), Reserved VM Instance (Azure), or Committed Use Discount (GCP) trades a 1 or 3 year commitment for a lower rate. The catch: you pay for the commitment whether you use it or not. So the real question is not "how big is the discount," it's "will I use it enough to beat paying on-demand for only the hours I actually run."

The break-even utilization is simply 1 − discount. A 40% discount breaks even at 60% utilization: if you expect to use the resource more than 60% of the term, committing wins. Less than that, on-demand is cheaper. This calculator drives its Buy / Marginal / Don't-buy verdict off your expected utilization versus that break-even, not off the size of the discount.

AWS Reserved Instances and Savings Plans

AWS commitments come in no-upfront, partial-upfront, and all-upfront. More upfront means a bigger discount. Savings Plans commit to a dollars-per-hour spend rather than a specific instance, so over-committing (paying for more than you use) is the common way teams lose money here.

Azure Reserved VM Instances and Savings Plans

Azure commitments cost the same whether you pay upfront or monthly, so the payment choice is about cash flow, not price. Reserved Instances lock to a VM family; Savings Plans apply to compute spend more broadly.

GCP Committed Use Discounts

GCP CUDs are billed monthly with no upfront. Resource-based CUDs commit to vCPU and memory in a region; flexible (spend-based) CUDs commit to a dollar amount and apply across families at a lower rate. CUDs auto-apply to matching usage.