Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Hookdeck

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
Full reviewWebsite
Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

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.; Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • They diverge on capability: HashiCorp Boundary covers Identity-based access, Hookdeck covers Ingest and persist.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where HashiCorp Boundary and Hookdeck differ
AttributeHashiCorp BoundaryHookdeck
Pricing modelOpen source, no licence feePer month by delivered event count
PlatformsLinux, macOS, Windows, WebWeb, Linux, macOS, Windows
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 Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

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

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot HashiCorp Boundary
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot HashiCorp Boundary
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot HashiCorp Boundary
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot 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.

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

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

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated support

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

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.
Hookdeck review

Questions people ask

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

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

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.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

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.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

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.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Share

Related pages

More on HashiCorp Boundary

More on Hookdeck

Keep looking

Other head to heads