Cloud Vendor Lock-In Has Four Distinct Layers, and Each Carries a Different Exit Cost

A technical analysis published on DEV Community argues that cloud vendor lock-in is not a single problem but four separate layers: data, platform, contract, and operations, each with its own cost to unwind. The platform layer — covering managed databases, serverless computing, IAM, and observability — is identified as the highest-risk area due to the lack of direct equivalents across providers. The piece contends that lock-in only becomes a serious concern when it traps regulated data, undermines pricing leverage, or makes migration prohibitively expensive. Infrastructure-as-code tools like Terraform are recommended as a high-leverage mitigation for the operations and platform layers, making dependencies explicit and exits more auditable, though not eliminating platform dependency itself. The author advises teams to audit each layer, assign a concrete exit-cost estimate, negotiate egress and deconversion terms before committing to contracts, and revisit the assessment on a regular schedule.