Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

HashiCorp Vault Alternatives (2026): 8 Secrets Managers

What can replace HashiCorp Vault when your team still needs one safe home for secrets? Four kinds of tool cover the job: a community fork of the same codebase, hosted developer secrets platforms, file-level encryption that keeps secrets in your repo, and the secrets services inside each big cloud. Match the kind to how your apps read secrets today.

If you want to leave HashiCorp Vault but keep the way your team already works, the closest swap is OpenBao, a community fork of the same codebase. If what you really want is to stop running a secrets server at all, move to a hosted secrets platform, keep encrypted values in your repo with a file-level tool, or use the secrets service built into the cloud you already pay for.

Which of those is right depends far less on features than on one honest answer: what is it about Vault you're trying to get away from? Get that wrong and you'll spend a quarter migrating, only to land in the same spot with a different logo on the login page.

Start with the reason you're leaving

People leave Vault for three quite different reasons, and each one points somewhere else.

Who runs the project. This is the reason most people give, so here's what changed. The licence file in Vault's own GitHub repository now puts Vault 1.15.0 and later under the Business Source License and names IBM as the licensor. You can still run it in production, but the terms rule out offering it to others as a hosted or embedded product that competes with IBM's paid versions. If your worry is the owner, the licence or the roadmap, a community fork taken from the last openly licensed code answers that directly. Look at who governs it, too: a project hosted by a foundation with several companies contributing is a different bet from one maintained by a single firm. The concepts, the policies and much of the muscle memory carry over. That makes it the smallest move on the list, though still a move: read the project's notes on what's changed and test the auth methods and integrations your apps lean on before you assume they behave identically.

The work of running it. If the pain is upgrades, unsealing, storage backends and the on-call pager, a fork keeps all of that on your plate. Here a hosted developer secrets platform is the better answer. You give up some control and gain your weekends back.

Too much tool for the job. Plenty of teams adopted Vault when what they needed was somewhere safe to put forty API keys and a database password. If that's you, a file-level encryption tool or your cloud provider's own service may cover everything with a fraction of the moving parts.

Run it, rent it, encrypt it or use your cloud's

Every tool below sits on one of four routes, and each route moves a different chore onto a different desk.

Self-hosting is the first route. The fork and the open source platforms with a self-hosting option keep secrets on infrastructure you control. That matters for strict data residency or air-gapped environments. The cost is an always-on, high-stakes service that your team patches, backs up and monitors, because if it goes down, every app that reads a secret at start-up goes with it.

Renting is the second. Hosted platforms centralise secrets across projects and environments and sync them into CI/CD and production. Developers stop passing dotenv files around on Slack, which on its own is reason enough for many teams. Some of these vendors now pitch a wider idea: one place for application secrets, certificates and privileged access, or a full identity layer for machines, people and AI agents.

The third route has no server at all. SOPS encrypts the values in YAML, JSON, INI and dotenv files while leaving the keys readable, so a config change can still be reviewed in a pull request. The catch is that access control, rotation and audit now live in whoever holds the decryption keys and in your team's habits, which is fine for five services and tiring for fifty.

Last comes the cloud you already pay for. If nearly everything runs in one cloud, its native secrets service keeps secrets close to the workloads that read them, with access tied to the identity system you already manage. It falls apart a little in a multi-cloud estate, where you end up with two or three places to look and two or three sets of rules to keep in step.

What is easy to miss in a Vault move

Static secrets, the passwords and keys you put in and read back out, move between almost any two tools without drama. The harder bits are the features that do work on your behalf. If you use Vault to issue short-lived database credentials on request, to run a private certificate authority or to encrypt data for apps without them ever seeing a key, check how each candidate handles that job, or whether you'll need a second tool for it. Roughly: the fork keeps all three, because it grew from the same codebase, but check its docs for each job by name rather than assuming. The hosted platforms vary, and the ones that pitch certificates alongside secrets are where to look for the CA work. File-level encryption covers none of them, and in the big clouds these jobs tend to live in neighbouring services rather than the secrets store, so they're a separate line on the bill. A shortlist that ignores those features looks cheap right up to the week you discover them.

The other thing nobody writes down is who reads what. Before choosing anything, build an inventory: every app, pipeline, scheduled job and person that reads a secret, how each one authenticates, and how often each secret rotates. It usually turns up a few surprises, such as a cron job reading a secret by a hard-coded path, or a certificate renewal that quietly depended on the old server. That inventory is your real migration plan. The tool comes second.

What a Vault alternative costs

The hosted platforms mostly have a free tier for very small teams, typically capped at around three to five users or machine identities, then charge per user or per identity. Per-user rates for each plan are on the vendors' own pricing pages. Enterprise identity platforms tend to quote on request. The cloud providers bill differently, per secret stored plus per API call, which works out at well under a dollar a secret per month in the published examples, though a chatty app that fetches secrets on every request can make the API line grow.

The fork and the file-level tool cost nothing to download. Their price is people: the hours spent running a highly available secrets service, or keeping encryption keys and access rules tidy by hand. Put a realistic number on that before you call any open source route free.

A one-hour trial on one service

Don't evaluate secrets managers by reading docs. Pick one low-risk service with a handful of secrets and a team that can watch it, and give two candidates the same small job. Copy the secrets in and grant that service the narrowest access that works. Point it at the new store in staging. Then rotate one secret on purpose and watch what happens: does the app pick up the new value on its own, or does it need a restart you didn't plan for? Finally, look at the audit trail and check you can answer who read that secret in the last hour.

The candidate you'd pick is the one where the rotation needed no restart and the audit question took one search. Once the service has run cleanly for a few days, delete the old copies so the two stores can never drift apart, and only then move the next service.

Mistakes that make a secrets migration hurt

Moving everything in one weekend is the big one; secrets migrations go best one service at a time. Close behind is copying Vault's policies across wholesale instead of using the move to cut access back, because most teams find developers holding production secrets they haven't touched in a year. Then there's forgetting non-human readers: CI runners, scheduled jobs and, increasingly, AI agents. Treat each agent like any other machine identity, with its own credentials and the narrowest access that works. Finally, there's the old store itself: left running with no end date, it doubles every rotation, and one day someone forgets the second half.

The eight alternatives

OpenBao

The community fork of Vault's own codebase, now a Linux Foundation project, for teams who want familiar concepts without the original steward.

Infisical

One platform that keeps application secrets, certificates and privileged access together across cloud, on-prem and AI infrastructure.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

Doppler

A hosted secrets service that gathers keys from every project and environment, then syncs them into CI/CD pipelines and production.

Phase

A smaller open source secrets platform covering development through to production, with a self-hosted route for teams that want the data in-house.

Akeyless

Secrets management folded into a wider identity security platform for machines, people and AI agents, built around the idea of moving past static secrets.

SOPS

A command-line encryption tool that scrambles the values inside config files and leaves the keys readable, so secrets can sit safely in Git.

AWS Secrets Manager

Amazon's own service for storing, encrypting and centrally auditing the credentials that workloads on its cloud need.

Azure Key Vault

Microsoft's cloud vault for the cryptographic keys and other secrets that applications and services running on Azure depend on.

Which kind to pick

Happy with Vault's model, unhappy with who owns it: the fork. Tired of running a secrets server: a hosted developer platform, trialled against your noisiest service first. A small team with a few services and everything in Git: file-level encryption, as long as someone owns the keys. Almost everything on one cloud: that cloud's own service, with a hosted or self-run platform only if you later spread out. Many machine and agent identities to govern: look at the platforms that put identity first and secrets second.

Secrets rarely move on their own; they travel with your deployment and infrastructure tooling. If that's changing too, my lists of container orchestration alternatives and configuration management alternatives cover the tools your secrets will be read by, and these login and identity provider alternatives help if user identity is part of the same project.

Do you make a secrets management or encryption tool? Tool makers can ask to be considered for a featured place on this list.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Frequently asked questions

Do I have to rotate every secret when I leave Vault?

It's the safest habit. Anything that sat in the old store, or in a backup or log of it, should be treated as known to that system. Rotating as each service moves means the old copies are worthless once you switch the old store off.

Can two secrets managers run side by side during a migration?

Yes, and for a while they usually have to. The rule that keeps it safe is one source of truth per secret: each secret is written in exactly one store, and anything else that holds it is a read-only copy fed from there.

Will my Vault policies work in another tool?

Only in the fork, and even there test them. Every other tool models access its own way, so expect to rewrite policies. That's no bad thing: it's the best chance you'll get to remove access nobody uses.

What should happen to Vault after the last service moves?

Revoke its tokens, take a final encrypted backup for your records if your retention rules require one, then shut it down and remove its credentials from CI. Then check the inventory you built at the start: every reader on it should now point somewhere else.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.