Reserved Instance vs On Demand Price Gaps
PUBLISHED JUNE 16, 2026 · REVIEWED JUNE 16, 2026
Reserved instance vs on demand price gaps are the first discount most buyers see, and the most misread. The spread between an on demand rate and a one or three year reservation looks large, which makes a reservation feel like an obvious win. It often is. But the size of the gap also gets used to justify deeper commitments than the workload supports, and it sits underneath a negotiated agreement that can change the real economics. This page sizes the gap honestly and shows how to benchmark it, with mechanics current as of June 2026.
Reservations are one layer in a stack. To see the others, read how cloud list prices hide the real price, and use the cloud spend benchmarking guide to place the whole picture in context.
How wide are reserved instance vs on demand price gaps
The headline spread
Reservations and savings plans trade flexibility for a lower rate on covered usage. The spread widens with term length and with paying more upfront, so a three year all upfront commitment shows the largest gap against on demand and a one year no upfront commitment the smallest. The exact figures are published by each provider and move over time, so anchor any analysis to a dated rate card pull rather than to a remembered number (source: provider pricing pages, as of June 2026).
Why the gap flatters the reservation
The on demand rate is the most expensive way to run a steady workload, so comparing against it makes any reservation look strong. The honest comparison is not reservation versus on demand. It is reservation versus the blended rate you would otherwise pay, including the commitment discount layered on top. Measured that way, the real gain from a reservation is usually smaller than the headline spread suggests.
Where the gap misleads buyers
The danger is using a wide on demand to reserved spread to justify covering usage you are not sure you will run. A reservation only pays back if the underlying usage persists for the term. Cover volatile or declining usage and the unused portion becomes waste, because the saving assumed steady consumption that did not arrive. The gap is real, but it is only earned on usage that actually runs.
On GCP the picture has an extra wrinkle. Committed use discounts and sustained use discounts do not double stack on the same resource as of June 2026 (source: Google Cloud documentation), so a buyer comparing a committed rate to on demand can overstate the gain by ignoring the sustained use discount that applied anyway. Benchmark the right baseline, not the most flattering one.
How to benchmark the reserved vs on demand gap
Compute the spread against your blended effective rate, not against on demand, and only on usage with a credible chance of running the full term. Then place your reservation coverage and rate against peer ranges, which is the method in how to benchmark a cloud commitment offer and the deal size ranges in cloud discount benchmarks by commitment size. An EDP, MACC, or committed use agreement stacks on top of these instruments, so the reservation gap should be assessed as part of the full deal, not in isolation.
A commitment benchmarking service sizes your reserved to on demand spread against comparable buyers and flags where reservation coverage is being used to justify overcommitment, before the gap costs you money rather than saving it.