What is Zero Vendor Lock-In?

Zero vendor lock-in is a software engineering commitment guaranteeing that a customer’s data, workflows, and intellectual property remain completely independent of the application used to create them.

In proprietary cloud software models, vendor lock-in is frequently treated as an intentional business strategy. By making it difficult for users to export their data or move to competitors—through non-standard APIs, proprietary block data formats, and complex database relationships—companies increase customer switching costs to protect recurring subscription revenues.

The mechanisms of artificial software lock-in

Proprietary platforms enforce lock-in through several common architectural techniques:

1. Closed database schemas: Documents exist only as rows in remote cloud databases (e.g., PostgreSQL or MongoDB), inaccessible via standard local operating system tools.
2. Proprietary block structures: Content is fragmented into proprietary JSON objects that cannot be parsed by standard Markdown or HTML compilers without proprietary conversion tools.
3. Degraded export fidelity: Export functions convert structured notes into static PDFs or flattened plain text, stripping bidirectional links, embedded attachments, and metadata tags.
4. Proprietary media containers: Audio recordings and attachments are stored behind authenticated cloud URLs that expire if you cancel your subscription.

The architectural criteria for zero lock-in

To achieve authentic zero lock-in, software must satisfy four strict invariants:

Criterion	Proprietary Lock-In	Zero Lock-In (Oyma)
File Format	Proprietary JSON / database blocks	Standard UTF-8 CommonMark / GFM
Storage Location	Vendor cloud server	User-selected folder on local Mac
Export Protocol	Manual export with formatting loss	Zero export needed; already files
Tool Portability	Incompatible with third-party tools	Compatible with VS Code, Obsidian, Vim

Zero lock-in in Oyma

Oyma rejects artificial lock-in completely.

When you use Oyma on macOS:

• Notes are stored directly as standard .md files in your chosen folder.
• Audio recordings are saved as standard audio files in your local attachments directory.
• Meeting records follow transparent CommonMark and GFM conventions.
• If you ever decide to stop using Oyma, you don’t need to click “Export”. You simply open your folder in Obsidian, VS Code, or Finder. Every link, table, callout, and tag remains intact.