Seal it locally.
vaultenv push production reads .env.production, draws a fresh 96-bit IV and encrypts with AES-256-GCM. The AAD binds the packet to this project and environment. Your key never leaves.
VaultEnv encrypts every .env value before it moves. The server keeps a sealed packet, never the key. Open it with one npx command where your code runs.
npx vaultenv@latest initFree for 3 projects No card One command to start
acme-cloud/web-platform EXAMPLE
8f3a 91c0 7b2e 44d1 0aa7 5c19 e2b8 6f03 d7a4 1e6c b40f 2d85 9c71 3a6e 88f2 07bd e154 6c9a 2f38 a1d0
Zero-knowledge is not a policy here. It is the shape of the system. The server is useful precisely because it is ignorant.
DECLASSIFIED / BY DESIGNA packet makes three stops. The key makes one. That difference is the product.
vaultenv push production reads .env.production, draws a fresh 96-bit IV and encrypts with AES-256-GCM. The AAD binds the packet to this project and environment. Your key never leaves.
The server stores ciphertext, IV, AAD and a revision number. No key, no plaintext, no recovery backdoor. A packet copied from staging to production fails its tag before a single value is read.
CIPHERTEXT + METADATA ONLYvaultenv run -- next dev pulls the latest revision, verifies the tag, decrypts in memory and injects the values into the child process. Nothing hits disk. vaultenv build does the same for CI from a Git-safe .env.vault.
This is the real cipher, running in this tab. Type a value, seal it, inspect the packet, then break the seal. Nothing is sent anywhere.
Your sealed packet will land here.
The plaintext stays in the form. The output is ciphertext.A fresh key is generated for this demo. It stays in this tab and disappears when you leave. Nothing is transmitted or stored.
Six entries, each one checkable in the code or in the protocol. No promises that live only on a marketing page.
AES-256-GCM with a fresh 96-bit IV on every push. AAD binds each packet to its project and environment.
CLIENT-SIDECiphertext, IV, AAD and revision metadata. No key, no plaintext, no recovery path on our side.
NO KEYSProject keys wrapped with each member’s ECDH P-256 public key. Environment-scoped roles decide who can open what.
SCOPEDThe decryption key travels in the URL fragment and never reaches the server. The record burns after the first read.
ONE READEvery push appends an immutable revision. Roll back to any retained version without re-encrypting older packets.
APPEND ONLYOne VAULTENV_KEY in your runner decrypts a committed .env.vault offline. Vercel, Docker and GitHub Actions all work.
PORTABLEThe server can delete a packet. It can refuse to serve one. It cannot read one.
Every workflow is one npx call. Install the CLI globally when you prefer a stable binary on every machine.
npm i -g https://env-vault.fkodelabs.com/cli.tgznpx vaultenv@latest initLinks a GitHub repo, writes .vaultenv.json, appends .env* to .gitignore and generates a local VAULT_KEY.
npx vaultenv@latest push [env]Encrypts .env locally with a fresh 96-bit IV and uploads ciphertext only. The revision increments.
npx vaultenv@latest pull [env]Fetches the latest or a pinned @v3 packet, verifies the AAD and decrypts on your machine.
npx vaultenv@latest run -- <cmd>Injects secrets straight into a child process. No plaintext file is ever written.
npx vaultenv@latest buildCompiles every active environment into one Git-safe .env.vault for offline CI/CD.
npx vaultenv@latest rotateGenerates a fresh key, re-encrypts active environments client-side and revokes compromised tokens.
The CLI is a thin client. It does the encryption locally, then treats the API as a dumb, encrypted locker.
Three tools solve the same problem differently. This is the narrowest honest read of the public docs.
| Capability | VaultEnv | EnvVault | Dotenv Vault |
|---|---|---|---|
| Client-side AES-256-GCM | Yes, ciphertext only | Yes | No, server holds keys by default |
| Single-command npx workflow | Yes, npx or global install | No | Yes |
| Git-safe .env.vault artifact | Yes, offline decrypt | No | Yes |
| Zero-disk runtime injection | Yes, run -- <cmd> | No | Partial |
| GitHub repo and branch sync | Yes, repo vaults | Manual projects | Manual projects |
| Team key wrapping and RBAC | Yes, ECDH P-256 | Yes | Server-managed |
Compiled from public documentation, November 2026. Check the current docs before you switch.
All plans use the same cipher. Paid plans add room, not stronger encryption.
For solo builders & prototypes
One price, no seat maths
For shipping startups & indie studios
One price, no seat maths
For production engineering orgs
Plus $5 per extra seat
Dodo Payments checkout is ready; sandbox billing is active in this build. Prices in USD. Cancel anytime.
Start with three projects and one command. Invite the team when the repo goes live.