Remember when moving to the cloud was supposed to save money? That was the pitch. Ditch your on-premise servers, stop paying for hardware refreshes, and enjoy flexible, pay-as-you-go pricing. It sounded great. For a lot of businesses, the reality has been quite different.

Cloud spending across Australian organisations has jumped by roughly 30% year-on-year according to Gartner’s latest forecasts, and a significant chunk of that increase isn’t planned. It’s accidental.

The Problem Isn’t the Cloud. It’s How You’re Using It.

Most cloud cost blowouts come down to three things: poor visibility, over-provisioning, and zombie resources. Let’s break those down.

Poor visibility means nobody in the organisation has a clear picture of what’s running, what it costs, and who’s responsible. This is shockingly common. A developer spins up a test environment on AWS, forgets about it, and six months later it’s costing $400 a month. Multiply that by a team of twenty and you’ve got a problem.

Over-provisioning happens when teams choose larger instance sizes or higher-tier services “just in case.” It’s the cloud equivalent of renting a warehouse when you need a storage locker. The mentality makes sense — nobody wants to be the person whose service went down because they cheaped out on compute — but it leads to massive waste.

Zombie resources are the silent killers. Unused storage volumes, orphaned snapshots, load balancers pointing to nothing, old database backups nobody will ever restore. They sit there, quietly generating charges, invisible to anyone not actively looking for them.

The Billing Dashboard Isn’t Enough

AWS, Azure, and Google Cloud all have cost management tools. They’re better than nothing. But they’re also designed by the people selling you the services, which creates an obvious conflict of interest. The dashboards show you what you’re spending, but they don’t tell you what you should be spending.

Third-party tools like Infracost or CloudHealth can help, but they’re only useful if someone’s actually reviewing the data and making decisions based on it. Most organisations set up cost alerts, ignore them for three months, then panic when the quarterly bill arrives.

What Actually Works

Here are some practical steps that make a real difference:

Assign cost ownership. Every cloud resource should have a tag that identifies who’s responsible for it and what project it belongs to. No tag, no deployment. This sounds strict because it is. It works.

Right-size monthly. Don’t set it and forget it. Review your instance utilisation every month. If a server is running at 15% CPU, it’s too big. Downsize it. Modern cloud platforms make this easy — most have recommendations built right into the console.

Set hard budgets with automatic shutdowns. This is particularly important for development and staging environments. There’s no reason your test environment needs to run 24/7. Schedule it to shut down at 6pm and start up at 8am. That alone can cut dev environment costs by 60%.

Use reserved instances and savings plans. If you know you’ll need a certain amount of compute for the next year, commit to it. The discounts are substantial — often 30-40% compared to on-demand pricing. Yes, it requires some forecasting, but even rough estimates save real money.

Run a quarterly cloud audit. Not just a cost review. A proper audit where someone goes through every active resource and asks: do we still need this? Who owns it? Is it the right size? It’s tedious work, but it pays for itself almost immediately.

The Bigger Picture

Cloud cost management isn’t a technical problem. It’s a governance problem. The technology to monitor and optimise spending exists. What’s usually missing is the organisational discipline to use it consistently.

The companies that keep their cloud bills under control aren’t the ones with the fanciest tools. They’re the ones where someone — a FinOps lead, a platform team, even just a diligent CTO — treats cloud spending with the same rigour they’d apply to any other significant business expense.

If your cloud bill has been climbing faster than your revenue, don’t blame the cloud. Look at your processes, your governance, and your team’s habits. That’s where the money’s hiding.