Roadmap

The engine is built. What should we run on it next?

The hardest part — the encryption, the on-device AI, the sync protocol, the permission system — is already built and being exercised in the beta. It doesn't need to be rebuilt for whatever comes next. It just needs an interface on top of it. You get to help decide what that is.

Why this isn't starting from zero

Notes was the first thing built on the engine specifically because it's the hardest test case — constant reading, writing, deleting, and syncing, touching every layer at once. Get that right, and the layer underneath it is proven. Anything built next inherits the encryption, the AI's permission tiers, the audit trail, and the sync protocol automatically, instead of needing to rebuild all of it from scratch.

That changes the question. It's no longer “could we build a secure password manager or photo vault from nothing” — it's “which interface do we put on the engine we already have.” That's a much smaller, much faster project. Small enough that it's worth actually asking what people want, instead of just picking one ourselves.

Cast a vote

Four real options. Pick one.

These are genuine candidates, not a promise that any specific one ships next — that decision follows the votes, not the other way around. Something else in mind entirely? Say so on the Contact page.

PasswordsA password managerSame vault, same on-device AI, a different interface on top.
PhotosA photo vaultEncrypted photo storage with on-device search — no cloud AI ever sees your images.
CalendarA calendarYour schedule, encrypted , with the same AI that already understands your notes.
MessagingA messaging appActually private messaging — end-to-end encrypted, no metadata harvesting, built on the same engine as your vault.