OpenBao
Foundation-governed secrets, key and certificate management with a customer-operated server.
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
OpenBao v2.7.3 auth and HA listener fixes
The release fixes auth alias case handling and corrects how HA request forwarding respects listener protections.
Scope: OpenBao v2.7.3 release notes name GHSA-fgmw-h9wp-wc7g and GHSA-h8fh-pmch-cjww. This review establishes the release-described fixes; it does not establish an independent published advisory record or a complete affected-version range.
Alias defaults apply to newly created auth mounts. Inspect case_sensitive_alias on existing mounts and test identity mappings. In HA deployments, review standby-to-active client-certificate forwarding, unauthenticated rekey/root endpoint restrictions and configured request limits.
Action: Apply v2.7.3 or a later compatible supported fix. Review each auth mount rather than assuming a new default reconfigures existing mounts; test authentication and forwarded requests against the configured listener protections.
Primary source · Upstream auth and listener security patch review · Reviewed 2026-11-20
What lands where
Supplied by
Vendor or project
Official binaries/containers or Helm chart; Akamai documents the full server on Linode Kubernetes Engine.
Runs in
Documented customer environment
Persistent secrets-server processes with durable storage, audit logs and optional HA clustering
- Linode: Customer cloud account
- Linode
Servers / containers
Operated by
Your team
Customer manages initialization, unseal/recovery keys, policy, TLS, durable storage, snapshots, audit logs and upgrades. Akamai operates LKE infrastructure; the customer operates the OpenBao service.
Deployment boundaries by provider
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Akamai full OpenBao server deployment on LKE ↗ · Source checked 2026-11-13
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official binaries/containers or Helm chart; Akamai documents the full server on Linode Kubernetes Engine. |
|---|---|
| Infrastructure | Servers / containers Persistent secrets-server processes with durable storage, audit logs and optional HA clustering. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements. |
| Licensing model | Open Source / Open Core The listed OpenBao core is MPL-2.0; separately distributed plugins and dependencies retain their own terms. It is not the commercially licensed HashiCorp Vault product. |
| License | MPL-2.0 core; dependencies and external plugins retain their licenses. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 5 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The JWT/OIDC auth method supports browser login through an OIDC provider from the UI or CLI. Configure roles, claims and token policies; downstream secret-consuming applications are separate clients.
OpenBao 2.7.x JWT/OIDC auth method · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The installation guide documents verifying release signatures and checksums, including the publisher workflow identity. This establishes an artifact-verification procedure, not a certification of the deployed service.
Upstream software supply-chain verification procedure · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The installation guide provides official packages/binaries and signature/checksum verification instructions. Configure server storage, TLS, initialization and recovery separately; a development-mode process is not a production service.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The Helm guide distinguishes demo, standalone and HA modes and warns that defaults target getting started. Current chart resources are empty; commented 250m CPU/256 MiB examples are not active production requirements. Whole-stack CPU/RAM/storage and HA sizing remain workload-dependent; do not import Vault sizing as an OpenBao guarantee.
Official chart guidance and actual values; numeric supported production baseline remains unconfirmed · Source ↗ · Official chart resource settings ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Mozilla Public License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
OpenBao v2.7.3 upstream source; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
OpenBao v2.7.3 includes release-described fixes identified as GHSA-fgmw-h9wp-wc7g and GHSA-h8fh-pmch-cjww: new auth-mount alias defaults and HA listener forwarding protections. Inspect existing mount settings separately and test the deployed HA configuration.
Upstream OpenBao server release; chart packages are versioned separately · Source ↗ · Upstream auth and listener security patch review ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Default standalone/file storage and development examples are not production HA configurations; follow the production checklist, configure TLS and test recovery. Cloud authentication and KMS unseal integrations do not imply additional hosting providers. OpenBao v2.7.3 corrects auth-alias handling and enforcement of listener settings when HA standbys forward requests to the active node. Newly created auth mounts use case-sensitive aliases by default. Review alias behavior and listener configuration when upgrading, and pin compatible server and chart versions. Inspect case_sensitive_alias on existing mounts rather than assuming the new default reconfigures them. HA review includes forwarded client certificates, unauthenticated rekey/root endpoint restrictions and request-size/duration limits.
Community & maintenance
OpenBao publishes an OpenSSF/Linux Foundation project structure, public TSC membership/governance and maintained releases. The reviewed 2.7.2 release includes security maintenance; governance and maintenance establish participation beyond inherited repository popularity.
Category fit
- Identity & access management
- Manages secrets, keys, certificates and policy-controlled access through a customer-operated service. Agent-only and external-server modes do not by themselves install that service.
Compare within Identity & access management
- authentikIdentity provider for centralized authentication and access policies across connected applications.
- AWS
- FusionAuth Self-HostedProprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Render
- HashiCorp Boundary EnterpriseCommercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
- AWS
- Azure
- Google Cloud
- Infisical Self-HostedSelf-hosted secrets-management platform with application and machine-identity access workflows.
- AWS
- Google Cloud
- Vultr
- Keycloak Self-HostedIdentity and access management for application sign-on, federation and authorization.
- AWS
- Azure
- NetBird Self-Hosted Community EditionOpen-source zero-trust networking control plane self-hosted on a customer cloud VM.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- DigitalOcean
- Hetzner
- OpenVPN Access ServerSelf-hosted business VPN and network-access server deployed in the customer's cloud account.
- AWS
- Azure
- Google Cloud
- Teleport Enterprise Self-HostedCommercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.
- AWS
- Azure
- Google Cloud
Showing 8 of 10 other listings in Identity & access management. These products address related workflows; read their category-fit notes before comparing scope. See all of Identity & access management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation distributions ↗openbao.org
- Helm modes and production responsibilities ↗openbao.org
- Akamai full OpenBao server deployment on LKE ↗www.akamai.com
- Exact upstream core license ↗github.com
- Public TSC governance ↗github.com
- Reviewed 2.7.2 maintenance release ↗github.com
- Foundation project and upstream source ↗github.com
- OpenBao v2.7.3 security release and behavior changes ↗github.com
- Auth-mount and HA listener security patch review ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Akamai full OpenBao server deployment on LKE ↗ · Linode
Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The provider guide creates an LKE cluster and installs, initializes and unseals the OpenBao server, then covers persistence, HA, TLS and access restrictions. It includes older illustrative chart output and standalone defaults; use supported pinned releases and production storage/TLS configuration, not development defaults.
- Akamai full OpenBao server deployment on LKE ↗ · Linode
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Public TSC governance ↗github.com
- Reviewed 2.7.2 maintenance release ↗github.com
- Foundation project and upstream source ↗github.com