Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Restate

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
Full reviewWebsite
Restate logo

Restate

Developer Tools

Durable execution engine in Rust with a free tier and low-latency workflows

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.; Restate the runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.
  • They diverge on capability: HashiCorp Boundary covers Identity-based access, Restate covers Durable execution.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where HashiCorp Boundary and Restate differ
AttributeHashiCorp BoundaryRestate
Pricing modelOpen source, no licence feePer month by durable action count
PlatformsLinux, macOS, Windows, WebLinux, macOS, Web
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 Restate

  • Durable execution
  • Virtual objects
  • Single binary runtime
  • Multi-language SDKs
  • Workflows and sagas
  • Restate Cloud

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

Restate

  • Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot HashiCorp Boundary
  • AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot HashiCorp Boundary
  • Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot HashiCorp Boundary
  • A small team that wants durable workflows without operating a Temporal cluster and its databasenot 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.

Restate

  • The runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.
  • Restate Cloud jumps from a free fifty thousand actions straight to 300 US dollars a month for twenty million, so a workload sitting at a few hundred thousand actions pays enterprise-shaped money for hobby-shaped volume.
  • It is a young project against Temporal’s established base, so hiring engineers who already know it is unrealistic and the answer to most questions is in the docs rather than on Stack Overflow.
  • The programming model requires structuring code around durable handlers and virtual objects, which is a genuine rewrite for existing services rather than a library you add.
  • The single-binary simplicity that makes small deployments cheap also means fewer operational knobs at very large scale than a system designed as separable components.

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

Restate

Free
  • FreeFree
    • Fifty thousand durable actions per month
    • No credit card required
    • Community support
  • Starter$300/month
    • Twenty million actions per month
    • Two hundred actions per second, bursting to one thousand
    • Twenty GB storage
  • Pro$1000/month
    • Fifty million actions per month
    • Five hundred actions per second, bursting to two thousand
    • Fifty GB storage
  • Enterprise$undefined/year
    • Negotiated volume
    • Twenty-four seven P0 support
    • 99.99 per cent SLA

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

  • You need durable execution.
  • You want to start without paying.
  • You work on Linux, macOS, Web.
  • You also want virtual objects.
Restate review

Questions people ask

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

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.

Restate: Is Restate open source?

The SDKs are MIT. The runtime is under a Business Source Licence, which permits self-hosting but not offering it as a competing service.

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.

Restate: How does it compare with Temporal?

Same problem, different shape: one Rust binary with embedded storage instead of a server plus database plus workers, and lower per-step latency.

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.

Restate: Is there a free tier?

Yes, fifty thousand durable actions a month on Restate Cloud with no card required.

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.

Restate: Which languages are supported?

TypeScript, Java, Kotlin, Go, Python and Rust.

Share

Related pages

More on HashiCorp Boundary

More on Restate

Keep looking

Other head to heads