Loading...
When leaving a provider would cost more than staying: the price of convenience, compounded.
Quick Definition
Vendor lock-in is dependence on a single provider's proprietary services, making it costly or difficult to switch. While managed services boost productivity, heavy lock-in reduces negotiating leverage and flexibility, which is one motivation for multi-cloud and portable, open standards.
Vendor lock-in is the state where switching away from a provider has become so expensive, in migration effort, retraining, and re-engineering, that you effectively cannot leave. In cloud, it grows quietly: each managed service adopted, each proprietary API integrated, each team trained deepens the commitment.
Lock-in is not automatically bad. Proprietary managed services often deliver real speed and lower total cost of ownership than portable alternatives. The mistake is accumulating lock-in unknowingly, then discovering it during a price increase or contract negotiation when leverage has already evaporated.
Example. A company built around one provider's proprietary database receives a 35 percent renewal increase. Migration is quoted at 18 months of engineering work, so they sign. The discount they could not negotiate is the measurable price of lock-in.
Sensible practice is deciding deliberately where lock-in is acceptable: use open standards like Kubernetes and Terraform at the portability layer, accept proprietary services where the value is clear, and document exit paths for critical systems. The multi-cloud guide examines when a multi-cloud posture is a real hedge and when it is expensive theater.
No, and pursuing total portability usually costs more than the lock-in it prevents. The goal is informed, deliberate commitment.
Partially, at real cost in complexity and forgone discounts. For most teams, portability at key layers matters more than running everywhere.
Estimate honest exit cost, engineering months plus risk, for critical systems. If the number is unknown, leverage in negotiations is too.