Pricing
The encryption is not the paid part and never will be. What a paid plan buys is the shape around it — vaults, an audit trail, and the accounts that make a share attributable to somebody.
01 / Plans
No plan weakens the guarantee. A paid share is encrypted exactly the same way a free one is, and the server can read neither.
These plans are a draft.Only the Free tier exists today. Pro and Enterprise pricing is not final and nothing on this page is a commitment — see the FAQ for what is actually available now.
$0forever, no account
Everything needed to hand one person a password safely. This is the product as it exists today.
$Xper user, per month
For a team that shares credentials often enough to want them organised, attributable, and revocable in one place.
Customannual, invoiced
For an organisation that has to answer to an auditor, or that would rather the whole thing ran on its own hardware.
02 / Self-hosting
The backend is one Rust binary over a SQLite/libSQL file. There is no licence key and no phone-home.
A hardened, non-root image and a Compose stack with an ordered one-shot migration, a persistent volume, and a readiness check.
No costEncrypted payloads and the control plane share one schema. Point it at a local file or a remote libSQL instance in whichever jurisdiction you have to answer to.
No costThe HTTP security and network-access boundaries are shared code. Self-hosting does not mean running a weaker build.
No cost