Softwr

Cybersecurity · head to head

HashiCorp Boundary vs HCP Terraform

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
HCP Terraform logo

HCP Terraform

Developer Tools

Infrastructure as code provisioning and management, formerly Terraform Cloud

From
Free
Free plan
Yes

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.; HCP Terraform legacy free version deprecated; no current freemium tier
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which HashiCorp Boundary and HCP Terraform actually diverge.

Attributes where HashiCorp Boundary and HCP Terraform differ
AttributeHashiCorp BoundaryHCP Terraform
Pricing modelOpen source, no licence feeusage-based
PlatformsLinux, macOS, Windows, WebWeb
CategoryCybersecurityDeveloper Tools

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

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

  • Identity-based access
  • Just-in-time credentials
  • Dynamic host catalogues
  • Session recording
  • Transparent sessions
  • Multi-hop workers
  • Audit logging
  • Terraform provider

Only in HCP Terraform

Nothing recorded that HashiCorp Boundary does not also cover.

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 HCP Terraform
  • Granting contractors time-boxed database access without ever issuing them a credential they could keepnot HCP Terraform
  • An estate where autoscaling replaces hosts continuously and a static access list is always out of datenot HCP Terraform
  • Producing session recordings as evidence for an audit that requires proof of who touched production and what they rannot HCP Terraform

HCP Terraform

  • Infrastructure as Code managementnot HashiCorp Boundary
  • Cloud resource provisioningnot 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.

HCP Terraform

  • Legacy free version deprecated; no current freemium tier
  • New users receive $500 credit but still require usage to continue service
  • Terraform Enterprise requires custom pricing

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

HCP Terraform

Free
  • Essentials$0.1/month
    • Per resource pricing
    • Remote state storage
    • VCS connection
  • Standard$0.47/month
    • Per resource pricing
    • Essentials features plus unlimited modules
    • Module deprecation
  • Premium$0.99/month
    • Per resource pricing
    • Standard features plus module revocation
    • Waypoint actions

Which should you pick?

Choose HashiCorp Boundary if

  • You need identity-based access.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want just-in-time credentials.

Choose HCP Terraform if

  • You want to start without paying.

Questions people ask

Is HashiCorp Boundary or HCP Terraform better?
Neither clearly leads. HashiCorp Boundary starts at Free and HCP Terraform at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, HashiCorp Boundary or HCP Terraform?
HashiCorp Boundary starts at Free and HCP Terraform at Free.
Does HashiCorp Boundary or HCP Terraform run on more platforms?
HashiCorp Boundary runs on Linux, macOS, Windows, Web. HCP Terraform runs on Web.
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 HCP Terraform is typically brought in for.
What can HashiCorp Boundary do that HCP Terraform cannot?
HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.

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.

HCP Terraform: How much does HCP Terraform cost?

HCP Terraform uses per-resource pricing starting at $0.10/month/resource for Essentials, $0.47/month/resource for Standard, and $0.99/month/resource for Premium.

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.

HCP Terraform: Does HCP Terraform offer a free tier?

No, the legacy free version has been deprecated. However, new users receive $500 credit to try the service.

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.

HCP Terraform: What does the Standard plan include?

Standard plan at $0.47/month/resource includes unlimited modules, module deprecation, team notifications, no-code provisioning, and Waypoint templates.

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.

Share

Related pages

Other head to heads