2026-10-07 · Operations & infrastructure
Why the cloud bill grows while nothing happens
Bills rarely grow through one big decision. They grow through many small ones that nobody takes back — here are the usual places.
Put several months of a cloud bill side by side and the picture is almost always the same: it rises in small steps, and when you ask what changed, nobody answers “we built something new”.
Nothing is ever switched off
Last year's test environment. The server for a migration that finished. The database snapshot kept “just in case”. Each item is too small to notice, and together they are often the largest block on the invoice.
The countermeasure is unspectacular: a list of every running resource, once a quarter, and for each one the question of who needs it right now. Where there is no answer, switch it off — tearing down is cheaper than paying on.
You pay for provisioning, not for use
Reserved compute, load balancers, fixed IP addresses, snapshots, traffic between zones — all of it runs whether anybody uses the system or not. A service that serves nobody at night and on weekends costs the same as on a Tuesday morning.
This is not an argument against the cloud but one for honest arithmetic: steady, modest workloads are often far cheaper on fixed machines. Workloads with real peaks pay for flexibility and rightly so.
Storage grows quietly
Logs without an expiry date, backups without a retention limit, uploads without cleanup. Storage is cheap per gigabyte and therefore the classic blind spot — until it suddenly shows up in the annual figure.
Two numbers help: how long data really has to be kept, and what that period costs. Usually the technical retention turns out to be far longer than the one the business actually needs.
How I did it myself
My own landscape had grown across several providers over the years. Cleaning it up was not one big migration but a list: every service, its purpose, its price, the last time anyone used it. A considerable part had no purpose any more and was switched off; the rest moved onto my own hardware.
The real insight was not technical: without the list, nobody knew what was being paid for. Writing it takes a day and is the cheapest measure available in this area.