Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/openbao/openbao (opens in new tab) · github.com/hashicorp/vault (opens in new tab)
Pick OpenBao
If you want a Vault-style secrets manager under MPL-2.0 with open governance, namespaces in the docs and a direct path out of Vault Community Edition.
Pick Vault
If you want HashiCorp's own distribution, need something from its Enterprise list such as replication or HSM support and will buy it, or already standardise on Vault and its Business Source terms are acceptable for your own use.
OpenBao and HashiCorp Vault are close relatives: OpenBao is the community fork of Vault, and both are API-driven secrets managers that start sealed, hand out tokens tied to policies, and can generate short-lived credentials on demand. The difference you will feel first is the licence. Vault's source is under the Business Source License from 1.15.0 on, while OpenBao is MPL-2.0 under the Linux Foundation. If you are choosing between them for a VPS, the day-to-day experience is similar. What changes is who controls the project and which features sit behind a paid edition. For a developer-facing alternative with a dashboard instead of policies, see Infisical vs OpenBao.
Vault is HashiCorp's secrets manager. Its README lists the core ideas: "Secure Secret Storage", "Dynamic Secrets" ("Vault can generate secrets on-demand for some systems, such as AWS or SQL databases"), "Data Encryption" ("Vault can encrypt and decrypt data without storing it"), "Leasing and Renewal" and "Revocation". Clients authenticate through an auth method (AppRole, Kubernetes, JWT/OIDC, LDAP, AWS, GitHub and more) and receive a token and policies.
OpenBao describes itself as "a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys." It is a Vault fork, kept under open governance, and aims for API compatibility, so existing Vault clients should keep working. Its docs reuse Vault's vocabulary: secrets engines, auth methods, leases, transit encryption, namespaces.
In August 2023 HashiCorp announced that future releases of its products would move from MPL 2.0 to the Business Source License v1.1, saying copying, modifying and redistributing stay allowed "except where providing a competitive offering to HashiCorp." The Vault licence file names "Vault Version 1.15.0 or later" as the licensed work. Its Additional Use Grant lets you "make production use of the Licensed Work", provided you are not "offering the Licensed Work to third parties on a hosted or embedded basis in order to compete" with IBM's paid versions. The change licence is MPL 2.0, "Four years from the date the Licensed Work is published."
For most self-hosters running Vault for their own services, that grant is enough, and BSL does not change how the software runs. It matters if you plan to build a hosted or embedded product around it, or if your organisation only approves OSI-style licences. OpenBao exists for the second case: an Open Horizon project chair told TechTarget that "Linux Foundation projects cannot embed BSL-licensed code" and that the alternative was to "fork an earlier MPL-licensed branch of Vault". OpenBao's repository carries the Mozilla Public License 2.0.
Vault has an Enterprise edition, and its docs group a long list of features under "Vault Enterprise": replication, performance standby nodes, namespaces, HSM support and the PKCS11 provider, control groups and policies as code among them. The namespaces page says an "Appropriate Vault Enterprise license or HCP Vault Dedicated cluster" is required. Some auth methods, such as SAML, are marked Enterprise on the auth page.
OpenBao documents namespaces too, for the same multi-tenant use. Do not assume the rest of Vault's Enterprise list carries over: check each feature you rely on (replication and HSM support, for example) in OpenBao's docs first. Its migration guide is explicit about the limits: "OpenBao makes no guarantees about storage compatibility with Vault", the in-place procedure was tested against one older Vault Community release with Shamir unseal, newer Vault versions are untested, and mounts whose plugins OpenBao does not ship are skipped at startup.
Both start sealed. Vault's docs say "the default Vault configuration uses an algorithm known as Shamir's Secret Sharing", with a threshold of shares needed to rebuild the unseal key. OpenBao's docs say the same of its default: "The default OpenBao config uses a Shamir seal." Both offer auto unseal through a cloud KMS or another trusted service; Vault's docs say it "aids in reducing the operational complexity of keeping the unseal key secure". Vault marks seal high availability and seal wrapping as Enterprise features.
Storage is where our installs differ. Our Vault snippet uses the file backend
on a named volume, which Vault's docs describe as suited to "durable single
server situations" and which "does not support high availability". Our OpenBao
snippet uses integrated Raft storage, which is the route to a cluster. Both
snippets run plain HTTP and set disable_mlock, so put TLS in front before
real use, and move the root token and unseal keys offline after
operator init.
On a GCP e2-standard-2 (Ubuntu 26.04), idle at first boot with our install snippet and no secrets loaded, OpenBao used ~20 MB of RAM and ~295 MB of disk (September 2026), and Vault used ~23 MB of RAM and ~731 MB of disk (November 2026). That is an idle first-boot reading, not a load test. The RAM gap is small. Our RAM floors (256 MB for OpenBao, 512 MB for Vault) are estimates.
Both are rated 3 out of 5 on our scale: one container, but a sealed-by-default service where you must initialise, store the unseal keys safely, write policies and add TLS before it is useful.
Choose OpenBao if you want a Vault-style secrets manager under MPL-2.0 with open governance, you want namespaces without a licence, or you are leaving Vault Community Edition and want the closest open-source path.
Choose Vault if you want HashiCorp's own distribution and documentation, you need something from the Enterprise list and will buy it, or your environment already standardises on Vault and its BSL terms are acceptable for internal use.
Both installs are verified on Ubuntu 26.04; see the OpenBao
and Vault pages for the pinned snippets. Back up the data volume
(openbao-data or vault_data) and keep the unseal keys and root token somewhere that does not
live on the same server.
OpenBao lists a lower minimum: 256 MB vs 512 MB for HashiCorp Vault.
No. OpenBao is MPL-2.0, HashiCorp Vault is BSL-1.1.
OpenBao if you want the Vault model under MPL-2.0, open governance and no paid edition to wonder about. Vault if you want HashiCorp's own build or need its Enterprise features. For one team's own services either works: both idled at ~20 MB and ~23 MB of RAM in our first-boot checks, which is not a load test.
Its migration guide says the API "should be compatible with Vault to the extent that existing clients should not even register a difference", but it also warns "OpenBao makes no guarantees about storage compatibility with Vault", was tested only from an older Vault Community release, and skips mounts whose plugins OpenBao does not ship. Test your plugins and mounts before switching.
Mostly yes. Vault 1.15.0 and later is under the Business Source License 1.1, whose Additional Use Grant allows production use unless you offer it to third parties on a hosted or embedded basis to compete with IBM's paid versions. Each release converts to MPL 2.0 four years after publication. Enterprise features need a paid licence.
HashiCorp moved future releases from MPL 2.0 to the Business Source License in August 2023. An Open Horizon project chair told TechTarget that Linux Foundation projects cannot embed BSL-licensed code, so the community forked an earlier MPL-licensed branch of Vault.
Paid link — we earn a commission if you shop through it.
A developer dashboard on PostgreSQL and Redis with an MIT core, or an API-first, sealed-by-default secrets engine under the Business Source License.
The developer secrets dashboard vs. the open-source Vault fork.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.