Cloud costs are nobody’s problem

The gap between IT and finance

It didn’t start with a plan. It started with a pattern.

At client after client, we saw the same thing. The systems ran fine. Performance was solid, availability wasn’t an issue. But somewhere between IT and finance, a gap opened up. IT looked at resources and workloads. Finance looked at the invoice. And the two worlds didn’t line up.

That’s not a technical problem. It’s an organizational one. And it gets worse as cloud environments grow.

Teams roll out resources faster than ever. They get more autonomy. Environments grow organically. And costs grow right along with them, often without anyone understanding why. Not because people are making mistakes, but because nobody feels like they own the cost picture.

FinOps tools miss the technical layer

You hear it a lot: managed services make the DBA redundant. Automation is taking over traditional management. And yes, part of the operational work is disappearing. Provisioning, routine maintenance, standard tasks: that keeps getting automated further and further.

But at the same time, data landscapes are getting more complex. Organizations run combinations of cloud and on-premises. Different database engines run side by side. Workloads spread across environments. And choices that used to be purely technical now have direct financial impact.

It used to be that the only question was: is it running? Now organizations want to know: is it running efficiently, safely, and at the right cost?

That’s where a blind spot opens up. Most FinOps tools stop at the invoice. They can see that a database costs €4,000 a month. But they don’t know why. They can’t see which queries are eating up resources unnecessarily. They don’t know whether a workload would run better on a different platform. They’re missing the technical layer underneath the cost.

We see that layer. Ten years of database work will do that.

Why insight alone doesn’t lead to savings

A lot of organizations already have decent visibility by now. Plenty of dashboards. Plenty of reports. They know where the costs sit.

And yet, not much changes.

Because lowering costs means intervening. In architecture. In workloads. In choices that made sense once but no longer fit. That takes insight, technical depth, and the nerve to actually change something. And that’s exactly where it gets stuck.

A standalone tool doesn’t fix that. Neither does standalone consultancy. What’s needed is someone who understands the technology and can translate that into cost, and who then actually turns off the tap. This problem shows up in a lot of different shapes. In the “12 Cloud Burnouts” whitepaper, we describe the twelve most common cost pitfalls in Azure environments.

Cost optimization as part of database management

If you take this shift seriously, you can’t keep doing as a database provider what you’ve always done. The market for classic management is under pressure. It’s still needed, but it sets you apart less than it used to. Managed services take over part of it, and clients are less willing to pay a premium for it.

At the same time, demand is growing for something else. For providers who understand systems and can steer on cost, risk, and performance at the same time. Who aren’t tied to a single platform, but can weigh choices across multiple environments.

OptimaSure is the direct result of that shift. Co-founder Henk van der Valk previously optimized Azure environments as a Microsoft Global Black Belt at organizations like Ajax and Microsoft. He built CloudXcellence: the tooling that combines insight with action. OptimaData brings the database and infrastructure knowledge, the ability to understand what’s actually happening technically. OptimaSure adds continuous cost steering and optimization on top, with CloudXcellence as the tooling and hands-on consultancy as the execution.

Together, they form something that’s genuinely rare in practice: a model where analysis and execution are directly connected. We don’t write reports. We turn off taps.

Database FinOps: understanding cost at the workload level

Cloud costs aren’t an abstract number. They’re the result of concrete choices. How generously is a database sized? How is storage being used? Which queries run when, and how often? How does a workload scale under load?

Without insight into that behavior, optimization stays superficial. Traditional FinOps stops at visibility. Database expertise goes one layer deeper.

Combine the two, and you get database FinOps: knowing where the costs sit, understanding why they’re there, and bringing them down structurally. It’s the logical next step for any organization that’s serious about getting a grip on cloud costs.

Want to know where your Azure costs are really coming from? Get in touch for a no-obligation conversation, or see what OptimaSure can do for you at optimasure.nl.