dotenvx vs OpenBao

dotenvx encrypts secrets stored in.env files, then decrypts and injects them when an application runs. Its maker describes it as free and open source, with hosted and self-hosted deployment options. Public-key encryption uses a secp256k1 key pair, keeping the private decryption key separate from the encrypted file. For development, the private key can be stored in the operating system’s secret store, including macOS Keychain, Windows Credential Manager, or Linux Secret Service. Listed workflow tools include environment selection and composition, validation, pre-commit leak prevention, Docker image protection, key/value operations, and runtime log redaction. The maker says encrypted files can travel with code and be decrypted at runtime using a private key supplied in the deployment environment, without a secrets service in the application’s critical path. Installation options include CLI, npm, winget, Homebrew, GitHub releases, Docker, a Ruby gem, and Python pip. Guides cover developer tools, programming languages, and deployment services. The free User plan includes CLI, SDKs, encryption, and GitHub Issues support. Member is $5 a month; Business is $90 a month. The paid product has a 14-day free trial.

OpenBao is a free, open-source system for storing and controlling access to secrets such as API tokens, encryption keys, passwords, and certificates. Management is available through a web UI, CLI, or HTTP API. Key/value secrets are encrypted before persistent storage, while dynamic credentials can be generated for Kubernetes and SQL databases and revoked when leases expire. Leases can be renewed, and individual secrets or groups can be revoked. OpenBao also encrypts and decrypts data without retaining it. Authentication methods include GitHub, LDAP, and AppRole, with token-based policies. Its storage barrier uses AES-256-GCM and verifies authentication tags during decryption. High-availability configurations are supported. Deployment options include packages, containers, binaries, source builds, and Helm; documentation covers Linux, macOS, FreeBSD, and Windows. Releases provide GPG signatures and SBOMs. Integrated Storage defaults to a 1 MiB maximum entry size, configurable with max_entry_size.