Environment variable syncing, diffing, and secret rotation — with secret-store integrations.

⭐ Star this repo if you manage environment variables — it helps other developers find Envault!

Why Envault? Managing .env files across dev, staging, and prod is error-prone — copy-pasting secrets between environments, accidentally committing .env to git, rotating keys by hand across 5 files. Envault encrypts your .env files with a single master key, syncs them across environments, and rotates secrets without touching a text editor. One envault push encrypts and deploys. One envault pull decrypts and loads. No more plaintext secrets in .git history.

Note: rh-envault is not yet published to PyPI. Install directly from GitHub.

pip install git+https://github.com/Coding-Dev-Tools/envault.git

# Initialize a project
rh-envault init my-project

# Diff environments
rh-envault diff dev prod

# Sync staging → prod
rh-envault sync staging prod

# Rotate a secret
rh-envault rotate DB_PASSWORD

Initialize a .envault.yml config file with sensible defaults.

rh-envault init my-project

Diff environment variables between two environments or .env files. Shows keys that are:

• Only in source
• Only in target
• Present in both but with different values

rh-envault diff dev staging
rh-envault diff prod staging
rh-envault diff-files .env.dev .env.prod

Sync environment variables from one environment to another with conflict resolution strategies.

# Sync staging → prod (source values win conflicts)
rh-envault sync staging prod

# Dry run first
rh-envault sync staging prod --dry-run

# Keep target values on conflict
rh-envault sync staging prod --strategy target_wins

# Delete keys in target that don't exist in source
rh-envault sync staging prod --allow-delete

# Skip certain keys
rh-envault sync staging prod --skip DB_HOST --skip DB_PORT

Rotate a single environment variable with an auto-generated cryptographically secure value.

rh-envault rotate DB_PASSWORD
rh-envault rotate API_KEY --env prod
rh-envault rotate JWT_SECRET --length 64 --dry-run --show
rh-envault rotate-all --env prod

Smart rotation infers the type of secret:

• DB_PASSWORD, DATABASE_URL → database-safe password (no ambiguous chars)
• API_KEY, STRIPE_SECRET → prefixed API key
• JWT_SECRET → 256-bit base64 secret
• WEBHOOK_SECRET → long hex key
• Everything else → 32-char random string

Manage secret store integrations — read, write, and list secrets from external stores.

rh-envault store list
rh-envault store list --prefix /production/
rh-envault store get DB_PASSWORD --store my-vault
rh-envault store set DB_PASSWORD new_value --store my-vault
rh-envault store delete DB_PASSWORD --store my-vault

Expose decrypted secrets as an HTTP JSON API — perfect for MCP servers, CI/CD sidecars, and AI agent runtimes.

# Start the secrets API on port 8080
rh-envault serve --port 8080

# Custom host and password
rh-envault serve --host 0.0.0.0 --port 3000 --password your-master-key --api-token my-token

Endpoints:

• GET /health — store connectivity check (no auth required)
• GET /auth/info — discover configured authentication methods (no auth required)
• GET /secrets — list all secret keys, optional ?prefix=X filter (auth required)
• GET /secrets/{key} — get decrypted value for a key (auth required)

Authentication: set --api-token or ENVAULT_API_TOKEN for Authorization: Bearer <token>, or set --api-key or ENVAULT_API_KEY for X-API-Key: <key>. API credentials are separate from the encryption password. Without credentials, secrets routes are unauthenticated and binding is limited to localhost.

# List all secrets
curl -H "Authorization: Bearer my-token" http://localhost:8080/secrets

# Filter by prefix
curl -H "Authorization: Bearer my-token" "http://localhost:8080/secrets?prefix=STRIPE"

# Get a specific secret
curl -H "Authorization: Bearer my-token" http://localhost:8080/secrets/DB_PASSWORD

View the audit log of all diff, sync, and rotate operations.

rh-envault audit
rh-envault audit --key DB_PASSWORD
rh-envault audit --action rotate --limit 100

Start an HTTP server that exposes decrypted secrets as a JSON API — ideal for MCP server sidecars, CI/CD pipelines, and AI agent runtimes.

# Start the secrets API on port 8080 (default)
rh-envault serve

# Custom port, host, and API key
rh-envault serve --port 3000 --host 0.0.0.0 --api-key my-api-key

# Use a named store from config
rh-envault serve --store production-secrets

Endpoints:

Security:

• Defaults to 127.0.0.1 (localhost only) — use --host 0.0.0.0 only behind a firewall or reverse proxy
• Set --api-key or ENVAULT_API_KEY for X-API-Key authentication, or --api-token or ENVAULT_API_TOKEN for Bearer authentication on /secrets endpoints
• Without API credentials, secrets endpoints are unauthenticated and binding is limited to localhost
• No built-in TLS — run behind a reverse proxy (nginx, Caddy) for HTTPS in production

# Fetch secrets with curl
curl -H "X-API-Key: my-api-key" http://localhost:8080/secrets

# Filter by prefix
curl -H "X-API-Key: my-api-key" "http://localhost:8080/secrets?prefix=STRIPE"

# Get a specific secret
curl -H "X-API-Key: my-api-key" http://localhost:8080/secrets/DB_PASSWORD

• Environment diffing — compare variables between any two environments with colorized output
• Conflict resolution — choose source-wins, target-wins, or interactive merge strategies
• Smart secret rotation — auto-detects secret type (DB password, API key, JWT, webhook) and generates appropriate values
• Bulk rotation — rotate-all with per-key dry-run preview
• HTTP secrets API — serve command exposes decrypted secrets as a JSON REST API with Bearer token auth
• Secret store integration — AWS SSM, HashiCorp Vault, Doppler, 1Password
• Secrets HTTP API — serve exposes decrypted secrets over HTTP with Bearer token auth for MCP sidecars, CI/CD, and agent runtimes
• Audit trail — every operation logged to .envault-audit.log with queryable CLI
• Configuration as code — .envault.yml is team-shareable and Git-friendly

Envault is one of 11 tools in the Revenue Holdings suite. One license covers all CLI tools.

🔹 No lock-in: CLI works fully offline on the free tier — no telemetry, no phone-home. 🔹 Annual billing: Save 20%.

_{Part of Revenue Holdings — CLI tools built by autonomous AI.}

Create a .envault.yml file in your project root:

project: my-app
version: '1'

environments:
  - name: dev
    env_file: .env.dev
  - name: staging
    env_file: .env.staging
  - name: prod
    env_file: .env.prod

stores:
  production-secrets:
    type: aws-ssm
    path_prefix: /my-app/prod
  vault:
    type: vault
    url: https://vault.example.com:8200
    token_env_var: VAULT_TOKEN
    path_prefix: my-app/prod

audit_log_path: .envault-audit.log

# Block deployment if production has secrets that staging doesn't
rh-envault diff staging prod --fail-on-missing

# Rotate a secret and sync to all environments
rh-envault rotate DB_PASSWORD --env staging
rh-envault sync staging prod

# Audit before deployment
rh-envault audit --action rotate --limit 20

Configuration and audit logs are stored in the project root and ~/.envault/:

• .envault.yml — project configuration (Git-friendly)
• .envault-audit.log — audit trail (append-only)

• Interactive merge for conflict resolution
• Vault OIDC auth
• GitOps mode — sync from Git-based config repos
• MCP server for AI-assisted env management → envault serve (HTTP API, see above)
• Docker-based CLI image
• Terraform provider for secret provisioning

MIT — see LICENSE

_{Part of Revenue Holdings — a suite of 11 developer CLI tools built by autonomous AI agents. Also check out API Contract Guardian (breaking change detection), DeployDiff (infrastructure diffs), json2sql (JSON → SQL), ConfigDrift (config drift detection), DeadCode (dead code cleanup), APIAuth (API key management), APIGhost (mock API server), SchemaForge (ORM converter), click-to-mcp (CLI → MCP server), and DataMorph (data format conversion).}

npm install

npm test  # runs: node --test tests/