A Password Manager Built for Developers

1Password and Bitwarden treat API keys as text in a Secure Note. There's no provider awareness, no expiry tracking, no environment tagging. You end up storing the same kind of data in three different shapes, and rotating becomes manual archaeology.

PassCryp's data model knows the difference between a login, an API key, an SSH key, a credit card, and a secure note. Each type has the right fields, the right UI, and the right alerts. Provider presets cover AWS, Stripe, OpenAI, GitHub, Vercel, Supabase, and dozens more.

Morning standup: unlock the vault with your master password. The extension is active across every tab. Open the dashboard for a side project, copy the Stripe test key from the vault (auto-clear in 30s), and you're moving.

Pair-programming session: share the project vault with your collaborator. They unlock with their own master password; the per-vault key is wrapped to their public key. Revoke them when the session ends and the vault key rotates instantly.

End of week: open the expiry tab and see the 3 API keys rotating next week. Rotate upstream, update PassCryp, and CI picks up the new values automatically.

`passcryp unlock` prompts for your master password and caches the vault key in shell session memory (never on disk). `passcryp get <name>` returns the secret on stdout, pipe it anywhere. `passcryp env --project myapp --env prod` exports project env vars to your shell without writing a file.

Auth is per-machine: each shell gets a session that expires on idle. No plaintext token sits in `~/.config` waiting to be copied. Same zero-knowledge model as the web vault, just with a TTY.