vendor lock-in

Vendor lock-in occurs when dependence on one supplier makes switching require substantial time, money or technical changes. The term often applies to software and cloud platforms, but can also concern hardware, licences or other services.

What causes vendor lock-in?

The dependency can be technical. Examples include data in a closed file format, integrations with a proprietary APIGlossary · In briefAPIAn API is a defined way for software to exchange data or call functions in other software without needing to know how that software works internally.Read more or software that works only in one cloud environment. Migration then requires converting data, rebuilding integrations or replacing parts of the application.

Agreements and working practices can also make switching difficult. A supplier may manage source code, accounts or documentation without giving the customer full access. Long contracts, high exit costs and knowledge held only by the supplier increase dependency. Vendor lock-in does not mean switching is impossible, but that the barrier is so high that staying can seem the only practical option.

How do you reduce the risk?

Consider a possible future switch before choosing a supplier. Record who owns the code and data, where accounts are managed and which export formats are available. Use open standards and open sourceGlossary · In briefopen sourceOpen source is software whose source code is available under a licence that allows others to use, study, modify and redistribute it.Read more technology where appropriate, and avoid keeping essential business logic solely in proprietary services.

An exit plan clarifies what a switch would require. Check both whether export is technically possible and whether the exported data is complete and usable. Good documentation, transferable accounts and current knowledge within your own team reduce dependence on one party.