API keys pasted into Slack DMs stay there forever. Rotating them means asking three people if they still have the old one.
A dozen repos, each with its own .env.local, .env.production, and .env.example that nobody keeps in sync.
Copy DATABASE_URL from the wrong source and suddenly your local build is pointing at production.
Dotvault is structured around projects and the credential types developers actually use.
Each project gets its own vault with tabs for Logins, SSH, API keys, Tokens, and Env. STRIPE_SECRET_KEY lives under acme-api, not next to your Netflix password.

Logins, API keys, tokens, and SSH configurations, each with fields that match how you actually use them.
No more keeping two .env files straight. Switch environments inside the same project and copy the one you need, when you need it.


Need a new database password or OAuth secret? Generate it inside the vault and save it in the same place, no browser tab, no clipboard history full of secrets.

Move your vault to another machine or back it up offline. The file stays encrypted end-to-end. You only need the same master password to unlock it anywhere.

Not a password manager with a dark mode. Not enterprise infrastructure you have to host.
Your master password never leaves your device. There is no server to breach and no account to hack.
Memory-hard password hashing tuned to resist GPU and ASIC cracking.
Authenticated encryption with a fresh nonce for every project write.
Decrypted data lives in memory only, and only while the vault is unlocked.
Set a timer and the vault locks itself when you step away. No secret left sitting on screen.

The desktop app is free during beta in exchange for feedback. After launch, it becomes a one-time purchase. Beta testers keep access.
Beta builds are unsigned, your OS may warn on first launch.