Vendor lock-in
When leaving a provider would cost so much that you are stuck with it.
Vendor lock-in is the situation where a company depends so heavily on one supplier's products that switching to another would be slow, risky or very expensive. It is not a contract clause; it builds up quietly as you use features only that vendor has.
In the cloud it usually looks like this: an app built on a provider's own database, its own queues, its own serverless functions and its own identity system. Each service is convenient on its own, but together they mean the code only runs there. Moving the data out can also cost money, since providers often charge for data leaving their network.
Some lock-in is a fair trade: managed services save real work, and a team that avoids every one of them often ends up building and running a lot of plumbing itself. The point is to choose it with open eyes: know which pieces would be hard to move, keep data in open formats, and prefer open standards like SQL, containers or Kubernetes where switching might matter.
Keep in mind
- It is the cost of switching, not a ban on switching.
- It grows from using features only one provider offers.
- Fees for moving data out add to the cost of leaving.
- Open standards and open data formats keep the exit door open.
