Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Jitsu

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
Full reviewWebsite
Jitsu logo

Jitsu

Developer Tools

Open source event pipeline that streams behavioural data to your own warehouse

From
Free
Free plan
Yes
Full reviewWebsite

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.; Jitsu jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • They diverge on capability: HashiCorp Boundary covers Identity-based access, Jitsu covers Event collection.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where HashiCorp Boundary and Jitsu differ
AttributeHashiCorp BoundaryJitsu
Pricing modelOpen source, no licence feePer month by event volume
PlatformsLinux, macOS, Windows, WebWeb, Linux, Docker, Kubernetes, iOS, Android
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 Jitsu

  • Event collection
  • Warehouse destinations
  • Connector syncs
  • Transformations
  • Bundled ClickHouse
  • Event debugger
  • Self-hosting
  • Custom domains

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

Jitsu

  • A team paying five figures a year to a customer data platform when all it actually does is send events to Snowflakenot HashiCorp Boundary
  • An engineering group that needs event collection running inside its own VPC for data residency or security review reasonsnot HashiCorp Boundary
  • A product analytics setup that wants raw events in the warehouse as the source of truth rather than trapped in a vendor toolnot HashiCorp Boundary
  • A startup that needs first-party event collection on its own domain to reduce loss from tracker blocking without paying CDP pricesnot 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.

Jitsu

  • Jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • Connector sync frequency is deliberately tiered, with the free plan limited to manual runs and one daily sync, so anything approaching operational freshness requires the paid plan or self-hosting.
  • Self-hosting means you own the reliability of a system that drops data silently when misconfigured, and event loss is uniquely hard to notice because nothing errors, the numbers are just quietly lower.
  • The connector catalogue is far smaller than Fivetran or Airbyte, so if your requirement is pulling from many SaaS sources rather than pushing events, Jitsu is the wrong half of the problem.
  • It is a small company with a small commercial team, so enterprise procurement processes around security review, contractual SLAs and support escalation take longer than with an incumbent vendor.

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

Jitsu

Free
  • Open SourceFree
    • MIT licence
    • Self-host on any cloud
    • No usage limits
  • Cloud FreeFree
    • Unlimited captured events
    • 200,000 active events per month
    • Manual connector runs only
  • Business$99/month
    • 2,000,000 active events per month
    • $40 per additional million events
    • Hourly connector sync frequency
  • Enterprise$undefined/year
    • Custom event volume
    • One minute sync frequency
    • Unlimited active syncs

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

Choose Jitsu if

  • You need event collection.
  • You want to start without paying.
  • You work on Web, Linux, Docker, Kubernetes, iOS, Android.
  • You also want warehouse destinations.
Jitsu review

Questions people ask

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

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.

Jitsu: Is Jitsu the same as Jitsi?

No. Jitsu is an open source event data pipeline. Jitsi is an unrelated video conferencing project.

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.

Jitsu: Can I self-host for free?

Yes. The project is MIT licensed with no usage limits when self-hosted.

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.

Jitsu: How does the cost compare with Segment?

The Business plan is 99 US dollars a month for two million active events, where a per-tracked-user CDP typically costs orders of magnitude more at comparable volume.

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.

Jitsu: Does Jitsu do identity resolution?

No. It transports and transforms events; identity stitching and audiences are not part of the product.

Share

Related pages

More on HashiCorp Boundary

More on Jitsu

Keep looking

Other head to heads