Keyway vs Secrets Manager
Keyway
keyway.shSecrets Manager
github.comSide by side
| Figure | Keyway | Secrets Manager |
|---|---|---|
| Price from | €9/mo | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 4 | 1 |
| Spec score · Secrets Management Tools | 7.9 (#16) | 8.3 (#7) |
| CLI | The keyway run command injects secrets into a process, and the secrets disappear when that process stops. | The `secrets run` command fetches environment secrets and supplies them to a child process without creating a `.env` file. |
| Encryption | Secrets are encrypted with AES-256-GCM, using a unique random IV for each secret. | 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. |
| Integrations | The documented available provider integrations are Vercel, Netlify, and Railway, with workflows to sync secrets. | 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`. |
| Purpose | Keyway is an open-source secrets manager that injects environment variables into process memory so they are not stored in a project .env file. | 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 | The Business plan includes priority support, and Keyway lists [email protected] as its contact email. | The repository directs vulnerability reports to a private GitHub security advisory and says not to disclose exploitable issues publicly. |
Plans
In their own words
Keyway
Keyway is an open-source secrets manager that injects environment variables into a running process instead of storing them in a project.env file. Its `keyway run` command makes secrets available while that process runs; they disappear when it stops. Keyway says AI agents reading files from disk cannot see secrets injected this way. Access follows GitHub repository permissions, so removing a person’s repository access also revokes their Keyway access.
Secrets use AES-256-GCM encryption with a unique random IV for each secret. An isolated crypto service holds the encryption key, which Keyway says does not touch its API server or database; connections among the CLI, API, crypto service, and database use TLS 1.3. An audit trail records who accessed which secrets, when, and from where. Documented provider workflows cover Vercel, Netlify, and Railway. CLI binaries are listed for macOS, Linux, and Windows, and the full stack can be self-hosted with Docker Compose. The Free plan includes unlimited public repositories, one private repository, three environments per repository, two provider integrations, and unlimited collaborators. Paid plans are Pro at €9 a month, Team at €19 a month, and Business at €39 a month.
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.