We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
Pricing is quote-based.
There is no free HCP Vault Dedicated plan listed. Vault can be self-managed, but that shifts ongoing operation to your team. For managed service, Essentials starts at $1.58 per cluster per hour plus $73 per Vault client monthly. That is $219 in client fees for three people or $365 for five, before the cluster charge. Annual prices are not published, so a team of 1–5 should request a quote that spells out billed hours and who counts as a client.
01Every plan, line by line
| Plan | Billed annually | Billed monthly | Built for |
|---|---|---|---|
| Development (IBM HCP Vault Dedicated) | — | Quote | Development and evaluation |
| Essentials (IBM HCP Vault Dedicated) | — | Quote | Teams needing essential Vault features |
| Standard (IBM HCP Vault Dedicated) | — | Quote | Teams needing standard Vault features |
| Flex | — | Quote | Organizations seeking flexible terms |
| Enterprise Self Managed | — | Quote | Organizations managing Vault themselves |
Add-ons and overages
- Essentials and Standard: $73 per Vault client / month
02What the plan grid doesn't tell you
Hourly cluster billing
Essentials starts at $1.58 per cluster per hour and Standard at $1.85. Your total depends on billable hours.
Per-client fees
Essentials and Standard list $73 per Vault client monthly: $219 for three clients or $365 for five.
Unpublished annual totals
Annual prices are not published. Ask the vendor for a written total, including the cluster charge and client count.
Self-managed upkeep
Self-management may avoid HCP subscription charges, but your team owns maintenance and recovery planning.
03Which plan should you buy?
| If you are… | Get | Why |
|---|---|---|
| Development or evaluation | Development (IBM HCP Vault Dedicated) | Starts at $0.62 per cluster per hour and includes up to 25 clients; it is for development and evaluation. |
| Small production team | Essentials (IBM HCP Vault Dedicated) | Starts at $1.58 per cluster per hour plus $73 per Vault client monthly; includes a $500 HCP trial credit. |
| Team needing standard features | Standard (IBM HCP Vault Dedicated) | Starts at $1.85 per cluster per hour and lists the same $73 monthly client fee as Essentials. |
04Is HashiCorp Vault worth the money?
For a small team, Vault is worth pricing out when centralized secrets control, generated database credentials, or transit encryption solve real needs. A self-managed setup may avoid HCP fees, but it puts upkeep on your team. The cheapest listed managed option, Development, is for evaluation; Essentials is the lower-priced listed fit for teams needing essential features. Its hourly cluster charge plus $73 per client each month can make a few seats costly. Ask for a full quote before choosing.
HashiCorp Vault pricing FAQ
Does HashiCorp Vault have a free plan?
The pricing page lists no free plan for HCP Vault Dedicated. Essentials and Standard list a $500 HCP trial credit, but the duration and other trial terms are not published. Reddit users report self-managing Vault without paying for SaaS, though that requires your team to operate it.
What is the cheapest HCP Vault Dedicated plan?
Development (IBM HCP Vault Dedicated) starts at $0.62 per cluster per hour and includes up to 25 clients. It is listed for development and evaluation. Essentials starts at $1.58 per cluster per hour and is the lower-priced listed option for teams needing essential Vault features.
How much does Vault cost for three clients?
Essentials and Standard each list a $73 monthly fee per Vault client. Three clients add $219 per month, plus the cluster charge: from $1.58 per hour on Essentials or $1.85 per hour on Standard. The vendor does not publish annual prices.
Can HashiCorp Vault be self-hosted?
Yes. Self-managed Vault may avoid HCP subscription charges, but the team takes on operation and maintenance. Reddit users report that upkeep and restoring a secret store can require attention. Confirm the current license and support terms with HashiCorp before adopting it.
