Myne
Roadmap

Where Myne is going.

An order, not a schedule. Bootstrapped and slow, shipped one phase at a time. No dates and no cadence promise — and every line here stays inside the public threat model.

Ledger/ledger
01
Foundation
v0.1 · public spec

The cryptographic core and the documents that govern it.

Public threat model & protocol spec Shipped
Local encryption — Argon2id, XChaCha20-Poly1305, key commitment Shipped
No-email identity & 24-word recovery phrase Shipped
Plain-markdown vault, encrypted on disk Shipped
Encrypted backup & restore Shipped
Cross-implementation test vectors Shipped
02
Desktop
phase 1 · pre-alpha

The single-user app you write in, running entirely on your device.

Tauri desktop client — editor, autosave, encrypted vault In progress
CodeMirror editor with live markdown & [[wikilinks]] In progress
Full-text search across decrypted notes In progress
Backlinks pane & minimal graph view In progress
Import from Obsidian In progress
Signed, reproducible desktop builds In progress
03
Sync
phase 2 · planned

Zero-knowledge sync — the server only ever holds ciphertext.

Zero-knowledge sync server Planned
Self-hostable, identical open-source server Planned
Hosted sync — optional paid tier, ciphertext only Planned
04
Mobile & web
phase 3 · planned

The same vault, the same encryption, in your pocket and your browser.

iOS client Planned
Android client Planned
Web client Planned
05
Collaboration
phase 4 · planned

Shared, real-time editing — once the rest of the product is solid.

Real-time collaborative editing (CRDT) Planned
Note sharing Planned
This page is append-only in spirit: items move from planned to shipped, they do not gain deadlines. No venture timeline, no hype cycle. When a protocol or spec change lands, the reasoning goes in the ledger.