The best secrets management tools in 2026
HashiCorp Vault is still the most capable secrets manager, but its Community Edition is no longer open source. OpenBao is the best open-source Vault alternative: an MPL-2.0 fork run under the Linux Foundation, which worked like Vault in our test. Infisical is the best all-rounder for teams that want a modern UI, a free tier and the option to self-host.
On a single cloud, that cloud's own secrets service is usually simplest. For small teams, SOPS with age keeps encrypted secrets in Git with no server at all.
Our top picks
- HashiCorp VaultBest for the most capable, most documented secrets platform
- OpenBaoBest for an open-source Vault replacement
- InfisicalBest for teams that want a modern UI, a free tier and self-hosting
Compare at a glance
| Tool | Best for | Pricing | Open source | Deployment | Tested by us |
|---|---|---|---|---|---|
| HashiCorp Vault | the most capable, most documented secrets platform | Community Edition free; HCP Vault Dedicated pay-as-you-go from $1.58 per hour (small Essentials cluster) plus $72.92 per client per month; Enterprise: contact sales | No | Self-hosted or SaaS (HCP Vault Dedicated) | Docs only |
| OpenBao | an open-source Vault replacement | Free | Yes | Self-hosted | Yes |
| Infisical | teams that want a modern UI, a free tier and self-hosting | Free for up to 5 identities; Pro $20 and Advanced $40 per identity per month billed annually ($23 and $46 monthly); Enterprise custom | Yes | SaaS or self-hosted | Docs only |
| AWS Secrets Manager | workloads that run on AWS | $0.40 per secret per month plus $0.05 per 10,000 API calls | No | SaaS (AWS managed service) | Docs only |
| SOPS (with age) | small teams and GitOps: encrypted secrets in Git | Free | Yes | Self-hosted command-line tool | Yes |
| Doppler | the most polished hosted developer experience | Developer free for 3 users ($8 per extra user per month); Team $21 per user per month; Enterprise custom | No | SaaS; on-prem deployment on the Enterprise plan | Docs only |
| Google Secret Manager | workloads that run on Google Cloud | $0.06 per active secret version per location per month and $0.03 per 10,000 access operations; first 6 versions and 10,000 operations free each month | No | SaaS (Google Cloud managed service) | Docs only |
| Azure Key Vault | workloads that run on Azure | Secrets: $0.03 per 10,000 operations, Standard and Premium (US list price, shown for Central US and East US; varies by region); no per-secret storage fee | No | SaaS (Azure managed service) | Docs only |
| 1Password Secrets Automation | teams already using 1Password | Included with 1Password business plans: Teams Starter Pack $24.95 per month for up to 10 users; Business $8.99 per user per month (billed yearly); Enterprise: contact sales | No | SaaS (service accounts) or self-hosted Connect server | Docs only |
| Bitwarden Secrets Manager | the lowest per-user price, with a free plan | Free for 2 users, 3 projects and 3 machine accounts; Teams $6 and Enterprise $12 per user per month (annual) | No | SaaS; self-hosting on Enterprise | Docs only |
The full ranking
HashiCorp Vault
Best for: the most capable, most documented secrets platform
Vault is still the reference secrets manager: centrally audited secret storage, dynamic secrets such as short-lived database credentials, certificate management, data encryption, and identity-based policies. Since version 1.15 the Community Edition is under the Business Source License, which allows production use unless you offer Vault as a competing hosted product, and HashiCorp is now part of IBM. HCP Vault Dedicated starts at about $1.58 an hour for a small Essentials cluster plus $72.92 per client per month on IBM's pay-as-you-go list. It's powerful, but running a highly available cluster yourself is a real operational job, and the hosted price adds up quickly.
- Pricing
- Community Edition free; HCP Vault Dedicated pay-as-you-go from $1.58 per hour (small Essentials cluster) plus $72.92 per client per month; Enterprise: contact sales (checked November 15, 2026, source)
- License
- Business Source License 1.1 (Community Edition, version 1.15 and later); Enterprise and HCP are proprietary
- Deployment
- Self-hosted or SaaS (HCP Vault Dedicated)
- Runs on
- Linux, macOS, Windows and FreeBSD binaries
Pros
- Dynamic secrets, leases, PKI and encryption as a service
- Self-hosted or hosted (HCP Vault Dedicated)
- Mature policy and identity model
Cons
- Community Edition is BSL, not open source
- HCP pricing combines cluster hours and per-client fees
- Self-hosting a highly available cluster takes real effort
Not tested by us yet: based on the vendor's documentation.
OpenBao
Best for: an open-source Vault replacement
OpenBao is the open-source Vault: a community fork run under the Linux Foundation's OpenSSF, licensed MPL-2.0, with the same model of secrets engines, leases, policies and tokens. In our test, the 2.7.2 binary ran a dev server, stored and versioned a key-value secret, and enforced a read-only policy on a 15-minute token exactly as a Vault user would expect; the CLI even saved its token to ~/.vault-token. It's the natural choice if Vault's license change is your reason to move. The project offers no commercial edition or hosted service, so support and high availability are up to you.
- Pricing
- Free (checked November 15, 2026, source)
- License
- Open source (MPL-2.0)
- Deployment
- Self-hosted
- Runs on
- Linux (deb, rpm and binaries), macOS, Windows and the BSDs
Pros
- Open source (MPL-2.0) under open governance
- Same concepts and commands as Vault
- Official deb and rpm packages with checksums
Cons
- No vendor support or hosted option from the project
- You run, unseal and back it up yourself
- Check plugin and feature parity before migrating
Tested by us: Debian 12 (web-01), OpenBao 2.7.2 (official .deb, SHA-256 matched checksums.txt; binary extracted, not installed), 14 Nov 2026: dev server on a localhost-only port; kv put, get and a second version; a read-only policy and 15-minute token that could read but got 403 permission denied on write. Deleted afterwards.
Infisical
Best for: teams that want a modern UI, a free tier and self-hosting
Infisical is the best all-rounder for teams that want a modern web UI and a free start. The core is MIT-licensed and free to self-host, and the cloud Free plan covers up to 5 identities, with unlimited projects, 3 environments and 10 secret syncs. Pro costs $20 and Advanced $40 per identity per month, billed annually, and Advanced adds dynamic secrets and gateways. An identity is any person or machine, so price a busy CI setup before you commit. Enterprise features such as approval workflows, SCIM and LDAP are under a commercial license.
- Pricing
- Free for up to 5 identities; Pro $20 and Advanced $40 per identity per month billed annually ($23 and $46 monthly); Enterprise custom (checked November 15, 2026, source)
- License
- Core open source (MIT); enterprise features under a commercial license
- Deployment
- SaaS or self-hosted
- Runs on
- Any Linux server via the Infisical CLI (Linux, macOS, Windows) and integrations
Pros
- MIT-licensed core, free to self-host
- Free cloud plan for up to 5 identities
- Secret syncs, environments and dynamic secrets (Advanced)
- Public pricing with a 30-day trial
Cons
- Machine identities count toward per-identity pricing
- Approval workflows and SCIM are Enterprise-only
- Enterprise features under a commercial license
Not tested by us yet: based on the vendor's documentation.
AWS Secrets Manager
Best for: workloads that run on AWS
If your workloads run on AWS, Secrets Manager is the default for good reasons. IAM policies control who can read each secret, AWS handles encryption at rest and replication, and it can rotate AWS and third-party secrets on a schedule. Pricing is simple: $0.40 per secret per month plus $0.05 per 10,000 API calls, so 50 secrets read a million times a month cost about $25. That per-secret fee adds up with hundreds of small secrets, and using it from servers outside AWS means putting AWS credentials on them, which moves the bootstrap problem rather than solving it.
- Pricing
- $0.40 per secret per month plus $0.05 per 10,000 API calls (checked November 15, 2026, source)
- License
- Proprietary
- Deployment
- SaaS (AWS managed service)
- Runs on
- Any workload with AWS credentials; best fit on AWS
Pros
- IAM-based access control
- Scheduled rotation and replication
- Nothing to run; simple public pricing
Cons
- $0.40 per secret per month adds up
- Outside AWS, servers need AWS credentials
- Ties secrets to one cloud
Not tested by us yet: based on the vendor's documentation.
SOPS (with age)
Best for: small teams and GitOps: encrypted secrets in Git
SOPS isn't a server. It encrypts the values in YAML, JSON, ENV and INI files so secrets can live in Git next to the config that uses them, readable only by holders of the right key. age is a small, modern encryption tool whose keys SOPS can use; it also works with PGP and cloud KMS keys. In our test, SOPS 3.13.3 encrypted every value while leaving the keys readable, decrypted with the age key, and refused without it. It's free and needs no infrastructure. There's no access log and no automatic rotation, and revoking someone means re-encrypting files without their key.
- Pricing
- Free (checked November 15, 2026, source)
- License
- Open source (MPL-2.0); age is BSD-3-Clause
- Deployment
- Self-hosted command-line tool
- Runs on
- Linux and macOS (official binaries)
Pros
- No server: secrets live encrypted in Git
- Readable keys and diffs; values encrypted
- age, PGP or cloud KMS keys
- Free (MPL-2.0); CNCF sandbox project
Cons
- No access log or central audit
- Revocation means re-encrypting files
- Anyone with the key and the repo history can read old values
Tested by us: Debian 12 (web-01), SOPS 3.13.3 (official binary, SHA-256 matched) with age 1.1.1 (Debian package, extracted only), 14 Nov 2026: encrypted a sample YAML file to one age recipient; all values became ENC[AES256_GCM,...] with keys readable; decrypted with the key file; decryption without it failed. Deleted afterwards.
Doppler
Best for: the most polished hosted developer experience
Doppler is a polished hosted option for developers: one place for environment variables per project and environment, synced to apps, CI/CD and cloud platforms through its CLI and integrations. The Developer plan is free for 3 users, then $8 per extra user per month, and Team costs $21 per user per month with SAML SSO and 90 days of activity logs. Doppler says AI agents and non-human identities don't count as seats, which helps busy pipelines. Its self-serve plans are SaaS, so secrets live with Doppler; its pricing page lists an on-prem deployment under Enterprise only. Pick it for speed of setup; Infisical's MIT-licensed core, by contrast, is free to self-host.
- Pricing
- Developer free for 3 users ($8 per extra user per month); Team $21 per user per month; Enterprise custom (checked November 15, 2026, source)
- License
- Proprietary
- Deployment
- SaaS; on-prem deployment on the Enterprise plan
- Runs on
- Any server via the Doppler CLI and integrations
Pros
- Fast setup; good CLI and integrations
- Non-human identities don't use seats
- Free for 3 users
Cons
- Self-hosting (on-prem) is Enterprise-only
- SAML SSO needs the $21 Team plan
- Free plan keeps only 3 days of activity logs
Not tested by us yet: based on the vendor's documentation.
Google Secret Manager
Best for: workloads that run on Google Cloud
On Google Cloud, Secret Manager is the obvious choice: IAM-controlled access, versioning, and rotation notifications through Pub/Sub. For small setups it costs far less than AWS, which charges per secret; in our worked example below, Azure came out cheaper still. The first 6 active secret versions and 10,000 access operations each month are free, then it's $0.06 per active version per location and $0.03 per 10,000 accesses. The trap is versions: every active version is billed, in each location if you use user-managed replication, so destroy old versions. Outside Google Cloud, each server needs Google Cloud credentials to read secrets.
- Pricing
- $0.06 per active secret version per location per month and $0.03 per 10,000 access operations; first 6 versions and 10,000 operations free each month (checked November 15, 2026, source)
- License
- Proprietary
- Deployment
- SaaS (Google Cloud managed service)
- Runs on
- Any workload with Google Cloud credentials; best fit on Google Cloud
Pros
- Monthly free usage
- Low per-version and per-access prices
- Versioning and rotation notifications
Cons
- Every active version is billed (per location with user-managed replication)
- Outside Google Cloud, servers need Google credentials
- Ties secrets to one cloud
Not tested by us yet: based on the vendor's documentation.
Azure Key Vault
Best for: workloads that run on Azure
Azure Key Vault stores secrets, keys and certificates, with HSM-backed options and a separate Managed HSM service. For secrets, Microsoft's price list charges per operation, $0.03 per 10,000 in US East (prices vary by region), with no per-secret fee, which makes it cheap for many rarely read secrets. Callers authenticate through Microsoft Entra ID; Microsoft recommends managed identities for Azure resources, which avoids storing a bootstrap secret. That's the catch off Azure: a server elsewhere needs a service principal with a certificate or secret that someone must rotate. On Azure it's the natural choice.
- Pricing
- Secrets: $0.03 per 10,000 operations, Standard and Premium (US list price, shown for Central US and East US; varies by region); no per-secret storage fee (checked November 15, 2026, source)
- License
- Proprietary
- Deployment
- SaaS (Azure managed service)
- Runs on
- Any workload that can authenticate with Microsoft Entra ID (managed identity or service principal); best fit on Azure
Pros
- No per-secret fee; $0.03 per 10,000 operations
- Managed identities remove bootstrap secrets on Azure
- Secrets, keys and certificates in one service
Cons
- Off Azure, you manage service principal credentials
- Designed around Azure resources and identities
- Ties secrets to one cloud
Not tested by us yet: based on the vendor's documentation.
1Password Secrets Automation
Best for: teams already using 1Password
If your team already uses 1Password, Secrets Automation lets servers and pipelines read the same vaults. You can use 1Password-hosted service accounts, which need no infrastructure but have strict rate limits, or a self-hosted Connect server that caches data, has a REST API and no listed rate limits. Both are included with a 1Password subscription: the Teams Starter Pack is $24.95 a month for up to 10 users, and Business is $8.99 per user per month, billed yearly. It's a convenient bridge from people's passwords to machine secrets; busy workloads need a Connect server.
- Pricing
- Included with 1Password business plans: Teams Starter Pack $24.95 per month for up to 10 users; Business $8.99 per user per month (billed yearly); Enterprise: contact sales (checked November 15, 2026, source)
- License
- Proprietary
- Deployment
- SaaS (service accounts) or self-hosted Connect server
- Runs on
- Any server via the 1Password CLI, SDKs or a Connect server
Pros
- Included with 1Password subscriptions
- Service accounts need no infrastructure
- Connect server caches secrets and has a REST API
Cons
- Service accounts are rate-limited
- Connect server is another service to run
- Best value only if you already use 1Password
Not tested by us yet: based on the vendor's documentation.
Bitwarden Secrets Manager
Best for: the lowest per-user price, with a free plan
Bitwarden Secrets Manager is the cheapest paid option per person. The Free plan covers 2 users, 3 projects and 3 machine accounts; Teams is $6 and Enterprise $12 per user per month on an annual subscription, with 20 or 50 machine accounts included and $1 for each extra. The bws CLI runs on Linux, macOS, Windows and Docker, using access tokens scoped to a machine account. Its server code sits in Bitwarden's commercial modules under the source-available Bitwarden License (the rest of Bitwarden's server is AGPL-3.0), so it isn't open source in the OSI sense. Self-hosting is Enterprise-only. Check its integrations against your stack before choosing it.
- Pricing
- Free for 2 users, 3 projects and 3 machine accounts; Teams $6 and Enterprise $12 per user per month (annual) (checked November 15, 2026, source)
- License
- Source available: Secrets Manager's server code sits in the commercial modules under the Bitwarden License (not an OSI license); the rest of Bitwarden's server is AGPL-3.0
- Deployment
- SaaS; self-hosting on Enterprise
- Runs on
- Any server via the bws CLI (Linux, macOS, Windows, Docker) and SDKs
Pros
- Free plan, then $6 per user per month
- Scoped machine-account access tokens
- bws CLI for Linux, macOS, Windows and Docker
Cons
- Self-hosting needs Enterprise
- Server code is source-available (Bitwarden License), not open source
- Free plan limited to 2 users and 3 projects
Not tested by us yet: based on the vendor's documentation.
How we picked
We ranked tools that store application and infrastructure secrets (database passwords, API keys, certificates) and hand them to servers, containers and pipelines. The criteria were: how secrets reach a Linux server without a new secret to bootstrap, access control and audit, dynamic or short-lived secrets, the license and whether you can self-host, how much it costs at small and growing scale, and how much work it is to run. Prices come from each vendor's own pricing page, checked on 15 November 2026.
On 14 November 2026 we ran OpenBao in dev mode and SOPS with age on a Debian 12 test server and deleted both afterwards. The cloud services and SaaS products need accounts, so they're covered from documentation. Password managers for people are a different category; 1Password and Bitwarden appear here only for their machine-secrets products.
What is a secrets manager?
A secrets manager is a service or tool that stores credentials outside your code and configuration files, and gives them only to the people and machines that need them. Instead of a database password sitting in a .env file on every server and in your Git history, the application authenticates to the secrets manager at start-up and receives the password, and every access is logged. Good ones add versioning (so you can roll back), rotation (so a leaked secret stops working), fine-grained policies, and dynamic secrets: credentials created on request with a short lease and revoked automatically, so there's nothing long-lived to leak. The hard part on Linux servers is the first secret, the credential a server uses to prove who it is to the secrets manager. Cloud services solve it with the instance's own cloud identity; self-hosted tools need an auth method such as certificates, tokens with short lifetimes, or a platform identity.
Vault alternatives
People look for Vault alternatives for three main reasons. The license changed: Vault 1.15 and later are under the Business Source License, and HashiCorp is now part of IBM, which some teams treat as a reason to move to open governance. Running Vault well is work: a highly available, backed-up cluster with a tested unseal process is a project in itself. And many teams use only a key-value store and a few integrations, so Vault's power isn't worth its weight. Pick the alternative that matches the reason. For the license, OpenBao keeps Vault's model under MPL-2.0 and open governance at the Linux Foundation. For less operational work, Infisical (self-hosted or cloud), Doppler, or your cloud's own service. For the simplest possible setup, SOPS with age keeps encrypted secrets in Git with no server at all. For teams already paying for 1Password or Bitwarden, their machine-secrets products are the cheapest step up from shared passwords.
What does a secrets manager cost?
Less than most security tools, but the pricing models differ so much that the cheapest option depends on your shape. Self-hosted tools (Vault Community Edition, OpenBao, SOPS) have no license fee; you pay in servers and time. The three big clouds charge for storage and use: AWS per secret plus API calls, Google per active secret version plus accesses (with a monthly free allowance), and Azure per operation with no per-secret fee. SaaS products charge per person, and Infisical charges per identity, which includes machines. So a small team with many secrets and heavy reads pays least on Azure or Google, while a large team with a few shared secrets may pay least for a cloud service and most for per-user SaaS. Here's a worked example at list prices for one month: 50 secrets, one version each, in one region, read 1,000,000 times in total. Per-user tools are priced for a 5-person team; for Infisical we assumed 3 machine identities as well.
| Tool | How it charges | Example month |
|---|---|---|
| Vault Community, OpenBao, SOPS | No license fee | $0 plus your server and time |
| Azure Key Vault | $0.03 per 10,000 operations (US East list price) | $3.00 |
| Google Secret Manager | $0.06 per active version, $0.03 per 10,000 accesses, monthly free usage | $2.64 + $2.97 = $5.61 |
| AWS Secrets Manager | $0.40 per secret, $0.05 per 10,000 calls | $20.00 + $5.00 = $25.00 |
| Bitwarden Secrets Manager Teams | $6 per user (annual) | $30 |
| 1Password Business | $8.99 per user (billed yearly), password manager included | $44.95 |
| Doppler Developer | Free for 3 users, then $8 per extra user (no SAML SSO) | $16 |
| Doppler Team | $21 per user, with SAML SSO | $105 |
| Infisical Pro | $20 per identity (annual), people and machines | 8 identities: $160 |
The cloud services are cheapest at this size, and AWS's per-secret fee is what makes it the most expensive of the three. Per-user SaaS buys you a UI, team workflows and integrations rather than storage.
What we saw testing OpenBao and SOPS
OpenBao 2.7.2 in dev mode (in-memory storage, never for production), with Vault-style commands:
$ bao server -dev -dev-listen-address=127.0.0.1:18299 &
$ bao status | grep -E 'Sealed|Storage Type'
Sealed false
Storage Type inmem
$ bao kv put -mount=secret myapp/db password=example-not-real
$ bao kv get -mount=secret -field=password myapp/db
example-not-real
$ bao policy write app-read - <<'EOF'
path "secret/data/myapp/*" { capabilities = ["read"] }
EOF
$ BAO_TOKEN=$(bao token create -policy=app-read -ttl=15m -field=token) \
bao kv put -mount=secret myapp/db password=x
Code: 403. Errors:
* permission denied
SOPS 3.13.3 with an age key encrypts each value and leaves the structure readable, which is what makes diffs and reviews work:
$ sops encrypt --age age1... app.yaml > app.enc.yaml
$ head -4 app.enc.yaml
db:
user: ENC[AES256_GCM,data:...]
password: ENC[AES256_GCM,data:...]
port: ENC[AES256_GCM,data:...]
$ SOPS_AGE_KEY_FILE=key.txt sops decrypt app.enc.yaml # prints the original file
$ SOPS_AGE_KEY_FILE=/dev/null sops decrypt app.enc.yaml
Recovery failed because no master key was able to decrypt the file.
Open source or SaaS?
Open-source and self-hosted tools (OpenBao, Infisical's MIT core, SOPS, and Vault under its BSL) keep secrets on infrastructure you control and cost nothing in licenses, but the secrets store becomes the most critical service you run: if it's down or its data is lost, nothing can start. You need backups you've restored at least once, monitoring, upgrades and, for Vault and OpenBao, an unseal procedure that works at 3 a.m. SaaS and cloud services take that work away and usually have better availability than a small team can build, in exchange for trusting a vendor with your most sensitive data and accepting its pricing model. A sensible default: use your cloud's service if you're on one cloud, a SaaS tool if you're multi-cloud and small, and OpenBao or Vault when you need dynamic secrets or must keep everything in-house.
Do you need a secrets manager at all?
If you run a few servers and a couple of applications, you may not need a service yet. Files readable only by the service's user (mode 0600, outside the web root and outside Git) are a reasonable start, and SOPS lets you keep those secrets encrypted in your repository without running anything. A secrets manager starts to pay off when several people or pipelines need the same secrets, when you need to know who read what, when someone leaves and you must rotate everything they could see, or when you want short-lived database credentials instead of a password that never changes. At that point, the hours spent finding and rotating secrets by hand cost more than any tool on this list. Whatever you choose, keep secrets out of Git history in plain text, out of process listings, and out of logs.
How we checked this: On 14 Nov 2026 (UTC), on our Debian 12 test VM (web-01): OpenBao 2.7.2 from its official .deb (SHA-256 checked against the release's checksums.txt), extracted rather than installed and run in dev mode on a localhost-only port; and SOPS 3.13.3 (official binary, SHA-256 checked) with age 1.1.1 from Debian's package, also extracted rather than installed. Both were deleted afterwards, including the token file the bao CLI wrote. The other eight products are covered from vendor documentation and pricing pages checked on 15 Nov 2026. Anything we didn't run ourselves comes from the official documentation listed under Sources.
Check which CVEs are really open on your server
HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.
FAQ
What's the best alternative to HashiCorp Vault?
If you want Vault without the Business Source License, OpenBao: it's a fork of Vault under MPL-2.0, run under the Linux Foundation's OpenSSF, with the same secrets engines, leases and policies. If you want a simpler product with a web UI and a hosted option, Infisical. If everything runs on one cloud, that cloud's secrets manager. If you just need encrypted config in Git, SOPS with age.
Is HashiCorp Vault still open source?
Not under an OSI-approved license. Vault 1.15 and later are under the Business Source License 1.1, which lets you use it in production unless you offer it as a hosted product that competes with HashiCorp's (now IBM's) paid versions. OpenBao was forked from Vault's earlier MPL-2.0 code to stay open source.
Is OpenBao compatible with Vault?
It keeps Vault's model: secrets engines, leases, policies and tokens. In our test, Vault-style commands and policies worked unchanged with the bao CLI, and it even saved its token to ~/.vault-token. For an existing Vault cluster, check OpenBao's migration notes for your Vault version and any plugins you rely on before switching.
What are SOPS and age?
SOPS is a command-line tool that encrypts the values in YAML, JSON, ENV and INI files while leaving the keys readable, so encrypted secrets can live in Git and still show a readable diff. age is a small, modern file encryption tool; SOPS can use age keys (or PGP, or a cloud KMS) to decide who can decrypt. Both are free.
How much does a secrets manager cost?
Self-hosted Vault Community Edition, OpenBao and SOPS cost nothing in license fees. Cloud services charge per secret or per call: for 50 secrets read a million times a month, about $25 on AWS, $5.61 on Google Cloud and $3 on Azure at list prices. Per-user SaaS starts at $6 per user per month (Bitwarden Teams) and runs to $21 per user (Doppler Team) or more, such as $40 per identity on Infisical Advanced (billed annually).
Sources
- IBM: HashiCorp pay-as-you-go pricing (Vault Dedicated)
- HashiCorp Vault license on GitHub (Business Source License 1.1)
- HashiCorp docs: What is Vault?
- OpenBao project site
- OpenBao LICENSE on GitHub (MPL-2.0)
- OpenBao v2.7.2 release on GitHub
- Infisical pricing
- Doppler pricing
- AWS Secrets Manager pricing
- AWS Secrets Manager product page
- Azure Key Vault pricing
- Azure Retail Prices API: Key Vault operations in US East ($0.03 per 10K, Standard and Premium)
- Microsoft Learn: What is Azure Key Vault?
- Google Cloud Secret Manager pricing
- 1Password business pricing
- 1Password developer docs: Secrets Automation (service accounts and Connect)
- SOPS project site
- SOPS LICENSE on GitHub (MPL-2.0)
- SOPS v3.13.3 release on GitHub
- Bitwarden Secrets Manager (plans and pricing)
- Bitwarden help: Secrets Manager CLI (bws)
- Bitwarden server LICENSE: AGPL-3.0 by default, Bitwarden License for the bitwarden_license directory (which holds Secrets Manager)