Derive locally
Your master password feeds Argon2id on-device. Keys live only in volatile memory for the session.
Cloak
A zero-knowledge desktop vault for credentials, API keys, and encrypted .env files. Sync convenience. Local cryptography. Opaque cloud storage.
Open source under MIT.
Native for Windows, macOS, and Linux · MIT open source
Encrypted on-device · synced as ciphertext
Built for the stack you already trust
Product
Cloak unifies everyday credentials with developer workflows — most notably encrypted .env management — behind a fast, native interface.
Store logins and tokens the way you work. Masked by default. Revealed on demand, per field.
Import plaintext or dotenvx-encrypted configs. Values sealed client-side; keys wrapped with your master key.
Group secrets by project. Keep recovery codes organized without scattering them across notes apps.
How it works
A horizontal story of local cryptography — scroll to walk the path secrets take.
Your master password feeds Argon2id on-device. Keys live only in volatile memory for the session.
XChaCha20-Poly1305 encrypts every secret before anything touches the network.
The API holds opaque blobs and auth hashes. It has nothing to decrypt — by design.
Browse metadata freely. Decrypt only the field you reveal or copy — never bulk on load.
Features
Cryptography
A per-user Vault DEK is wrapped by your master key — and by a recovery-wrapping key — so resets re-wrap without exposing data.
Argon2id · XChaCha20-Poly1305 · domain-separated KDFs
Developer workflow
Import plaintext or already-encrypted dotenvx files. View, decrypt, edit, and delete — with the private key sealed under your master key.
Per-value encryption · wrapped key token · opaque sync
Exposure model
Secrets render as truncated ciphertext by default. Reveal and copy decrypt a single field in real time — conveying that decryption is intentional.
No bulk decrypt on browse · metadata-only search
Account recovery
A Recovery Key plus email flow lets you reset a lost master password. The server never learns your secrets — only new wrapped keys.
Zero-knowledge recovery · OS secure-store Remember Me
Why Cloak
The gap between password managers and cloud secret stores — filled by local cryptography.
The gap — Built for logins — not .env workflows, API key lifecycle, or dotenvx.
With Cloak
Five modules including environment files and projects.
The gap — Often require trusting the provider with keys that can decrypt your data.
With Cloak
Server stores ciphertext it cannot read. Ever.
The gap — Secrets scatter. History leaks. Accidental commits happen.
With Cloak
Encrypted vault with on-demand reveal and sandbox to explore safely.
Voices
“I needed something that understood .env files the way I understand them — encrypted at rest, sealed before sync, never plaintext in the cloud.”
“The reveal model is the point. You feel the decryption. That alone changes how carefully you treat secrets.”
“Sandbox mode sold me. Full UI, dummy data, no account — then I built from source when I was ready.”
By design
0
plaintext secrets on the server
0
vault modules in one native app
0
platforms — Windows, macOS, Linux
0-day
Remember Me via OS secure store
Product
production.env
api-service · dotenvx
01
Projects, modules, and search over non-encrypted metadata — without waking sealed fields.
02
Click to decrypt. Copy to clipboard. Everything else stays masked.
03
Bring encrypted configs in. Keep the private key wrapped under your master key.
FAQ
Security model, platforms, sandbox, and license — without the marketing fog.
Your master password and plaintext secrets never leave the device. Keys are derived with Argon2id locally; secrets are sealed with XChaCha20-Poly1305 before any network request. The API stores ciphertext it cannot decrypt.
Download the native app, explore Sandbox, or build from source. Cryptography happens on your machine — every time.
Open source under MIT.