Softwr

Cloud · head to head

Crossplane vs HashiCorp Boundary

Crossplane logo

Crossplane

Cloud

The Cloud-Native Framework for Platform Engineering

From
Free
Rated
-
Full reviewWebsite
HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Crossplane requires Kubernetes expertise and infrastructure; 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.
  • They diverge on capability: Crossplane covers Kubernetes extension, HashiCorp Boundary covers Identity-based access.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Crossplane and HashiCorp Boundary differ
AttributeCrossplaneHashiCorp Boundary
Pricing modelUnknownOpen source, no licence fee
PlatformsKubernetes, AWS, Azure, GCPLinux, macOS, Windows, Web
CategoryCloudCybersecurity

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 Crossplane

  • Kubernetes extension
  • Custom API building
  • Resource management anywhere
  • Declarative interfaces
  • Component library
  • Provider ecosystem

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

What people use each for

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

Crossplane

  • Building platform-as-a-service offerings for internal teamsnot HashiCorp Boundary
  • Creating unified control layers for multi-cloud infrastructurenot HashiCorp Boundary
  • Designing declarative APIs for infrastructure provisioningnot HashiCorp Boundary

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

Where each one falls short

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

Crossplane

  • Requires Kubernetes expertise and infrastructure
  • Steep learning curve for teams new to Kubernetes patterns
  • Provider ecosystem smaller than Terraform

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.

Pricing, plan by plan

Crossplane

Free

No published plan breakdown. See the Crossplane review.

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

Which should you pick?

Choose Crossplane if

  • You need kubernetes extension.
  • You want to start without paying.
  • You work on Kubernetes, AWS, Azure, GCP.
  • You also want custom api building.
Crossplane review

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.
HashiCorp Boundary review

Questions people ask

Is Crossplane or HashiCorp Boundary better?
Neither clearly leads. Crossplane starts at Free and HashiCorp Boundary at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Crossplane or HashiCorp Boundary?
Crossplane starts at Free and HashiCorp Boundary at Free.
Does Crossplane or HashiCorp Boundary run on more platforms?
Crossplane runs on Kubernetes, AWS, Azure, GCP. HashiCorp Boundary runs on Linux, macOS, Windows, Web.
Can I use Crossplane for free?
Both have a free tier, so you can try either at no cost before committing.
What is Crossplane best used for?
Crossplane is most often used for building platform-as-a-service offerings for internal teams, creating unified control layers for multi-cloud infrastructure, designing declarative apis for infrastructure provisioning. Of those, building platform-as-a-service offerings for internal teams and creating unified control layers for multi-cloud infrastructure are not what HashiCorp Boundary is typically brought in for.
What can Crossplane do that HashiCorp Boundary cannot?
Crossplane covers Kubernetes extension, Custom API building, Resource management anywhere, Declarative interfaces. HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.

Answered from the vendors’ own pages

Crossplane: Is Crossplane free?

Yes, Crossplane is open source and free to use. It requires a Kubernetes cluster but has no licensing costs.

Source
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.

Crossplane: What is Crossplane used for?

Crossplane is used to build control planes and platforms for infrastructure management, enabling platform teams to expose safe APIs to other teams.

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 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 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

More on Crossplane

More on HashiCorp Boundary

Keep looking

Other head to heads