openbao
v2.7.2 open-sourceThe section your link pointed to isn't on openbao's page any more, so we've brought you to the top.
OpenBao is a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys.
bao write ssh/roles/my-role allow_wildcards_in_identity_templates=true
export BAO_ADDR=https://bao.internal:8200
export BAO_CACERT=/etc/bao/ca.pem
export BAO_CLIENT_CERT=/etc/bao/client.crt
export BAO_CLIENT_KEY=/etc/bao/client.key
export BAO_MAX_RETRIES=3
bao proxy -config=/etc/bao/proxy.hcl
export BAO_PROXY_DISABLE_IDLE_CONNECTIONS=true
export BAO_PROXY_DISABLE_KEEP_ALIVES=true
bao proxy -config=/etc/bao/proxy.hcl
listener "tcp" {
address = "0.0.0.0:8200"
tls_cert_file = "/etc/openbao/tls/server.crt"
tls_key_file = "/etc/openbao/tls/server.key"
tls_key_exchange_preferences = "X25519MLKEM768,MLKEM1024"
}
curl -s -H "X-Vault-Token: $BAO_TOKEN" \
-H "X-Vault-Index: $WRITE_INDEX" \
-H "X-Vault-Inconsistent: await-state" \
https://openbao.example.com:8200/v1/secret/data/myapp
bao proxy -config=/etc/openbao/proxy-config.hcl -log-format=json -log-file=/var/log/openbao/proxy.log -log-rotate-bytes=104857600 -log-rotate-max-files=5
listener "tcp" {
address = "127.0.0.1:8200"
proxy_api {
enable_quit = true
}
}
curl -s -X POST http://127.0.0.1:8200/proxy/v1/quit
curl -X PATCH -H 'X-Vault-Token: ...' http://127.0.0.1:8200/v1/sys/policies/acl/my-policy -d '{"allow_wildcards_in_identity_templates": true}'
curl -X PATCH --header 'X-Vault-Token: ...' http://localhost:8200/v1/sys/namespaces/my-ns -d '{ "custom_metadata": null }'
bao plugin init registry.example.com/my-plugin:latest
bao operator validate-config /etc/openbao/config.hcl
PUT /v1/sys/config/audit
{
"unsafe_allow_api_audit_creation": true
}
PUT /v1/sys/config/audit
{
"allow_audit_log_prefixing": false
}
Summary
OpenBao is an open-source secrets management system, free to use, that stores and distributes credentials, certificates, and encryption keys for applications and infrastructure. It runs as a self-hosted service, deployed as a cluster that applications and operators talk to over an API, which makes it a fit for platform and infrastructure teams responsible for centralizing secrets access rather than for individual developers managing their own credentials. It is a fork of HashiCorp Vault, led under open-governance principles, and keeps that same role of storing and controlling access to sensitive data, now adding its own features such as namespace isolation with full lifecycle management, OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant.-based plugin distribution, and KMIP auto-unseal. Started in 2015 and currently carrying over 1,600 contributors with releases roughly every few weeks, including one 46 days ago, it is under active development.
OpenBao is a software solution to manage, store, and distribute sensitive data including secrets, certificates, and keys.
How openbao helps
Where are my applications getting their database credentials from, and can I stop handing out long-lived passwords?
mints short-lived credentials on demand through a database secret engine and revokes them when their lease expires, so no static password sits in a config file
What happens to my secrets if the machine holding them is compromised?
keeps all stored data encrypted with keys held only in memory after unseal, so a stolen disk or snapshot is unreadable without going through the running server
Which services can decrypt or read a given secret path, and who read or changed it last?
checks every request against the attached policy before releasing a secret and writes an audit record of who accessed or changed which path and when
How do I hand a build step a secret without exporting it into the environment or checking it into a repo?
lets a pipeline authenticate and fetch the value at run time through the client library, CLI, or proxy mode, so the secret exists only for the life of the step
Can I roll a signing key or certificate authority without redeploying every service that trusts it?
issues certificates dynamically through its key and certificate management engines, so trust rolls forward as services request new ones instead of pushing a shared file everywhere
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for openbao, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail openbao puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
36 entries
No entries match these filters.
- October 20263
- September 20266
- August 20262
- July 20266
- June 20265
- May 20263
- April 20261
- February 20261
- October 20251
- September 20251
- August 20252
- June 20251
- March 20251
- February 20251
- November 20241
- July 20241
Project health
Issue, contributor and maintainer activity in openbao/openbao, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 117 +35 vs prior 12 months
- Maintainers 9 +3 joined · −3 left, last 12 months
- Bus factor 3 committers behind half the commits
- Community-filed 76% of issues opened, last 12 months
- Median time to close 5 days first maintainer reply 10 hours
- Open backlog 243 of 877 issues ever filed
- Issues opened / month 11 · 3 communitymaintainers
- Open backlog 243
- Contributors / month 13
- Commits / month 68
- Stars 7,365
- bugs 45%
- features 29%
- docs 4%
- other 22%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 4, 2026Where openbao turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Attacks on openbao 1
-
A Realistic Code Execution Exploit Chain in OpenBao and Vault
This is the second-ever remote code execution vulnerability in Vault and OpenBao.
2 more quotes
There are two main takeaways from this post: This release fixed a number of critical vulnerabilities that have existed for years in OpenBao and Vault.
If you haven’t already patched to OpenBao v2.6.3 or 2.7.0, now is a good time to do so!
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.