Oracle Cloud Infrastructure Secret Management vs Teller

Oracle Cloud Infrastructure Secret Management stores, retrieves, rotates, and manages credentials used by applications and cloud environments. It supports database passwords, access tokens, third-party API keys, SSH private keys, application configuration secrets, and OAuth2 or JWT signing credentials. Administrators and applications can access secrets through APIs, SDKs, the CLI, and OCI Console. OCI Vault keys encrypt secrets, while OCI manages encryption, decryption, access control, and audit logging; OCI IAM policies provide granular permissions. Automatic rotation can run at intervals from one to 12 months and integrates with Autonomous AI Database and OCI Functions. Secrets can be replicated to as many as three destination regions, where replicas are read-only and inherit changes from the source. A tenancy can contain up to 5,000 secrets, with up to 30 active versions and 30 versions pending deletion per secret. The service is aimed at applications and cloud environments that need centrally managed secrets rather than credentials embedded in source code or configuration files. It is listed as free, though no price is provided.

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.