Roadmap
What's shipped, what's next, and what's only an idea
LiveVault is built by one person, so this roadmap is short and the ordering is real — each item genuinely waits on the one above it. Every entry carries a status, and the statuses are not decorative: Shipped means you can install it today, and Exploring means it may never happen.
Nothing here has a date. A dated roadmap from a one-person company is a guess in a costume, and the only thing it reliably produces is a page that is visibly wrong later.
The local vault
Foundation
The product as it exists today, and the work finishing it. All of it runs inside your browser, with no account and no server involved.
Capture anything, into local storage
ShippedPages, selected text, links, images, screenshots and standalone notes, from the toolbar popup or the right-click menu. Written straight to the browser's own storage with the source URL and a timestamp.
Search, collections and tags
ShippedFull-text search across every title, note, tag and captured selection, with collections and tags for the things worth organising. Neither is required in order to save something.
Export as a portable backup
ShippedOne click in Settings writes the entire vault to a single JSON file. Plain, documented, and readable without LiveVault — the point is that leaving is possible.
Chrome Web Store listing
ShippedApproved and publicly listed on 11 September 2026. One-click install, with reviews and updates handled through the store like any other extension.
Firefox and Edge builds
PlannedThe extension is written against the WebExtensions API rather than Chrome-specific interfaces, so this should be packaging, store review and per-browser storage quirks rather than a rewrite. Not started.
Full-page archive, not just the link
PlannedSave a readable snapshot of the page body alongside the URL, so a capture survives the page being edited, paywalled or taken down. Stored locally like everything else, which makes vault size the real design problem.
Beyond one browser
The things that need a server
Sync across devices and sharing with a team are the two limits people hit first, and neither can be solved inside a single browser. These are the items that take LiveVault from an extension to a business.
Optional end-to-end encrypted sync
PlannedThe same vault on a laptop and a desktop — the first hard limit of storing everything in one browser. Encrypted in the browser with a key derived from a passphrase, so the server stores ciphertext it cannot read. Opt-in, off by default, and a vault that never turns it on keeps behaving exactly as it does today.
Needs: Object storage, a sync API, and per-account isolation.
Shared team vaults
PlannedCollections a small team can capture into together — the research, the competitor pricing, the screenshots of the bug. This is what the Team tier is for, and it is the first feature that genuinely cannot work without accounts.
Needs: Identity, authorisation, and a multi-tenant data model.
Public API and webhooks
ExploringRead your own vault programmatically, or push captures into it from elsewhere. Interesting, frequently requested, and firmly behind the two items above.
Needs: A public API surface, rate limiting and token management.
Consolidating infrastructure
PlannedThe server-backed side of the business currently runs across three separate providers for compute, database and object storage — a reasonable way to start and a poor way to continue. Consolidating onto one cloud removes a class of operational work that a one-person team cannot afford to keep paying.
Needs: A single cloud account, with infrastructure defined as code.
What this does not do
Every item in this section is opt-in and off by default. Turning none of them on leaves LiveVault exactly as it is described everywhere else on this site: local-first, no account, no server, nothing leaving your browser. Sync is designed so the server holds ciphertext it has no key for — the guarantee is not that we promise not to look, it is that there is nothing readable to look at.
Influence it
The ordering is not settled
Sync and team vaults are both ahead of everything else, but which of the two comes first is genuinely open. If one of them is the reason you would or would not use LiveVault, that is worth more to this decision than any amount of guessing from here.