Vault, Generator, AutoFill, Sync, Recovery, Sharing. Every feature traces back to a primitive in the security model — and stops where the threat model says it should.
Logins, secure notes, API keys, credit cards, software licenses, identity documents. All client-side encrypted, all searchable, all yours.
Backed by your operating system's CSPRNG. We don't have a "service" that "generates passwords for you" — generation is a single function call, on your device, taking your bytes from /dev/urandom.
iOS AutoFill API on iPhone. MV3 content scripts on Chrome. Both match by exact registrable domain — never by visual similarity, never with fuzzy matching that could leak credentials to a phishing clone.
Each change to the vault is sealed locally and pushed as a versioned delta. Other devices pull, verify the signature, decrypt locally, and replay. The relay sees a content-addressed ciphertext; nothing else.
One-time encrypted links for guests (a contractor, a friend, IT). Persistent shares for teammates via a public-key handshake. Revoke any share and the recipient's local copy refuses to decrypt.
Keevo can't email you a reset link, because we don't have anything to reset to. The Recovery Kit is your one-page failsafe — generated locally at signup, printed once, kept somewhere physically safe.
Pick a Master Password, generate a Secret Key, print the Recovery Kit. You're done.