Direct naar content

Vendor lock-in isn’t a technical problem. It’s a math problem.

Cloud burnout #10

“We’re stuck with our cloud.” You usually hear that sentence from an IT manager who just got hit with a price increase, or suddenly has to stand up a sovereign cloud alternative and realizes there’s no budget room to move. No exit strategy, no price comparison, no leverage at the negotiating table. In this blog, Edco Wallet explains why vendor lock-in only really hurts once it shows up on the invoice and how two numbers can give you a grip on it.

Edco Wallet

Co-Founder & eigenaar
Edco Wallet - Co-Founder & eigenaar
Vendor lock-in is geen technisch probleem. Het is een rekensom. Azure Cloud optimalisatie | OptimaSure

Why lock-in only becomes visible on the invoice

Vendor lock-in feels like a technical story: proprietary services, provider-specific APIs, data formats nothing else can read. And that’s all true. But the pain is financial. As long as everything’s running, you don’t notice a thing. You keep building, you connect new workloads to the same identity layer, you put your data in a service that’s just that bit more convenient than the open alternative. The path of least resistance.

Until the moment you want to move, and discover the door is locked.

That’s when the hidden costs surface: data egress charges to get your data out of the platform, dual-running while you migrate, refactoring code written for one specific provider. And the worst part: without a real alternative, you lose your negotiating power. A vendor who knows you can’t leave has no reason to stay sharp. Discounts quietly disappear, prices quietly rise, and there’s nothing you can do to push back.

In our “12 Cloud Burnouts” whitepaper, this one sits at number 10 and it might be the most underestimated of the twelve. Though lately, it’s coming up more and more as a concern. It stays invisible for so long that nobody actively deals with it. Until the invoice does it for them.

Do the math before you’re locked in

In my view, lock-in is a sum you can calculate ahead of time. Two numbers matter.

The first is Cost-to-Switch (CTS): what would it cost you to move? Add up: egress, dual-running during the migration, refactoring and re-platforming, testing and validation, plus the change management and training costs. That’s your real exit price, not the number the sales brochure implies.

The second is Option Value (OV): the present value of the freedom to be able to switch. Price pressure on your current vendor, access to better or cheaper services elsewhere, compliance flexibility. That option has value, even if you never use it.

The decision rule is simple: only accept lock-in if the value of that option, within your investment horizon (say, 36 months), outweighs the exit cost. Make that CTS/OV comparison part of every business case for a new cloud service, and lock-in becomes a deliberate choice instead of an accident you discover later.

From insight to control

You don’t have to choose between the convenience of Azure and freedom of choice. A handful of measures structurally lower your CTS without costing you any speed.

Keep your data in open, standard formats (Parquet, CSV, JSON) so it stays readable elsewhere. Standardize on BYOK/HYOK for key management: Bring Your Own Key means you manage the keys, not the provider, so your encrypted data never gets held hostage inside one environment. Use open-source engines wherever you can: PostgreSQL and MySQL run everywhere, so an Azure Database for PostgreSQL is more portable than a service that only exists inside Azure. And define your infrastructure in Terraform instead of platform-native templates.

This is where OptimaSure and sister company OptimaData meet in the middle. With CloudXcellence, we map your current cloud environment within 24 hours, where your Azure cost hotspots are, and where lock-in is undermining your negotiating position. No dashboard without a follow-up: we link it straight to action. On the database layer, OptimaData takes over: they’re the open-source, multi-platform database specialist, and they know how to move a proprietary engine to an open landing zone in phases, with migration scripts, CDC, and restore rehearsals that prove your portability. FinOps control on the cost layer, database expertise on the data layer. Together, we cover the whole equation.

What it delivers

Clients who follow this approach save 20 to 30 percent structurally on their cloud costs. But the real return is something that never shows up on the invoice: you get your negotiating power back. You can benchmark. You can credibly threaten to leave, or bring business-critical processes back in-house and take control again. You can choose the best service instead of the only one you’ve got left.

Lock-in isn’t an unavoidable fate. It’s a series of small decisions you can steer deliberately, as long as you do the math before you sign.

Want to know where your biggest lock-in risks and quickest savings are hiding? Schedule an Azure Cost Scan, or talk through your data strategy, BYOK, and migration path with us. Insight within 30 days, structural savings after that.

This problem is part of a bigger pattern. In our “12 Cloud Burnouts” whitepaper, we describe all twelve cost pitfalls in Azure environments.

Want to talk this through and get clarity on where your lock-in sits and where you want to get out of it? We’d love to hear from you. Feel free to reach out to

Edco Wallet Co-founder, OptimaSure

This is part 10 of a 12-part series on the most costly Azure pitfalls. Every two weeks, we cover one “burnout” with practical fixes you can apply right away.

Other blogs

FinOps blog
Secret Link