Questions

How do I avoid vendor lock-in?

Short answer

Own the code, the accounts and the data, keep everything documented, and prefer common, portable tools over proprietary ones unless the proprietary one clearly earns its place. Lock-in is not always bad; the goal is to choose it on purpose and know what leaving would cost.

Last updated 2026-10-25

Lock-in to an agency

1A contract that assigns the code and IP to you.
2Repository, hosting, domains and app store accounts in your name from day one.
3Documentation, setup steps and automated deployments, so another team can run the system.
4Mainstream languages and frameworks that many engineers know.
5A handover clause: what the vendor provides if you move on.

Lock-in to a platform or cloud

Managed services save real time. Before you rely on one, check that you can export your data in a usable format, what it would take to switch, and how prices can change. Keep business logic in your own code rather than inside a vendor's workflow tool when it is core to your product.

For AI, put model calls behind your own interface and keep evals, so you can switch providers or use model routing without rewriting the product.

Frequently asked

Common follow-up questions.

Is using one cloud provider lock-in?

Some, yes. For most teams the speed is worth it. Reduce the risk with infrastructure as code, standard databases and exportable data.

What is source code escrow?

An arrangement where a copy of the code is held by a third party and released to you if the vendor cannot continue. It is mostly used for licensed software you do not own.

How do I check a vendor's lock-in risk before signing?

Ask who owns the code and accounts, how you would leave, and what they hand over. Our due diligence checklist covers the questions.

Keep reading

Planning a build? Talk it through.

OceanLab designs and builds production software. Tell us what you are planning and we will reply with how we would approach it.