Envshed vs Teller

Envshed is a cloud secrets manager for small engineering teams, with a CLI that works across monorepos. It manages secrets and environments, supports per-user overrides, warns about expirations, allows project duplication and keeps an audit trail. For pnpm or npm workspaces, the CLI can detect workspaces and retrieve secrets from the repository root. Listed integrations include GitHub Actions, Docker, a Node.js SDK, a CLI for any shell and Coolify; a REST API supports languages including Python, Go and Rust. Secret values are encrypted at rest with AES-256-GCM, traffic uses TLS 1.3, and encryption keys are held separately from encrypted data. Envshed offers role-based access control and an immutable audit trail, including records of secret reads and changes. The maker says it is not a zero-knowledge vault: a small on-call group with production credentials could technically decrypt a secret value. Data is stored in one region on US-based cloud infrastructure. Self-hosting is unavailable, and the service is not yet SOC 2 or ISO 27001 certified. The Developer plan is free forever for up to two members and three projects; Team is $5/user/month and Business is $9/user/month.

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.