Updated 2026-11-13
Self-hosted secrets: your vault is sealed after every reboot
Short answer: the category is already served. Vault, OpenBao, Infisical, Doppler, SOPS and Bitwarden all exist and all work. The one gap they share is the one this thread is actually about: after a reboot, a sealed store cannot serve secrets, and every app that depends on it fails to start until a human supplies the unseal keys. Nobody sells a self-hosted setup that survives an unattended reboot without giving the keys to the machine. That is a narrow, defensible product, and it is a hard one.
🔥 Heat 196.64
1 evidence post
3 pain points
2026-11-13
Mention 1 · 1 source🔥 Surging
At a glance
Who asks
Self-hosters running 3 to 10 boxes
Docker Compose, a CI pipeline, a handful of services that all need credentials.
What they pay today
$0 to $21 per user
Vault and OpenBao free. Doppler free for 3 users, then $21 per user.
First revenue
Slow, and only via hosting
This audience self-hosts to avoid paying. Managed hosting is the real market.
Cost to build v1
2 to 3 weeks
TPM-backed auto-unseal plus packaging, not a new secret store.
Up against
6 established tools
Vault, OpenBao, Infisical, Doppler, SOPS, Bitwarden Secrets Manager.
Ceiling
Low, with one honest exception
Managed hosting for people who tried and gave up.
Sources: Doppler and AWS Secrets Manager pricing via Dupple, 2026-06-16, and Toolradar, 2026-11-04. Vault and OpenBao free tiers are open source.
What one self-hoster actually said
“There are .env files on a few different hosts, some passwords pasted straight into compose files, tokens sitting in CI variables, and a password manager note I'm not proud of.”
This is the starting state for most homelabs. Not one bad practice, five of them, accumulated over years because each one was the fastest thing available at the time.
“Every time I rotate something I forget at least one place.”
Rotation is where scattered secrets turn dangerous. The old value stays live in whichever location got forgotten, and nothing tells you which one it was.
“What I actually want is pretty simple: one place per environment, some history so I can undo a bad change, tokens for CI that expire on their own, and something that doesn't need babysitting.”
That last clause is the whole design brief. Every requirement before it is already met by existing tools. "Doesn't need babysitting" is the one nobody ships.
Why now
1. Vault's license changed and the fork is now hosted by a foundation
On 10 August 2023 HashiCorp moved its whole portfolio, Vault included, from MPL 2.0 to the Business Source License. The code stayed visible and the usage became restricted. OpenBao started later that year as the open continuation, kept API compatibility, and now runs under the Linux Foundation's OpenSSF. One detail from OpenBao's own talks is worth knowing: IBM was among the main forces behind the fork, because Open Horizon depended on Vault and the license change put that dependency at risk.
The practical result is two ecosystems where there used to be one, and neither of them has solved unsealing.
OpenBao, OSSNA 2026 talk and Siemens open source day 2026; SHPV, 2026-06-29, on the 10 August 2023 relicense.
2. The vendor documents the problem itself
Vault's own documentation says unsealing makes automating an install difficult, and notes that a restart seals the server. This is not a rumor from a frustrated user. It is the security model working as designed: the root key lives in memory only, so a reboot destroys it. OpenBao inherited the same behavior, with Shamir shares at 3 of 5 by default. When the store is sealed, apps that fetch secrets at startup simply fail, and systemd retries them until someone walks over and supplies the keys.
Vault developer docs on seal and unseal; SSD Nodes, 2026-10-27, describing the OpenBao reboot failure mode.
3. Managed options got good enough to be the default
Doppler at $21 per user is expensive for a homelab but trivial for a small company, and Infisical positions itself as working out of the box. The people who remain unserved are precisely the ones who refuse both: they will not pay per seat, and they will not accept a cloud dependency for the keys to their own machines.
The gap: unseal is a security trade dressed up as an operational one
Line up the tools by how they handle a reboot, and the empty cell is visible.
- Vault and OpenBao: sealed on restart, manual unseal with Shamir shares, or auto-unseal against a cloud KMS or HSM. Free, powerful, and the reboot is yours to handle.
- Infisical and Doppler: hosted, so the reboot problem belongs to the vendor. Priced per seat, which is the thing this audience is trying to escape.
- SOPS plus age: files encrypted at rest, no server to seal. Works until you need rotation, history or per-environment scoping, at which point you are building a secret manager in shell scripts.
- Bitwarden Secrets Manager: open source, client-side encryption, self-hosting only on enterprise plans. Good for teams already inside Bitwarden, awkward for a homelab.
- AWS Secrets Manager: $0.40 per secret per month, and a hard dependency on AWS for the keys to your own hardware. Wrong shape for this buyer.
Why the cell stayed empty
Because filling it requires a contradiction. A store that unseals itself after a reboot must keep the means to unseal somewhere the machine can reach, which means an attacker with root on that machine can also reach it. The security guarantee weakens by exactly the amount the convenience improves.
There is one honest way through: bind the unseal key to hardware the attacker cannot copy, meaning a TPM 2.0 measured boot chain, so the key releases only to the same firmware and OS image that was running when it was sealed. That is real, it is narrower than a cloud KMS, and almost nobody packages it for a single-box homelab. The gap is not "a lighter Vault." The gap is "unseal that survives a reboot without handing the key to a text file."
Reasons to build
- The requirement is stated verbatim in the request. "Doesn't need babysitting" is not an inference from the thread, it is the sentence the user wrote. The existing tools meet every other clause and miss this one.
- The TPM path is real and undersold. Plenty of homelab hardware already has a TPM 2.0 module, and OpenBao's auto-unseal already supports pluggable seals. What is missing is packaging, not capability.
- The audience is small but unusually loud. Self-hosters write about their setups, file detailed issues, and recommend tools to each other. A working solution spreads without paid acquisition.
- Every incumbent has a reason not to build it. Vault and OpenBao treat manual unseal as a security feature. Hosted vendors solve it by taking the server away, which is the thing this buyer rejects.
Reasons not to build
- The audience does not pay, by definition. People self-host to avoid subscriptions. Doppler's $21 per user is not competing with you, it is the thing that pushed this buyer toward self-hosting in the first place. Expecting them to pay for a self-hosted tool is a category error.
- You are weakening the security property you are selling. Any auto-unseal scheme makes the key reachable to the host. If your product page does not lead with that trade-off, you are selling something you cannot deliver, and a security audience will find out fast.
- Two foundations and a large vendor own the roadmap. OpenBao has foundation backing and Vault has HashiCorp engineering. A solo maintainer building on the same API inherits every breaking change and competes for the same users.
- The adjacent products are genuinely good. Infisical is polished, Bitwarden is trusted, SOPS is simple. The gap is real but narrow, and narrow gaps are easy to close by accident when a bigger project ships a feature.
If you build it anyway
Do not build a new secret store. Build a deployment target. Ship OpenBao, unchanged, with three things the upstream documentation leaves to the reader: a TPM-backed auto-unseal configuration that works on a single box, a health check that proves the store came back sealed or not, and a documented statement of what security you gave up to get the reboot behavior.
Package as a Compose file plus an install script. The first version fits in a repository and a README. The honest selling line is the trade-off, written in the README, not hidden in it.
What you would charge
- The repository is free. Charging for a Compose file in a community that expects free configs will get you ignored, and the config is the part that earns trust.
- $5 to $10 a month for a managed instance. This is the only durable revenue in the category: the people who tried self-hosting, hit the unseal wall, and would rather pay than debug a TPM.
- No per-seat pricing. The whole point of the target audience is avoiding per-seat billing. Copying Doppler's model copies the reason they left.
Napkin math
Assumptions, and the second one is the whole argument.
- A repository that solves TPM auto-unseal draws 400 stars in year one and roughly 1,500 monthly visitors (assumption).
- Conversion from visitor to $8 managed instance: 1 percent, or 15 paying customers.
- Monthly revenue: $120. Annual: $1,440, before hosting costs for those instances.
Hosting 15 instances costs real money and real uptime responsibility. At this scale the managed tier is a break-even courtesy, not a business. The repository is the asset. Build it for the reputation, and treat any revenue as a rounding error.
Evidence (1 post)
r/selfhosted, 2026-11-09. The quotes above are from that thread. The technical claims about unsealing come from Vault and OpenBao documentation, cited inline.
FAQ
Why is my vault sealed after a reboot?
By design. Vault and OpenBao keep the root key in memory only, so a restart destroys it and the server comes back sealed. Until the unseal threshold is supplied, typically 3 of 5 Shamir shares, applications that fetch secrets at startup cannot start.
What already exists?
Vault and OpenBao as free open source, Infisical and Doppler as managed products, SOPS with age for file-level encryption, Bitwarden Secrets Manager for teams already on Bitwarden, and AWS Secrets Manager at $0.40 per secret per month. All of them work. None of them ships unattended reboot recovery for a single self-hosted box.
Can auto-unseal be secure on one machine?
Only if the key is bound to hardware. A TPM 2.0 measured boot chain releases the key only to the firmware and OS image that was running when it was sealed, which is meaningfully stronger than a key file on disk. It is still weaker than a cloud KMS or an HSM, and any honest product page has to say so.
What changed in 2023?
On 10 August 2023 HashiCorp relicensed Vault and the rest of its portfolio from MPL 2.0 to the Business Source License. OpenBao forked later that year to keep an open continuation, and now runs under the Linux Foundation's OpenSSF.
Does this audience pay for anything?
Rarely, and almost never per seat. They will pay for hosting they cannot run themselves, and they will pay for hardware. A subscription for a configuration file is not something this audience buys.
How is this data collected and verified?
Technical claims come from Vault, OpenBao and vendor documentation, each cited with a date. Quotes link to the original thread. See how data is collected.
One new evidence-backed need every day. Every trend traced to the original post and the exact quote.
Subscribe $19.99/mo →