George Orwell — 1984
We did. Your Sealed key is derived in your browser from your Touch ID. Our servers have never seen it. They could not decrypt your private fields even if they wanted to. Or anybody else.
6 corners. Front face dominant, slight depth peek right + top.
A. Subtle
B. More depth
C. Just a hair
D. Lighter top
E. A at 40px
F. Red at 40px
Every password manager was built before AI agents existed. Now they need to catch up.
All others give your AI agent access to everything in your vault, or nothing at all. Your AI needs your GitHub token — it shouldn't also see your passport number.
"AI-safe" vaults still decrypt everything server-side. If the server can read it, it's not truly private. Math beats policy every time.
Your AI can't log in, pass two-factor, or rotate keys without access. clavitor lets it do all three — without exposing your credit card to the same pipeline.
How it works
Every field is encrypted. But some get a second lock. That second key is derived from your fingerprint and only exists in your browser. We hold the safe. Only you hold that key.
Encrypted at rest, decryptable by the vault server. Your AI agent reads these via MCP.
Encrypted client-side with WebAuthn PRF. The server never sees the plaintext. Ever.
Not another password manager with an AI checkbox. The architecture is the feature.
Each field has its own encryption tier. Your AI reads the username, not the CVV. Same entry, different access.
Sealed encryption uses WebAuthn PRF — a cryptographic key derived from your biometric hardware. Math, not policy. We literally cannot decrypt it.
Store TOTP secrets as Agent fields. Your AI generates time-based codes on demand via MCP — no more switching to your phone.
Create separate MCP tokens per agent. Each token sees only its designated entries. Compromise one, the rest stay clean.
No Docker. No Postgres. No Redis. One Go binary, one SQLite file. Runs on a Raspberry Pi. Runs on a $4/month VPS.
Import from any password manager. The built-in LLM automatically classifies which fields should be Agent vs Sealed.
Create scoped MCP tokens per agent. One compromised agent exposes one scope — not your entire vault.
~/.claude/mcp.json
{
"mcpServers": {
"vault-dev": {
"url": "http://localhost:1984/mcp",
"headers": { "Authorization": "Bearer mcp_dev_a3f8..." }
},
"vault-social": {
"url": "http://localhost:1984/mcp",
"headers": { "Authorization": "Bearer mcp_social_7b2e..." }
}
}
}
Four ways in. Each one designed for a different context. All pointing at the same encrypted store.
MCP
Claude, GPT, or any MCP-compatible agent can search credentials, fetch API keys, and generate 2FA codes — scoped to exactly what you allow.
Extension
Autofill passwords, generate 2FA codes inline, and unlock L3 fields with Touch ID — without leaving the page you're on.
CLI
Pipe credentials directly into scripts and CI pipelines. vault get github.token — done.
API
REST API with scoped tokens. Give your deployment pipeline read access to staging keys. Nothing else.
The competition
Real complaints from real users — about 1Password, Bitwarden, and LastPass. Pulled from forums, GitHub issues, and Hacker News. Not cherry-picked from our own users.
1PASSWORD — Community Forum
"The web extensions are laughably bad at this point. This has been going on for months. They either won't fill, wont' unlock, or just plain won't do anything (even clicking extension icon). It's so bad"
BITWARDEN — GitHub Issues
"Every single website loads slower. From Google, up to social media websites like Reddit, Instagram, X up to websites like example.com. Even scrolling and animation stutters sometimes. javascript heavy websites like X, Instagram, Reddit etc. become extremely sluggish when interacting with buttons. So for me the Bitwarden browser extension is unusable. It interferes with my browsing experience like malware."
LASTPASS — Hacker News
"The fact they're drip-feeding how bad this breach actually was is terrible enough... Personally I'm never touching them again."
— intunderflow, January 2023 ↗
1PASSWORD — Community Forum
"Since doing so, it asks me to enter my password every 10 minutes or so in the chrome extension"
— Anonymous (Former Member), November 2022 ↗
BITWARDEN — Community Forums
"the password not only auto-filled in the password field, but also auto-filled in reddit's search box!"
"if autofill has the propensity at times to put an entire password in plain text in a random field, autofill seems like more risk than it's worth."
BITWARDEN — Community Forums
"Bitwarden REFUSES to autofill the actual password saved for a given site or app...and instead fills an old password. It simply substitutes the OLD password for the new one that is plainly saved in the vault."
All quotes verbatim from public posts. URLs verified. View sources →
A password manager that only works on your home network isn't a password manager. Your laptop moves. Your phone moves. Your browser extension needs your vault at the coffee shop, on the plane, at the client's office.
Self-hosting that means a server with a public IP, DNS, TLS certificates, uptime monitoring, and backups. That's not a weekend project — that's infrastructure.
We run clavitor across 22 regions on every continent. $20 $12/yr. Your Sealed keys never leave your browser — we mathematically cannot read your private fields.
One command. No dependencies.
Terminal
MCP config for Claude Code / Cursor / Codex
{
"mcpServers": {
"clavitor": {
"url": "http://localhost:1984/mcp",
"headers": { "Authorization": "Bearer mcp_your_token_here" }
}
}
}