Claude Code
Can explain the cryptography and write a learning version with tests, while flagging what needs expert review.
Security · updated 2026-11-03
Don't: No, use a product No. A password manager holds the keys to everything you own; one crypto or sync mistake exposes all of it. Build one only to learn, and keep using an audited product.
AI tools will happily generate a password vault with encryption, and it may even look correct. That is the danger. Real password managers rely on zero-knowledge designs, careful key derivation, audited cryptography, secure autofill and years of security reviews. A subtle bug will not show up in testing but will expose every account you have. Learn from building one, then use 1Password, Bitwarden or your platform's built-in manager.
1Password is password manager that stores logins, passkeys and secrets in encrypted vaults synced across devices. This page is about building your own version for personal or internal use, or to learn how this kind of product works, not about copying 1Password to compete with it. How we grade.
Difficulty is for a solo builder using an AI coding tool. Skip means not worth building yourself.
| Feature | Difficulty | Why |
|---|---|---|
| Vault UI and search | Easy | Standard list and detail views. |
| Password generator | Easy | Use crypto.getRandomValues, never Math.random. |
| Client-side encryption | Hard | Argon2id key derivation and authenticated encryption via WebCrypto or libsodium; mistakes are invisible. |
| Sync across devices | Hard | Encrypted blobs with versioning and conflict handling. |
| Account recovery | Hard | Zero-knowledge means lost master password equals lost data unless you design recovery keys. |
| Browser extension autofill | Hard | Origin matching, iframe and phishing defences; a major attack surface. |
| Sharing with others | Hard | Public key encryption per recipient. |
| Passkeys and TOTP codes | Skip | Leave to audited products. |
Your own version vs 1Password, at personal or small-team scale.
Individual: $3.99/mo billed annually
Individual is $3.99 per month billed yearly ($2.99 in the first year for new customers); Families is $5.99. Teams and Business are priced separately.
Source: 1password.com/pricing/password-manager. Prices change; check before deciding.
| Running cost | Per month | Notes |
|---|---|---|
| Hosting and database for encrypted blobs | $0–$25 | Free tiers would work technically. |
| Security audit | $0 | Not a monthly cost, but a credible audit costs thousands; without it, you are trusting unreviewed code. |
| Total | $0–$25/mo | Saves up to $48 a year vs 1Password Individual; at the top of the range it costs $252 a year more. |
Can explain the cryptography and write a learning version with tests, while flagging what needs expert review.
Helpful for reading open-source password manager code, such as Bitwarden's clients, to learn how it is done.
Paste it into your tool, then ask for a plan before any code. Edit the specifics to match what you need.
This is strictly a learning project. I will not store real passwords in it. Build a minimal zero-knowledge password vault so I understand how password managers protect data. Stack: Next.js, Supabase (auth and Postgres for encrypted blobs only), WebCrypto or libsodium in the browser. Design: - Derive a key from the master password in the browser with Argon2id (libsodium) using a per-user random salt and documented parameters. - Generate a random vault key; encrypt it with the derived key. Encrypt each item with the vault key using authenticated encryption (XChaCha20-Poly1305 or AES-GCM with unique nonces). - The server stores only ciphertext, nonces, salts and KDF parameters. It never receives the master password or keys. - Separate the login password (hashed for auth) from the encryption key. Data model: users (id, kdf_salt, kdf_params, encrypted_vault_key), items (id, user_id, ciphertext, nonce, updated_at, version). Requirements: vault list, add, edit, delete, password generator with crypto.getRandomValues, auto-lock after 5 minutes, clipboard auto-clear. Security: strict Content Security Policy, no third-party scripts, Row Level Security, rate-limited login. Add comments explaining each cryptographic choice and list what a professional audit would check.
AI tools often get these wrong by default. Check each one before anyone else uses the app.
They went far past the prototype: support, payments, reliability and years of iteration. Their profiles show what that took.
Aleksandar Jovanovic built SecretDrop
Client-side encrypted, auto-expiring sharing for API keys and env files.
Colin Percival built Tarsnap
Encrypted backup service from the creator of the scrypt key derivation function.
If you need 1Password's job done rather than a project, these are built and supported by independent makers.
secretdrop.dev
Client-side encrypted, auto-expiring file sharing for API keys and .env files.
tarsnap.com
Encrypted, deduplicated online backup service for UNIX-like operating systems, stored on Amazon S3.
You learn key derivation, authenticated encryption and zero-knowledge architecture, which improves how you handle secrets in every app.
Don't. No. A password manager holds the keys to everything you own; one crypto or sync mistake exposes all of it. Build one only to learn, and keep using an audited product.
A working personal or internal MVP takes about 8 h–3 days with a tool like Claude Code. A polished version you would rely on every day takes about 63–250 days, mostly spent on zero-knowledge encryption where the server never sees your keys.
Expect $0–$25/mo at personal or small-team scale (hosting and database for encrypted blobs, security audit). 1Password Individual costs $3.99/mo (checked 2026-11-03), so the most you would save is $48 a year, before counting your time.
Only as a learning project. Password managers depend on careful cryptography, secure autofill and independent audits, and a subtle mistake exposes every account you store.
Bitwarden is open source with a free tier and can be self-hosted, and Apple and Google include password managers in their platforms. These are far safer than a homemade vault.
AI can produce code that uses the right primitives, but it can also make subtle errors like nonce reuse or weak key derivation that tests will not catch. Security-critical code needs expert review.
Building your own tool that solves the same problem is common and generally fine. Copying 1Password's code, design assets, brand name or content is not. Use your own name and design, respect their terms of service, and get proper advice if you plan to sell it. This page is not legal advice.