Secrets Manager vs Teller

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.

Teller is a free, Apache-2.0 open-source secret manager for developers working with secrets during development, testing, and app builds. It connects to vaults, key stores, and cloud services for personal environments or team workflows. Named integrations include HashiCorp Vault, AWS Secrets Manager, Google Secret Manager, HashiCorp Consul, AWS SSM, dotenv, etcd, and an in-memory store. The `teller run` command can start a subprocess with fetched variables, while `teller env` can provide a Docker `--env-file`. Teller can scan code for secrets and return exit code 1 in CI when run with `--error-if-found`. It can also redact secrets from process output, logs, live log tails, and files. Provider mappings can specify a root path, mapping ID, and key renames; configuration templates can use environment variables. The project offers release binaries and source installation with `cargo install --path .`. Write operations are available only through providers that support them.