Own your AI: how to avoid vendor lock-in

← Back to all articles

Lock-in rarely announces itself. No one sends an email saying "you now depend entirely on us." It builds up quietly, one reasonable-sounding decision at a time — until switching away would cost more than starting over.

AI makes this easier to fall into than usual, because so much of the value lives in places you can't see: the data you fed in, the model that learned from it, and the glue that connects everything. Lose access to those and a slick tool becomes a hostage situation.

You don't need to be technical to avoid it. You just need to ask a few blunt questions before you sign anything.

The questions worth asking

1. Who owns the data — and can I get it out?

Your data is the part that's genuinely yours. Make sure you can export it in a standard format (CSV, JSON, plain files) at any time, without paying a fee or filing a request. If "export" isn't a one-click thing, that's a flag.

2. Who owns the model and the code?

If someone trains a model on your data, who owns the result? If a tool is custom-built for you, do you get the source code, or just a login? "You own everything we build for you" should be in writing, not implied.

3. Can it run somewhere other than their servers?

You don't always need on-premise hosting, but you should know whether it's possible. A tool that only ever runs inside one vendor's cloud is a tool you can never move.

4. What happens if they disappear?

Vendors get acquired, pivot, or shut down. Ask the uncomfortable question early: if this company vanished tomorrow, could you keep running? If the honest answer is no, price that risk in.

Good vendors don't mind these questions. The ones who get defensive are telling you something.

Lock-in isn't always wrong

Some dependence is fine. You probably don't want to self-host your email or rebuild a payment processor. The point isn't to avoid every external tool — it's to choose your dependencies deliberately, and to keep the parts that are genuinely yours (your data, your trained models, your core workflows) under your own control.

The test I use is simple: if I had to leave this vendor, how bad would the morning be? If the answer is "annoying," that's healthy. If the answer is "we'd have to rebuild from scratch and we can't even get our data," something went wrong earlier.

How we do it

Everything we build is yours: the code, the models, the documentation. No recurring fees for things you don't need, no proprietary format holding your data hostage, and no part of the system that only we can touch. You should be able to take what we build and walk away with it. The fact that clients rarely want to is the point — but they always could.