Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Osano

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Rated
-
Full reviewWebsite
Osano logo

Osano

Cybersecurity

Consent management and data privacy platform with a published self-serve tier

From
Free
Rated
-
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.; Osano the published visitor ceilings are low, with the paid self-serve tier stopping around 30,000 monthly visitors, so any consumer facing site with real traffic leaves published pricing immediately and negotiates a quote with no public anchor.
  • They diverge on capability: HashiCorp Boundary covers Identity-based access, Osano covers Consent banner.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where HashiCorp Boundary and Osano differ
AttributeHashiCorp BoundaryOsano
Pricing modelOpen source, no licence feePer month by monthly website visitors
PlatformsLinux, macOS, Windows, WebWeb

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

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

Only in Osano

  • Consent banner
  • Pre-consent tag blocking
  • Consent record
  • No fines guarantee
  • Subject rights requests
  • Data mapping
  • Vendor privacy monitoring
  • Cookie scanning

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

Osano

  • A mid market company selling into the EU and California that needs one banner honouring different consent rules by visitor regionnot HashiCorp Boundary
  • A privacy counsel who wants a vendor that will contractually stand behind its consent product rather than disclaim all liabilitynot HashiCorp Boundary
  • A marketing team that needs Google Consent Mode signals wired correctly so analytics and ads degrade rather than break when consent is refusednot HashiCorp Boundary
  • A company with a handful of brand domains wanting one consent record and one scanning schedule across all of themnot 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.

Osano

  • The published visitor ceilings are low, with the paid self-serve tier stopping around 30,000 monthly visitors, so any consumer facing site with real traffic leaves published pricing immediately and negotiates a quote with no public anchor.
  • The no fines guarantee is bounded and conditional on configuring the product as instructed, so it is a marketing differentiator with an indemnity cap rather than the insurance policy the name suggests, and the limits should be read before it influences a decision.
  • Everything beyond consent, including subject rights automation, data mapping and vendor monitoring, is enterprise quoted, so the transparent pricing that attracts buyers covers only the cheapest part of the platform.
  • Tag blocking depends on tags being loaded through the mechanisms Osano can intercept, and marketing teams that inject scripts directly into templates or through server side tagging routinely leak trackers past the banner without anyone noticing.
  • It is a privacy platform rather than a security compliance one, so organisations that also need SOC 2 or ISO 27001 evidence collection run it alongside a separate tool and duplicate parts of the vendor and asset inventory.

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

Osano

Free
  • FreeFree
    • 1 user
    • 1 domain
    • 5,000 monthly visitors
  • Plus$199/month
    • 2 users
    • 3 domains
    • 30,000 monthly visitors
  • Enterprise$undefined/year
    • Unlimited domains and higher visitor volumes
    • Subject rights request automation
    • Data mapping and assessments

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

  • You need consent banner.
  • You want to start without paying.
  • You also want pre-consent tag blocking.
Osano review

Questions people ask

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

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.

Osano: Does the free tier include the no fines guarantee?

No. The guarantee attaches to paid use of the consent product, and the free tier is capped at one domain and 5,000 monthly visitors.

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.

Osano: How is Osano priced?

By monthly website visitors, number of domains and tier. The self-serve path stops at a low visitor ceiling and everything above is quoted.

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.

Osano: Can it handle US state privacy laws as well as GDPR?

Yes, with region aware rule sets covering GDPR, ePrivacy and the US state regimes, so an EU visitor sees an opt-in banner and a US visitor sees the applicable opt-out.

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.

Osano: Does Osano do subject access requests?

Yes, but in the enterprise tier rather than the published plans, and it is quoted separately from consent.

Share

Related pages

More on HashiCorp Boundary

More on Osano

Keep looking

Other head to heads