Softwr

Cybersecurity · head to head

HashiCorp Boundary vs HashiCorp Vault

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Rated
-
HashiCorp Vault logo

HashiCorp Vault

Cybersecurity

Manage secrets and protect sensitive data

From
Free
Rated
-

The short version

  • Each has a real cost: HashiCorp Boundary hashiCorp was acquired by IBM in February 2025 and Enterprise licensing now runs through IBM Passport Advantage; IBM has already retired HCP Vault Secrets, so Boundary's roadmap depends on IBM portfolio decisions rather than HashiCorp's own product strategy.; HashiCorp Vault policies are written in HCL with no graphical user interface for policy management or editing
  • They diverge on capability: HashiCorp Boundary covers Just-in-time credentials, HashiCorp Vault covers Secret storage.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which HashiCorp Boundary and HashiCorp Vault actually diverge.

Attributes where HashiCorp Boundary and HashiCorp Vault differ
AttributeHashiCorp BoundaryHashiCorp Vault
Pricing modelOpen source, no licence feeopen-source
PlatformsLinux, macOS, Windows, WebLinux, Windows, Mac, Api
FoundedUnknown2014

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in HashiCorp Boundary

  • Just-in-time credentials
  • Dynamic host catalogues
  • Session recording
  • Transparent sessions
  • Multi-hop workers
  • Terraform provider

Only in HashiCorp Vault

  • Secret storage
  • Dynamic secrets
  • Encryption as a service
  • Leasing and renewal
  • Secret engines
  • Auth methods
  • Terraform
  • Kubernetes

Both cover

  • Identity-based access
  • Audit logging

What people use each for

The jobs each tool is most often brought in to do.

HashiCorp Boundary

  • A platform team replacing shared SSH keys and a bastion host so that leavers lose access the moment they are removed from the identity providernot HashiCorp Vault
  • Granting contractors time-boxed database access without ever issuing them a credential they could keepnot HashiCorp Vault
  • An estate where autoscaling replaces hosts continuously and a static access list is always out of datenot HashiCorp Vault
  • Producing session recordings as evidence for an audit that requires proof of who touched production and what they rannot HashiCorp Vault

HashiCorp Vault

  • Secrets managementnot HashiCorp Boundary
  • Database credentialsnot HashiCorp Boundary
  • API keysnot HashiCorp Boundary
  • SSH accessnot HashiCorp Boundary
  • PKI and certificatesnot HashiCorp Boundary

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

HashiCorp Boundary

  • HashiCorp was acquired by IBM in February 2025 and Enterprise licensing now runs through IBM Passport Advantage; IBM has already retired HCP Vault Secrets, so Boundary's roadmap depends on IBM portfolio decisions rather than HashiCorp's own product strategy.
  • Enterprise pricing is not published anywhere, and the features most organisations actually need for compliance, notably session recording, are Enterprise only, so the free community edition is rarely the version you end up buying.
  • It solves access to infrastructure, not to applications; browser-based internal tools, SaaS admin consoles and APIs need a separate control, so Boundary is one component of a zero-trust programme rather than the whole thing.
  • Running it yourself means operating controllers, worker nodes and a Postgres database in a highly available configuration, and if that control plane is down nobody can reach production, which makes it a new critical dependency.
  • It is materially easier to adopt if you already run Vault and Terraform; teams without that ecosystem face a steeper learning curve than a device-based mesh product like Tailscale, for a similar access outcome.

HashiCorp Vault

  • Policies are written in HCL with no graphical user interface for policy management or editing
  • Unsealing requires managing multiple key shares and coordinating a quorum of operators
  • Community Edition lacks enterprise features like namespaces and disaster recovery replication
  • Requires additional monitoring solutions for alerting and observability

Pricing, plan by plan

HashiCorp Boundary

Free
  • Boundary Community EditionFree
    • MPL 2.0 open source
    • Self-hosted controllers and workers
    • Identity-based target access
  • Boundary Enterprise$undefined/year
    • Session recording and playback
    • Multi-hop and transparent sessions
    • Multi-tenancy via scopes

HashiCorp Vault

Free
  • Open SourceFree
    • Secrets management
    • Encryption
    • Community support
  • Vault Enterprise$6000/year
    • Replication
    • HSM support
    • Advanced audit

Which should you pick?

Choose HashiCorp Boundary if

  • You need just-in-time credentials.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want dynamic host catalogues.

Choose HashiCorp Vault if

  • You need secret storage.
  • You want to start without paying.
  • You work on Linux, Windows, Mac, Api.
  • You also want dynamic secrets.

Questions people ask

Is HashiCorp Boundary or HashiCorp Vault better?
Neither clearly leads. HashiCorp Boundary starts at Free and HashiCorp Vault at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, HashiCorp Boundary or HashiCorp Vault?
HashiCorp Boundary starts at Free and HashiCorp Vault at Free.
Does HashiCorp Boundary or HashiCorp Vault run on more platforms?
HashiCorp Boundary runs on Linux, macOS, Windows, Web. HashiCorp Vault runs on Linux, Windows, Mac, Api.
Can I use HashiCorp Boundary for free?
Both have a free tier, so you can try either at no cost before committing.
What is HashiCorp Boundary best used for?
HashiCorp Boundary is most often used for a platform team replacing shared ssh keys and a bastion host so that leavers lose access the moment they are removed from the identity provider, granting contractors time-boxed database access without ever issuing them a credential they could keep, an estate where autoscaling replaces hosts continuously and a static access list is always out of date, producing session recordings as evidence for an audit that requires proof of who touched production and what they ran. Of those, a platform team replacing shared ssh keys and a bastion host so that leavers lose access the moment they are removed from the identity provider and granting contractors time-boxed database access without ever issuing them a credential they could keep are not what HashiCorp Vault is typically brought in for.
What can HashiCorp Boundary do that HashiCorp Vault cannot?
HashiCorp Boundary covers Just-in-time credentials, Dynamic host catalogues, Session recording, Transparent sessions. HashiCorp Vault covers Secret storage, Dynamic secrets, Encryption as a service, Leasing and renewal. Both handle Identity-based access, Audit logging.

Answered from the vendors’ own pages

HashiCorp Boundary: Is Boundary open source?

The community edition is, under MPL 2.0. Boundary Enterprise is commercial and is now sold through IBM Passport Advantage.

HashiCorp Vault: Does HashiCorp Vault have a free version?

Yes. The open-source Community Edition is completely free and includes core secrets management, dynamic secrets, and encryption as a service. It is self-hosted with no licensing fees or secret count limits, but lacks enterprise features like namespaces, disaster recovery replication, and Sentinel policies.

Source
HashiCorp Boundary: Does it replace a VPN?

For infrastructure access, largely yes. It grants a session to a specific target rather than putting the user on a network, but it does not cover browser-based internal applications.

HashiCorp Vault: Can I use HashiCorp Vault in production?

The Community Edition is suitable for non-production environments and small teams. For production deployments, organizations typically use HCP Vault Dedicated (managed cloud service starting at approximately 22 USD per month) or Vault Enterprise with custom pricing that includes disaster recovery, performance replication, and 24/7 support.

Source
HashiCorp Boundary: What does Boundary Enterprise cost?

HashiCorp does not publish Boundary pricing. It is quoted, and since the IBM acquisition it is transacted on IBM licensing paper.

HashiCorp Vault: What are the main integrations available?

Vault integrates with AWS, Azure, Google Cloud, Active Directory, Okta, and 80+ other platforms. It supports dynamic credential generation for cloud providers, database systems, and identity services, enabling centralized secret management across multi-cloud infrastructure.

Source
HashiCorp Boundary: Do I need Vault to use it?

No, but the just-in-time credential brokering that makes Boundary worthwhile depends on Vault or an equivalent secrets store.

HashiCorp Vault: Does Vault work offline?

Vault requires network connectivity to function as it is a centralized secrets management server. However, it can be deployed on-premises for air-gapped environments, and clients can cache short-lived tokens for temporary offline access once authenticated.

Source
Share

Related pages

Other head to heads