Cloud Vendor Lock-In: Real Risk or Overblown Fear for Developers?

Vendor lock-in occurs when an organization becomes so dependent on a specific vendor that switching becomes costly or technically difficult, as seen when Broadcom acquired VMware and introduced disruptive pricing changes. To avoid this risk, some teams opt for self-managed Kubernetes clusters, on-premises datacenters, or strictly open-source tools, even when managed cloud alternatives may be more efficient. Advocates like David Heinemeier Hansson promote building private datacenters, but critics argue such decisions often ignore the true total cost of ownership, including staffing, security, and maintenance. Overreliance on open-source solutions can also introduce operational overhead, particularly for teams lacking strong DevOps expertise. Engineering decisions ultimately involve trade-offs, and letting fear of vendor lock-in drive strategy can lead to unnecessary complexity rather than genuine resilience.