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.
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. vault1984 lets it do all three — without exposing your credit card to the same pipeline.
"Your assistant can book your flights.
Not read your diary."
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..." }
}
}
}
We host vault1984 across 22 regions on every continent. $12/year. Pick your region at signup.
Your Sealed keys are derived in your browser. We mathematically cannot read your private fields.
One command. No dependencies.
Terminal
MCP config for Claude Code / Cursor / Codex
{
"mcpServers": {
"vault1984": {
"url": "http://localhost:1984/mcp",
"headers": { "Authorization": "Bearer mcp_your_token_here" }
}
}
}