Skip to content
dvnt.io

Resources · glossary

Vendor lock-in

Dependence on a single provider, where switching tools or vendors is so costly that it stops being a real option. It is rarely a decision, usually a side effect.

Also called
  • lock-in
  • supplier lock-in
  • proprietary lock-in
  • vendor dependency
  1. 01

    Where it comes from

    From data in a closed format, from custom code no one but the vendor understands, from having no access to the repository, or from a licence that ends with the contract. Each of these on its own is a small thing; together they form a wall.

  2. 02

    How to spot it early

    Ask three questions before signing: who owns the code, where the data sits and whether it can be exported in a readable format, and whether another company could take over the project without rewriting it from scratch.

  3. 03

    Is it always bad

    No. Every technology choice is some degree of commitment, and fighting for full portability can cost more than the risk it protects against. The point is for it to be a conscious price, not a surprise.

  4. 04

    What reduces the risk

    Standard technologies instead of proprietary ones, data in open formats, access to the repository from day one, and documentation written for an outsider.

In practice

Related terms

  • E-commerce migrationMoving an online shop to another platform along with its products, customers, orders and URLs. The biggest risk isn't the data; it's losing search visibility.
  • Headless CMSA content management system that stores content and serves it through an API but does not dictate how the site looks. The presentation layer is built separately, usually in a modern framework.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.