Vendor Lock-in
The situation where switching to a different tool or service becomes prohibitively difficult due to proprietary dependencies.
Also known as: Lock-in, Platform Lock-in, Tool Lock-in
Category: Principles
Tags: data-portability, knowledge-management, tools, risk-management, principles
Explanation
Vendor lock-in occurs when a customer becomes dependent on a vendor's products or services, making it difficult or expensive to switch to an alternative. In knowledge management, this is a critical consideration because your notes may represent decades of accumulated thinking.
**Forms of lock-in in PKM:**
1. **Data formats** - Proprietary file formats that can't be easily exported or converted
2. **Tools and platforms** - Features that only work within one ecosystem
3. **Data handling** - APIs or storage methods that restrict data access
4. **Extensions and plugins** - Customizations that don't transfer to other tools
**How to avoid vendor lock-in:**
- **Use open file formats** - Prefer Markdown, plain text, and open standards over proprietary formats
- **Favor local-first software** - Tools that store data on your device give you full control
- **Regular exports** - Periodically export your data to ensure it's portable
- **Evaluate exit scenarios** - Before adopting a tool, understand how you would migrate away from it
- **Prefer interoperable tools** - Choose software that plays well with others through standard APIs and formats
The principle of 'File over app' captures this well: your files should outlive any single application. Tools like Obsidian, which use plain Markdown files, exemplify this approach - even if the tool disappears, your notes remain accessible.
Related Concepts
← Back to all concepts