TL;DR Vendor lock-in is what happens when leaving a platform costs more than staying does - even after it stops serving you well - because your data, workflow, or history is trapped inside it.
Vendor lock-in is what happens when switching from one platform or service to another becomes expensive, difficult, or effectively impossible - whether because data can't be exported, contracts forbid it, or the practical friction is simply too high to bother.
Origin & Context
Lock-in isn't accidental - it's frequently a deliberate business strategy. Making data export difficult, using proprietary formats that don't transfer cleanly, or building deep integrations that would all need to be rebuilt elsewhere all raise the cost of leaving, independent of whether the product itself is still good. The everyday synonyms for this - platform lock-in, digital ownership disputes, the case for local-first software - are all describing the same underlying trap from different angles.
Why It Matters for Digital Independence
Lock-in is precisely the mechanism this entire project exists to work around. A company doesn't need to keep earning your business once switching costs enough - years of history, an established workflow, and irreplaceable integrations become the reason you stay even after a price hike or a feature you depend on disappears.
Real-World Examples
Years of photos, contacts, and purchase history built up inside one company's ecosystem is lock-in, even if nobody ever calls it that. Leaving means starting over, not just switching apps. The same pattern shows up in business software: a team standardizes on a chat or project-management tool, builds years of history and integrations on top of it, and then absorbs a price increase they'd never have accepted as a new customer, simply because migrating everything elsewhere costs more than paying up. Self-hosted, open-source, and open-format tools are the direct countermeasure: Nextcloud's files are just files, Immich's photos export cleanly, and an open format doesn't hold your own data hostage to keep you as a customer.
What You Can Do
Before adopting any new service, it's worth asking one question up front: can I get all my data back out, in a usable format, if I want to leave next year? If the honest answer is no, that's lock-in being built in from day one - and it's a much cheaper problem to notice before you commit than after.
Related Terms
- Self-Hosted - a direct countermeasure to vendor lock-in
- Open-Source - reduces lock-in through portable, inspectable formats
- Data Ownership - what vendor lock-in ultimately threatens
- Nextcloud - a concrete example of a lock-in-resistant tool