Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content
OpenBao logo

OpenBao

Identity and Access Management (IAM)

Open Source
Self-hosted
E
Enterprise
OpenMSP Score
43
40
Reddit Impact Score
Github Score
389M
9KStars
707Forks
21KCommits
Mozilla Public License 2.0License
Nov 19, 2026Last commit
OpenBao is an open-source secrets, certificate, and key management platform forked from HashiCorp Vault. It was created after HashiCorp relicensed Vault under the Business Source License in August 2023; community members forked the last MPL-licensed Vault codebase in December 2023, and the project joined the Linux Foundation, reaching a stable 2.0 release around April 2024. Governance is vendor-neutral, with maintainers from SAP, GitLab, ControlPlane, Adfinis, IBM, and others rather than a single controlling company. OpenBao centralizes sensitive data behind a unified API and ACL/policy system: it encrypts key-value secrets before persisting them, issues dynamic short-lived credentials for databases and cloud providers, provides "encryption as a service" via its Transit engine, and offers a full PKI engine for certificate issuance and rotation. It has also added KMIP server support and open-sourced namespaces (multi-tenant isolation) - a feature Vault keeps enterprise-only. OpenBao is licensed under the Mozilla Public License 2.0 (MPL-2.0), a genuine OSI-approved open-source license. Adoption is growing among privacy- and cost-conscious organizations, with an active GitHub community and roughly monthly releases.
image media

Key Features

Dynamic Secrets

Generates short-lived, on-demand credentials for databases, cloud providers, and other systems, auto-revoked at lease expiry.

KV Secrets Engine

Encrypted key-value secret storage with versioning, mounted at arbitrary paths.

PKI Secrets Engine

Issues and manages X.509 certificates, acting as an internal or intermediate CA with automated rotation.

Transit (Encryption as a Service)

Encrypts/decrypts/signs application data centrally without OpenBao ever storing the plaintext or ciphertext.

KMIP Secrets Engine

Acts as a KMIP server so KMIP-compliant devices/appliances can manage keys through OpenBao.

Open-Source Namespaces

Secure multi-tenancy with tenant isolation and delegated administration, included free unlike Vault where this is enterprise-only.

Pros and Cons

Pros

Fully Open Source, No BUSL Risk

MPL-2.0 licensed with no source-available restrictions or future relicensing threat from a single vendor.

Enterprise Features Included Free

Namespaces/multi-tenancy and KMIP, which are paywalled in Vault, ship in the open-source build.

Vault API/Workflow Compatibility

Close API and CLI parity with Vault eases migration for teams already using Vault tooling and Terraform providers.

Vendor-Neutral Governance

Linux Foundation stewardship with a multi-company maintainer base reduces single-vendor lock-in risk.

Active, Fast-Moving Development

Frequent releases (roughly monthly) and a responsive community/issue tracker.

Cons

Younger Project, Less Battle-Tested

Despite inheriting Vault's codebase, OpenBao has been an independent project only since late 2023 (v2.7 in October 2026)

Smaller Ecosystem Than Vault

Fewer third-party integrations, less mature CI tooling, and a smaller pool of experienced practitioners.

No Official Managed Cloud/SaaS

Unlike HCP Vault, there is no first-party hosted SaaS; MSPs must self-host or rely on third-party managed offerings.

Commercial Support Still Consolidating

Enterprise support is only just emerging (e.g., ControlPlane), so SLAs and long-term roadmaps are less proven than incumbents.

Migration Friction From Vault Enterprise

Organizations relying on Vault Enterprise-only features beyond namespaces may face gaps before switching.

Feature Comparison

Features
Cost and Licensing
Loading the comparison

Comments

No reviews yet. Be the first to share your experience with OpenBao.

Frequently Asked Questions

/vendor/openbao