# Reserved and Spot Instances

> Four ways to pay less for the same cloud server: rightsizing, reserved instances, savings plans and spot. What each one asks of you in return.

**Course:** [Virtualization and Cloud Computing](https://learn.benibix.com/learn/infrastructure-virtualization)  
**Time:** 12 min

**After this lesson you can:**

- Rightsize a server that is too big
- Compare reserved instances, savings plans and spot
- Pick the right price for a job

## Four ways to pay less for the same server

There are four main ways to cut a cloud bill. Rightsizing shrinks servers that are too big. A reserved instance or a savings plan trades a one or three year promise for a lower price, up to 72% off. A spot instance rents spare capacity for up to 90% off, but can be taken back.

Each one trades something for the discount. Rightsizing costs some care. A reservation costs a promise. Spot costs the right to keep your server.

Rightsizing comes first, because it is free. Many cloud servers use a small share of what they pay for. A server with 16 vCPUs that never uses more than 2 can drop to a 4 vCPU type and cost about a quarter as much.

A reserved instance is a promise to use one server type, in one region, for one or three years. A savings plan is a promise to spend a set amount each hour instead, on any type you like. Both suit servers that run all day, every day.

A spot instance is a spare server the cloud sells cheap. When the cloud needs it back, it gives a warning, often just two minutes, then takes it. That suits work that can stop and start, like batch jobs or test runs.

The full price, with no promise, is called on-demand. It is the right price for new work you cannot predict yet, and for short tests. Most teams mix all four: a reserved base, on-demand for growth and spot for batch work.

The mistake is to reserve before rightsizing. A three year promise on a server twice the size you need locks in the waste for three years. Shrink first, then reserve what is left.

## The ways to pay for one server

| Price | Discount | You promise | The catch |
| --- | --- | --- | --- |
| On-demand | None | Nothing | The top price |
| Savings plan | Up to 72% | An amount each hour, 1 or 3 years | You pay even if you use less |
| Reserved instance | Up to 72% | One server type, 1 or 3 years | Stuck with that type |
| Spot instance | Up to 90% | Nothing | Can be taken back at short notice |

## Which one to pick

1. **Rightsize.** Always, first. Shrink any server that never uses most of what it has.
2. **Reserve or plan.** For servers that run all day, every day, and will for a year or more.
3. **Spot.** For work that can stop and start again, like batch jobs and test runs.
4. **On-demand.** For new or short work you cannot predict yet.

![Four columns for four ways to pay for the same cloud server: on-demand, savings plan, reserved instance and spot. A price bar in each: on-demand is full height, savings plan and reserved are each up to 72% lower, and spot is up to 90% lower. Under each bar is what you promise and the catch.](https://learn.benibix.com/diagrams/inf-cloud-pricing.svg)

### Example: A data team cuts its bill in half

A data team spends 20,000 euros a month on cloud servers, all on-demand. Their main servers average 15% busy.

They rightsize first, then reserve the steady base for one year and move nightly reports to spot. The bill falls to about 9,000 euros a month.

**Words in this lesson:** [Rightsizing](https://learn.benibix.com/term/infrastructure/rightsizing), [Reserved Instance](https://learn.benibix.com/term/infrastructure/reserved-instance), [Savings Plan](https://learn.benibix.com/term/infrastructure/savings-plan), [Spot Instance](https://learn.benibix.com/term/infrastructure/spot-instance)

> **The one difference.** Reserved and savings plans trade a long promise for a lower price. Spot needs no promise, but the cloud can take the server back.

**Question:** Which job suits a spot instance best?

**Answer:** A nightly batch job that can restart if stopped. A spot server can be taken back with a short warning. Work that can stop and pick up again loses little, while a database or checkout would go down.

---

Source: https://learn.benibix.com/learn/infrastructure-virtualization/reserved-and-spot-instances
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
