Envy vs Secrets Manager
Envy
getenv.orgSecrets Manager
github.comSide by side
| Figure | Envy | Secrets Manager |
|---|---|---|
| Price from | $125/mo | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 3 | 1 |
| Spec score · Secrets Management Tools | 7.6 (#21) | 8.3 (#7) |
| Deployment | Envy runs on your own infrastructure using Docker Compose, with an API, web dashboard, and PostgreSQL. | Docker Compose starts PostgreSQL, Redis, the backend, and frontend; local Kubernetes manifests are also provided for a kind cluster. |
| Encryption | Secrets are encrypted on the client before they are sent, and the backend stores ciphertext rather than plaintext secret values. | The backend uses AES-256-GCM envelope encryption with a random data key per secret value, and the documentation says plaintext secret values are never stored in the database. |
| Purpose | Envy is self-hosted secrets management for engineering teams sharing secrets across environments and CI/CD pipelines. | Secrets Manager is a self-hosted system for storing application secrets encrypted, managing them in a web UI, and injecting them into processes through a CLI. |
| Support | Founding licenses include direct founder access, an onboarding call, deployment support, and a response within one business day. | The repository directs vulnerability reports to a private GitHub security advisory and says not to disclose exploitable issues publicly. |
Plans
In their own words
Secrets Manager
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.