FIELD MANUAL / NO. 01ZERO-KNOWLEDGE ENVIRONMENT DISPATCHEST. 2026
ZERO-KNOWLEDGE ENVIRONMENT DISPATCHFOR GITHUB TEAMS

Your secretsleave homesealed.

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 init

Free for 3 projects No card One command to start

An example dispatch packet for the acme-cloud/web-platform repository. It shows ciphertext, a fresh IV, the environment AAD and a key that stays on the device.
DISPATCH PACKET

acme-cloud/web-platform EXAMPLE

PRODUCTION / v4
SEALED CONTENTS7 VARIABLES
8f3a 91c0 7b2e 44d1 0aa7
5c19 e2b8 6f03 d7a4 1e6c
b40f 2d85 9c71 3a6e 88f2
07bd e154 6c9a 2f38 a1d0
AES-256-GCM96-BIT IVPLAINTEXT 0 B
ALGORITHM
AES-256-GCM
IV
96-bit / random
AAD
vaultenv:v1:proj_acme_web:production
KEY
Held on your device
ROUTED FROM YOUR MACHINE
256-bitAES-GCM key length
0 bytesPlaintext stored on our servers
96-bitFresh IV for every push
1 commandnpx, with no binary to install

We can’t read your secrets.Not because we promise not to.Because the key never leaves your machine.

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 DESIGN
§ 02 / THE ROUTE

The route of a secret.

A packet makes three stops. The key makes one. That difference is the product.

01 / YOUR MACHINE

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.

CLI OR BROWSER / AES-256-GCM
02 / VAULTENV

Park the ciphertext.

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 ONLY
03 / RUNTIME

Open it where it runs.

vaultenv 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.

IN-MEMORY / ZERO DISK
§ 03 / THE SEAL LAB

Try the seal.

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.

  • WEBCRYPTO
  • AES-256-GCM
  • 96-BIT IV
Environment
Local only. No network request.
SEALED PACKETAWAITING INPUT

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.

§ 04 / THE LEDGER

The ledger of guarantees.

Six entries, each one checkable in the code or in the protocol. No promises that live only on a marketing page.

L-01

Cipher

AES-256-GCM with a fresh 96-bit IV on every push. AAD binds each packet to its project and environment.

CLIENT-SIDE
L-02

Server knowledge

Ciphertext, IV, AAD and revision metadata. No key, no plaintext, no recovery path on our side.

NO KEYS
L-03

Team access

Project keys wrapped with each member’s ECDH P-256 public key. Environment-scoped roles decide who can open what.

SCOPED
L-04

One-time shares

The decryption key travels in the URL fragment and never reaches the server. The record burns after the first read.

ONE READ
L-05

Version history

Every push appends an immutable revision. Roll back to any retained version without re-encrypting older packets.

APPEND ONLY
L-06

CI/CD

One VAULTENV_KEY in your runner decrypts a committed .env.vault offline. Vercel, Docker and GitHub Actions all work.

PORTABLE
VERIFIED BY CONSTRUCTION

The server can delete a packet. It can refuse to serve one. It cannot read one.

§ 05 / FIELD MANUAL

Six commands. No daemon.

Every workflow is one npx call. Install the CLI globally when you prefer a stable binary on every machine.

HOSTED INSTALL
npm i -g https://vaultenv-phi.vercel.app/cli.tgz
npx vaultenv@latest init

Links 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 build

Compiles every active environment into one Git-safe .env.vault for offline CI/CD.

npx vaultenv@latest rotate

Generates a fresh key, re-encrypts active environments client-side and revokes compromised tokens.

NO PLAINTEXT

The CLI is a thin client. It does the encryption locally, then treats the API as a dumb, encrypted locker.

§ 06 / THE DOCKET

The honest comparison.

Three tools solve the same problem differently. This is the narrowest honest read of the public docs.

Feature comparison between VaultEnv, EnvVault and Dotenv Vault
CapabilityVaultEnvEnvVaultDotenv Vault
Client-side AES-256-GCMYes, ciphertext onlyYesNo, server holds keys by default
Single-command npx workflowYes, npx or global installNoYes
Git-safe .env.vault artifactYes, offline decryptNoYes
Zero-disk runtime injectionYes, run -- <cmd>NoPartial
GitHub repo and branch syncYes, repo vaultsManual projectsManual projects
Team key wrapping and RBACYes, ECDH P-256YesServer-managed

Compiled from public documentation, November 2026. Check the current docs before you switch.

§ 07 / THE DESK

Three ways to hold the key.

All plans use the same cipher. Paid plans add room, not stronger encryption.

Hobby

For solo builders & prototypes

$0/ mo

One price, no seat maths

  • Up to 3 GitHub projects
  • Development, staging and production
  • 1 member (solo)
  • Version history: last 5 versions
  • Audit logs: 7 days
  • 2 CI/CD tokens
Create free account
ProMOST DISPATCHED

For shipping startups & indie studios

$12/ mo

One price, no seat maths

  • Unlimited GitHub projects
  • Unlimited custom environments
  • Up to 3 team members
  • Version history: 90-day retention
  • Audit logs: 90 days
  • Unlimited CI/CD tokens
Start with Pro
Team

For production engineering orgs

$29/ mo

Plus $5 per extra seat

  • Unlimited GitHub projects
  • Unlimited custom environments
  • Unlimited team seats and RBAC
  • Version history: unlimited retention
  • Audit logs: 365 days with JSON export
  • Unlimited CI/CD tokens with IP allowlist
Start with Team
SAME CIPHER ON EVERY PLAN

Dodo Payments checkout is ready; sandbox billing is active in this build. Prices in USD. Cancel anytime.

THE DISPATCH DESK / OPEN NOW

Seal it once.
Open it anywhere.

Start with three projects and one command. Invite the team when the repo goes live.

FREE FOREVER FOR SOLO PROJECTSNO CARDNO PLAINTEXT