Open-source encrypted knowledge workspace
The credible gap is not merely an open-source note application with E2EE. Joplin and Notesnook already meet that description, and Anytype supplies another local-first alternative. Obsidian itself keeps user content in local files and offers E2EE through its paid Sync service, although the application is proprietary.
The missing combination is an Obsidian-class workspace whose durable format, clients, sync, extensions, collaboration, and recovery are all credible at the same time.
Required product shape
The product would need:
- ordinary inspectable files or a lossless documented export
- offline-first desktop and mobile clients
- background E2EE sync that does not require key choreography
- conflict explanation and version recovery
- fast mobile capture and attachment handling
- shared spaces with understandable membership changes
- a permissioned extension model
- verifiable builds and published security review
- self-hosting as an exit path, not as the only usable deployment
Plain Markdown alone is insufficient. Attachments, metadata, links, canvas objects, databases, and plugin-defined state also need a continuity contract.
Monetization
Use open clients and a paid hosted sync service, with team administration, managed recovery choices, migration, and support as paid layers. An acquisition-continuity covenant, export escrow, and reproducible release path could become meaningful differentiators.
The lowest-risk first business is not a new editor. It is Privacy migration and continuity for existing Obsidian, Joplin, Notesnook, and Anytype users, plus a compatibility and recovery test corpus. Only build the workspace after those migrations expose a repeated defect that upstream tools cannot or will not fix.
Why this remains hard
This market is crowded, and users compare every missing editor feature against mature incumbents. E2EE makes server-side search, collaboration, and support more difficult. Extensions can exfiltrate plaintext even when sync encryption is sound. Mobile background restrictions turn theoretically correct sync into a practical failure.
The commercial question is therefore narrow: which user segment will pay for the complete trust and continuity package, rather than merely prefer open source in a survey?