Envshed vs Secrets Manager

Envshed is a cloud secrets manager for small engineering teams, with a CLI that works across monorepos. It manages secrets and environments, supports per-user overrides, warns about expirations, allows project duplication and keeps an audit trail. For pnpm or npm workspaces, the CLI can detect workspaces and retrieve secrets from the repository root. Listed integrations include GitHub Actions, Docker, a Node.js SDK, a CLI for any shell and Coolify; a REST API supports languages including Python, Go and Rust. Secret values are encrypted at rest with AES-256-GCM, traffic uses TLS 1.3, and encryption keys are held separately from encrypted data. Envshed offers role-based access control and an immutable audit trail, including records of secret reads and changes. The maker says it is not a zero-knowledge vault: a small on-call group with production credentials could technically decrypt a secret value. Data is stored in one region on US-based cloud infrastructure. Self-hosting is unavailable, and the service is not yet SOC 2 or ISO 27001 certified. The Developer plan is free forever for up to two members and three projects; Team is $5/user/month and Business is $9/user/month.

Secrets Manager is a free, open-source, self-hosted system for storing application secrets in encrypted form, managing them through a web interface, and injecting them into processes with a command-line tool. Users organize secrets by organization, project, and environment, import.env files, edit or reveal values, keep versions, roll back, and soft-delete entries. The `secrets run` command supplies environment secrets to a child process and its descendants without creating a.env file. Documented workflows cover Node.js, Python, npm, and Next.js; CI or deployment can use an API URL, token, and environment ID. User and service-account grants can be scoped to projects or environments, and revealing values requires explicit permission. AES-256-GCM envelope encryption uses a separate data key per value, while plaintext values are not stored in the database. Audit events include secret reveals, and values are withheld if audit writing fails. Docker Compose starts PostgreSQL, Redis, backend, and frontend; local Kubernetes manifests are also provided. A user-generated master key is mandatory and lost keys make secrets unrecoverable. The repository is MIT licensed.