Cloud vendors sell flexibility as a feature. They are right to — it is genuinely valuable. But flexibility is a product, and like every product, it has a price. The price is 40 to 72 per cent more than committed pricing, depending on the service. Most organisations pay it indefinitely, for resources they have no intention of ever removing.
You Are Paying for Optionality You Are Not Using
Pay-as-you-go pricing is priced to include the cost of unused capacity the cloud vendor must reserve for you. If your production database server has been running unchanged for 18 months and will be running unchanged in 18 months’ time, you are paying a significant premium for optionality you are not exercising.
This is not a mistake — it is a choice. But it should be a deliberate one, not a default.
The Three Types of Flexibility — And Which One You Actually Need
- Real-time flexibility: The ability to scale up and down in response to demand. You need this. Autoscaling handles it. Reservations do not prevent it.
- Strategic flexibility: The ability to migrate workloads or change architecture. One-year commitments accommodate this well.
- Psychological flexibility: The comfort of feeling like nothing is locked in. You are paying for this more than you realise.
A Simpler Framework
- If a workload has been running for >6 months with no change planned: It is a reservation candidate.
- If a workload is in active development: Leave it on pay-as-you-go.
- If a workload is genuinely experimental: Pay-as-you-go is the right answer.
The Dan Rebuttal: When leadership pushes back with “What if we want to change our tech stack in 18 months?”, I point out the reality of inertia. The likelihood of a company suddenly switching languages or stacks is incredibly low. The sheer cost of redevelopment—the time, the testing, and the retraining—far outweighs the “safety” of a flexible cloud bill. If the business is committed to the code, they should be committed to the compute.
Flexibility is worth paying for when you use it. The goal is to identify the workloads where you are paying for flexibility you will never exercise, and make a deliberate decision — not to assume pay-as-you-go is the safe default.
Identifying which workloads are reservation candidates and which genuinely need flexibility is an architectural assessment. Get in touch if you want an independent view.
