OpenBao vs secr

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.

secr manages secrets and non-human identities for development teams, with a cloud service and a CLI that injects secrets directly into a process instead of requiring them in.env files. Teams can separate development, staging, and production secrets, compare or promote environments, and apply role-based permissions by environment. A scanner detects 20+ credential patterns and can install a pre-commit hook to block leaks before they reach git. AI agents can use scoped credentials, secret allowlists, and conditional access policies. Integrations include development tools, approval channels, cloud platforms, and SDKs for Node.js, Python, and Go. The Free plan costs nothing and includes 3 projects, 100 secrets, 1 AI agent, and a 7-day audit log. Pro is $6 a month and Team is $14 a month, each with a 14-day trial. Enterprise pricing is custom. The security page calls its SOC 2 control mapping a self-assessment; formal Type II certification is on its roadmap.