All insights

Reserved instances vs savings plans: when to commit

How cloud commitment discounts work, how they differ, and how to commit without locking yourself in.

Commitment discounts are often the single biggest lever in a cloud bill. You promise the provider a certain level of usage for one or three years, and in return you pay significantly less than on-demand prices.

The catch: commit too much and you pay for capacity you don’t use. Commit too little and you leave money on the table. Here’s how to get it right.

The two main families

Every major cloud offers commitment discounts, with different names and slightly different rules.

Reserved instances and reservations commit you to a specific type of resource, for example a certain instance family in a certain region. AWS calls them Reserved Instances. Azure calls them Reservations. They usually offer the deepest discounts, in exchange for less flexibility.

Savings plans commit you to a level of spend per hour, rather than a specific resource. AWS offers Compute Savings Plans and EC2 Instance Savings Plans. Azure offers a savings plan for compute. They’re more flexible: if you change instance types, or in some cases regions or services, the discount follows your usage.

Google Cloud uses committed use discounts, which come in both resource-based and spend-based forms, so the same trade-off applies.

The trade-off in one sentence

The more specific your commitment, the bigger the discount, and the bigger the risk if your usage changes.

Reservations Savings plans
Discount level Usually highest Slightly lower
Flexibility Low: tied to a resource type High: follows your spend
Best for Stable, predictable workloads Workloads that change over time

How to decide what to commit

  1. Look at your baseline, not your average. Commit only to the level of usage you run consistently, even in quiet periods. Peaks stay on-demand.
  2. Start with flexible commitments. If your architecture is still evolving, savings plans protect you from paying for resources you’ve moved away from.
  3. Prefer one-year terms while you’re growing or changing. Three-year terms save more, but only if you’re confident the usage will still be there.
  4. Commit in layers. Instead of one big purchase, commit gradually every month or quarter. Your coverage grows with your confidence, and commitments expire at different times.
  5. Watch utilisation monthly. A commitment you don’t use is just a prepaid bill. Track how much of each commitment is actually used.

Common mistakes

  • Buying before cleaning up. Rightsize and remove idle resources first. Otherwise you lock in a discount on waste.
  • Forgetting renewals. When a commitment expires, prices jump back to on-demand overnight. Keep a calendar of expiry dates.
  • Committing in silos. Teams buying their own commitments often over-commit in total. Commitments work best when managed centrally.

Where to start

If you’re not sure what your current coverage and utilisation look like, that’s the first thing to measure. It’s a standard part of a FinOps assessment, and it often reveals savings that need no engineering work at all.

Free · 30 minutes · Online

Book your free demo

Tell us a little about your setup. We'll come back within one business day with a time that suits you.

  • 30 minutes, online, completely free
  • A first look at your cost picture
  • No commitment, no sales pitch

Which clouds, platforms or tools do you use?

What would you like to achieve?

We only use your details to reply to you. See our privacy policy.