Reserved Instances vs Savings Plans vs Commitments
Reserved instances vs savings plans is the first question most teams ask, but it is the wrong place to stop. Reserved instances, savings plans, and a committed spend agreement are three different levers that do different jobs, and the biggest savings come from using them together rather than choosing one. This page sets reserved instances vs savings plans side by side, then adds the committed spend layer that sits on top of both.
What reserved instances vs savings plans actually means
Reserved instances vs savings plans is a comparison of two prepaid discount mechanisms inside a single cloud account. A reserved instance commits you to a specific instance configuration in a region for a one or three year term in exchange for a lower rate. A savings plan commits you to a steady dollar per hour of compute for a one or three year term, and applies that rate flexibly across instance families and, for the broader plans, across compute services. As of June 2026 both are self service, both reward a longer term and an upfront payment with a deeper rate, and both leave you paying for the commitment whether or not you use it.
The practical difference is flexibility. A reserved instance is precise and can earn a slightly deeper rate, but it locks you to a configuration that your architecture may outgrow. A savings plan trades a little of that depth for the freedom to move workloads around without losing the discount. For most buyers running changing workloads, the flexibility of a savings plan is worth more than the last point of reserved instance rate.
| Lever | Reserved instances | Savings plans | Committed spend agreement |
|---|---|---|---|
| Commitment unit | A specific instance type in a region | A steady dollar per hour of compute | A total dollar amount over the term |
| Flexibility | Low, tied to configuration | Moderate to high across families | Highest, applies to eligible spend |
| Typical term | 1 or 3 years | 1 or 3 years | 1 to 5 years |
| How you get it | Self service | Self service | Negotiated, you usually have to ask |
| Main risk | Stranded reservations | Unused hourly commitment | Overcommitment and shortfall |
| Stacks with a commitment | Yes | Yes | Sits on top of both |
Where a committed spend agreement fits
A committed spend agreement is a different animal. It is a negotiated commitment to a total dollar amount of cloud spend over a multi year term, and in exchange you receive a discount that scales with the size of the commitment. On AWS this is the Enterprise Discount Program. On Azure it is the Microsoft Azure Consumption Commitment. On Google Cloud it shows up as committed use discounts and custom private pricing. As of June 2026 an AWS Enterprise Discount Program is typically available from around one million dollars of annual spend, with dedicated account attention usually arriving nearer five million.
The point that account teams rarely volunteer is that the committed spend discount stacks on top of reserved instances and savings plans. You do not choose between them. You run reserved instances or savings plans to optimise your steady compute, then layer a committed spend agreement over your total bill to capture an additional discount across the rest. Treating the commitment as a replacement for optimisation is how buyers overcommit.
How to combine the three without overcommitting
Start from the bottom. Cover your genuinely steady compute with savings plans or reserved instances, sized to the usage you are confident will persist even in a flat year. That layer is predictable and low risk because it tracks workloads you already run. Leave a margin so a single migration or a workload retirement does not strand the commitment.
Then size the committed spend agreement against your conservative total, not the growth case. The committed layer rewards scale, so the temptation is to commit high and bank the deeper tier. Resist it. Overcommitment creates a shortfall you pay regardless, and the deeper tier is worthless if you never reach the spend that earns it. Model the effective discount at two or three spend levels and pick the point where confidence and saving meet.
Sequence matters too. Lock your savings plan and reserved instance coverage first so you know your true discounted baseline, then negotiate the committed agreement on top of that lower number. Committing on a gross, unoptimised bill is how buyers end up paying for a commitment twice.
What to negotiate once you move past the self service levers
Reserved instances and savings plans are list mechanics with little to negotiate. The committed spend agreement is where the leverage lives. Push the ramp behind your forecast so a slow quarter does not trigger a shortfall. Negotiate Marketplace inclusion and cross account credit application, both of which are negotiable and both of which widen the spend that earns the discount.
Watch the term and the renewal. A five year commitment removes future leverage, and renewal leverage is greatest 6 to 9 months before expiry, so a shorter term or a mid term re forecast right keeps you in control. Strip or diary any auto renewal. None of this applies to a savings plan, which simply expires, but all of it applies to the committed layer that carries the real money.
The buyer view on reserved instances vs savings plans
If you only remember one thing, make it this. Reserved instances vs savings plans is a tactical choice you can make yourself, and a savings plan wins for most buyers because flexibility protects you when architecture changes. The committed spend agreement is the strategic choice, it carries the negotiation leverage and the real risk, and it deserves outside scrutiny before signature.
An independent adviser paid only by the buyer can confirm your reserved instance and savings plan coverage is right sized, then pressure test the committed agreement against your real usage so the discount you sign for is the discount you actually capture.
Sizing reserved instances, savings plans, and a committed spend agreement together? Book a confidential cloud commitment negotiation review before you sign.
Should I use reserved instances or savings plans?
For most buyers a savings plan wins because it keeps the discount when you change instance families. Reserved instances can earn a slightly deeper rate but lock you to a configuration. As of June 2026 both run on 1 or 3 year terms.
Do savings plans stack with a committed spend agreement?
Yes. A committed spend agreement such as an AWS Enterprise Discount Program stacks on top of reserved instances and savings plans, so the committed discount applies across your total eligible spend rather than replacing your optimisation.
What is the difference between a savings plan and a commitment?
A savings plan is a self service compute discount you buy in the console. A commitment is a negotiated total spend agreement over a multi year term that earns a tiered discount across your bill. The commitment carries the real negotiation leverage.
Which lever creates the most risk?
The committed spend agreement. Reserved instances strand if you change architecture, savings plans waste if you under use them, but a committed agreement creates a shortfall you pay if you commit more than you spend, as of June 2026.
How do I avoid overcommitting?
Cover steady compute with savings plans first, then size the committed agreement against a conservative flat year rather than the growth case. Model the effective discount at several spend levels before you sign.
“[PLACEHOLDER: short anonymized client quote about a quantified outcome, e.g. cut a commitment by X% before signing.]”
[ROLE, INDUSTRY, APPROX DEAL SIZE]“[PLACEHOLDER: short anonymized client quote about a quantified outcome, e.g. cut a commitment by X% before signing.]”
[ROLE, INDUSTRY, APPROX DEAL SIZE]“[PLACEHOLDER: short anonymized client quote about a quantified outcome, e.g. cut a commitment by X% before signing.]”
[ROLE, INDUSTRY, APPROX DEAL SIZE]PLACEHOLDER PROOF BLOCK · REPLACE WITH REAL ANONYMIZED CLIENT RESULTS BEFORE PUBLISHING
Condense the commitment before you sign.
A CONFIDENTIAL COMMITMENT REVIEW · INDEPENDENT · BUYER SIDE · PAID ONLY BY YOU
GET A CONFIDENTIAL REVIEW →Or download the Buy Side Guide to Cloud Commitment Structuring →The Buy Side Guide to Cloud Commitment Structuring
Sizing, ramp, term and exit, structured so the discount survives contact with reality. Free to download with a work email.