Prevon

Roadmap

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

The encryption, the on-device AI, the sync protocol (off by default, no independent audit) and the permission system are built and being tested in the private beta. We hope to reuse them for whatever comes next, with a new interface on top. 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. The beta is how we test the layer underneath. Anything built next is meant to reuse the encryption, the AI's permission tiers, the audit log, and the sync protocol rather than rebuilding them from scratch. None of it has had an independent security audit yet.

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.” We expect that to be a smaller project than starting from nothing, small enough that it's worth asking what people want instead of just picking one ourselves. Nothing here is a commitment or a timeline.

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 design, same on-device AI, a different interface on top.
PhotosA photo vaultPhoto storage designed to be encrypted, with on-device search, designed so images are not sent to a cloud AI.
CalendarA calendarYour schedule, designed to be encrypted , with the same AI that already understands your notes.
MessagingA messaging appPrivate messaging designed to be end-to-end encrypted, built on the same engine as your vault. Nothing here is built yet, and metadata exposure is not yet designed.