Chamber vs Teller
Chamber
github.comTeller
github.comSide by side
| Figure | Chamber | Teller |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 1 |
| Spec score · Secrets Management Tools | 8.2 (#8) | 7.3 (#27) |
| License | The project is licensed under the MIT License. | The GitHub repository identifies the project as Apache-2.0 licensed. |
| Purpose | Chamber is a local-first secrets manager for passwords, API keys, certificates, database credentials, and other sensitive information. | Teller is an open-source secret manager for developers working with secrets while developing, testing, and building apps. |
Plans
In their own words
Teller
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.