Secrets Manager
github.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Secrets Manager is
Secrets Manager is a self-hosted system for storing encrypted application secrets, organizing them in a web interface, and passing them to processes through a CLI. Users can arrange secrets by organization, project, and environment, import .env files, edit or reveal values, keep versions, roll back, and soft-delete secrets. Its `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. Access grants can be scoped to users or service accounts at project or environment level, and a grant is required to reveal a value. The backend uses AES-256-GCM envelope encryption, and the documentation says plaintext secret values are not stored in the database. A user-generated master key is required before startup; losing it makes stored secrets unrecoverable. The project is free and open source under the MIT license. Deployment uses Docker Compose, with local Kubernetes manifests also provided. The CLI requires Node 20 or later. The maker warns that a real master key appeared in repository history before 2026-07-26; treat secrets encrypted with it as disclosed and follow the recovery steps.
Who it suits
It suits developers or teams seeking a self-hosted way to organize and inject application secrets. Its organization controls may help teams, while its stated MVP focus is a single developer’s first-run experience.
Good to know, and what to watch
- Secrets can be organized by project and environment
- CLI injects secrets without creating a .env file
- Revealing values requires an explicit access grant
- Secret versions can be rolled back
- Audit events include secret reveals
- Losing the user-generated master key makes secrets unrecoverable
- Quickstart requires Docker and Docker Compose
- CLI step requires Node 20 or later
- Maker warns that an earlier repository master key was exposed
Plans
Every plan and priceOpen-source self-hosted
Open source
The verdict
Secrets Manager provides self-hosted secret storage, access grants, versioning, and CLI injection without writing a .env file. Before setup, account for the required master key and follow the maker’s recovery guidance for secrets associated with the exposed repository key.
What the maker publishes
- Access controls
- Access can be granted to users and service accounts at project or environment scope, and revealing secret values requires an explicit grant. source
- Audit
- The system records audit events including secret reveals, and documents that secret values are not returned if the required audit write fails. source
- CLI
- The `secrets run` command fetches environment secrets and supplies them to a child process without creating a `.env` file. source
- CLI injection
- The `secrets run` CLI command injects an environment’s secrets into a child process and its children without creating a .env file. source
- Deployment
- Docker Compose starts PostgreSQL, Redis, the backend, and frontend; local Kubernetes manifests are also provided for a kind cluster. source
- Deployment requirements
- The quickstart requires Docker and Docker Compose, plus Node 20 or later for the CLI step. source
- Encryption
- 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. source
- Important security notice
- The maker says a real master key was published in the repository before 2026-07-26 and advises treating secrets encrypted with it as disclosed and following its recovery steps. source
- Integrations
- The documented CLI workflow uses Node.js and shows app commands for Node.js, Python, npm, and Next.js; CI or deployment can use `SECRETS_API_URL`, `SECRETS_TOKEN`, and `ENVIRONMENT_ID`. source
- Key requirement
- A user-generated master key is required before startup; losing it makes stored secrets unrecoverable. source
- License
- The repository identifies its license as MIT. source
- Master key requirement
- A user-generated master encryption key is required before startup, and the maker warns that losing it makes stored secrets unrecoverable. source
- MVP audience
- The project describes itself as an open-source MVP focused on a clean first-run experience for a single developer, with multi-user organizations, roles, and grants also available. source
- Organization
- Users can create organizations, projects, and environments to organize secrets for team projects. source
- Platforms
- The CLI documentation includes Windows PowerShell and macOS/Linux usage; the product also provides a browser UI and API. source
- Platform support
- The maker documents CLI support for Windows PowerShell and Command Prompt, and gives macOS/Linux command examples. source
- Product status
- The project’s README documents self-hosted Docker Compose deployment and does not list hosted plans or prices. source
- Purpose
- 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. source
- Secret history
- Secrets have versions that can be rolled back to earlier versions. source
- Secret management
- The UI supports importing .env files, editing and revealing secrets, keeping versions, rolling back, and soft-deleting secrets. source
- Security incident
- The maker says a real master key appeared in repository history before 2026-07-26 and warns that any key obtained from the repository before that date must never be used. source
- Support
- The repository directs vulnerability reports to a private GitHub security advisory and says not to disclose exploitable issues publicly. source
- Support channel
- The security policy asks users to report exploitable vulnerabilities through a private GitHub security advisory rather than a public issue. source
Checked against the maker's pages on 11 Oct 2026.