CLI-first secrets and config delivery for dev, staging, CI, and production.

Why EnvSync?

The problem: .env files are the #1 source of credential leaks. Teams share secrets via Slack DMs, email threads, and Google Docs. Each copy is a potential breach.

The solution: EnvSync provides a single source of truth for environment variables and secrets, with:

• 🔄 Point-in-time rollback — Undo any secret change to any previous state
• ✅ Approval workflows — Require review before production changes
• 🔐 End-to-end encryption — AES-256 at rest, TLS in transit
• 🚀 CLI-first workflow — envsync pull and envsync push in your terminal
• 🌐 28+ integrations — GitHub, GitLab, Vercel, AWS, and more

Quick Start

# Install CLI
curl -fsSL https://cli.envsync.cloud/install.sh | sh

# Login
envsync auth login

# Pull secrets
envsync pull --env development

# Push changes
envsync push --env staging

Architecture

One API process serves both product routes (/api/...) and, when Enterprise modules are enabled, manage routes (/api/v1/manage/{module}/...). There is no separate management API process or management SDK package.…