[verdict][generated prompt][source: 1password.com]
Can I vibecode 1Password?
// buildable in a weekend, but real gaps stay open
A basic encrypted vault is buildable, but browser autofill, mobile apps, passkeys, sharing, recovery, audits, and trust make this a dangerous thing to replace casually.
confidence: high
what it is: Password manager for logins, passkeys, secrets, and secure sharing
Buildability index · an editorial game
- Price 2.99 $/month weight: zero
- Time multi-day weight: plus 1
- Category security no weight
- Moat brand and trust · execution quality weight: minus 2
- Confidence high weight: plus 1
- What you lose 7 items weight: minus 3
- Site 1password.com (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Create a local encrypted vault, generate passwords, search entries, and optionally sync the encrypted database with a cloud drive.
what you need
- strong encryption library
- secure key derivation
- browser extension if autofill matters
- mobile/desktop storage
- backup plan
A crucial honesty page: buildable in theory, but replacing a password manager is high-risk.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build me a local encrypted password vault to replace 1Password, CLI-first. Requirements:
- A single-binary CLI in Go using filippo.io/age for encryption and Argon2id
(golang.org/x/crypto) to derive the key from my master passphrase. Use the
library primitives exactly as documented, invent no crypto.
- The vault is one encrypted file at ~/.vault/vault.age holding JSON entries:
name, username, password, URL, notes, updated timestamp.
- Commands: add, get <name> (copies to clipboard, clears it after 20 seconds),
ls, gen (32-char random password), edit, rm.
- Fuzzy name matching on get; never print a password to stdout unless --show
is passed.
- vault backup writes a date-suffixed copy of the encrypted file to a folder
set in .env; it is already encrypted, so any cloud drive can sync it.
- Import from a 1Password CSV export so I can migrate in one command.
- Everything local: no server, no accounts, no telemetry.
- Out of scope: browser autofill, passkeys, and secure sharing. Those are why
people pay 1Password; if I need them the honest move is KeePassXC or
Bitwarden, say exactly that in the README.
- README: a five-line threat model, how key derivation works, and a warning
that losing the master passphrase loses everything, there is no recovery.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- browser/mobile autofill
- passkey support
- secure sharing
- recovery
- audits
- watchtower alerts
- family/team management
Why people still pay
They pay because password managers are one place where reliability and audited security beat saving a few dollars.
moat: Brand and trust Execution quality what a moat is
security/trust/cross-platform
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (3) — and why
- KeePassXC (si apre in una nuova scheda) — Excellent local secrets and passkeys; secure multi-user sharing is deliberately absent.
- Padloc (si apre in una nuova scheda) — The live site hides a stalled repo: last commit March 2025 and production self-hosting docs never really arrived.
- Proton Pass Free (si apre in una nuova scheda) — Passkeys and unlimited logins are free; secure vault sharing and broader monitoring are paid.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- KeePassXC (opens in a new tab) — Mature open-source local password manager and the safest DIY-adjacent alternative. (alive)
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
