Softwr

Cybersecurity · head to head

Clerk vs HashiCorp Boundary

Clerk logo

Clerk

Cybersecurity

Drop-in user authentication and management for developers

From
Free
Rated
-
HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Rated
-

The short version

  • Each has a real cost: Clerk pricing scales with monthly retained users, which can grow expensive quickly for consumer apps with large user bases.; 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: Clerk covers Prebuilt UI components, 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 Clerk and HashiCorp Boundary actually diverge.

Attributes where Clerk and HashiCorp Boundary differ
AttributeClerkHashiCorp Boundary
Pricing modelfreemiumOpen source, no licence fee
Platformsweb, ios, android, apiLinux, macOS, Windows, Web

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 Clerk

  • Prebuilt UI components
  • Organization management
  • Multi-factor authentication
  • Social sign-on
  • Billing
  • Enterprise connections

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.

Clerk

  • Adding sign-in and user profiles to a web or mobile app quicklynot HashiCorp Boundary
  • B2B SaaS apps needing organizations and role-based accessnot HashiCorp Boundary
  • Startups wanting prebuilt UI instead of building auth in-housenot HashiCorp Boundary
  • Apps needing MFA and fraud detection out of the boxnot 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 Clerk
  • Granting contractors time-boxed database access without ever issuing them a credential they could keepnot Clerk
  • An estate where autoscaling replaces hosts continuously and a static access list is always out of datenot Clerk
  • Producing session recordings as evidence for an audit that requires proof of who touched production and what they rannot Clerk

Where each one falls short

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

Clerk

  • Pricing scales with monthly retained users, which can grow expensive quickly for consumer apps with large user bases.
  • Enterprise SSO connections beyond the first are billed as add-ons, adding cost for larger organizations.
  • The Business tier's extra dashboard seats cost $20/month each, which adds up for larger teams.
  • Enterprise-tier features like the 99.99% uptime SLA require annual contracts rather than flexible monthly billing.

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

Clerk

Free
  • HobbyFree
    • 50,000 MRU limit per app
    • Up to 3 dashboard seats
    • Unlimited applications
  • Pro$25/month
    • 50,000 MRUs included, $0.02/MRU overage
    • Up to 3 dashboard seats
    • 1 Enterprise Connection included
  • Business$300/month
    • 50,000 MRUs included with volume pricing
    • 10 dashboard seats included
    • SOC2 report and priority support
  • Enterprise$undefined/month
    • Custom pricing, annual billing
    • 99.99% uptime SLA
    • HIPAA available, dedicated Slack channel

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

  • You need prebuilt ui components.
  • You want to start without paying.
  • You work on web, ios, android, api.
  • You also want organization management.

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.

Questions people ask

Is Clerk or HashiCorp Boundary better?
Neither clearly leads. Clerk 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, Clerk or HashiCorp Boundary?
Clerk starts at Free and HashiCorp Boundary at Free.
Does Clerk or HashiCorp Boundary run on more platforms?
Clerk runs on web, ios, android, api. HashiCorp Boundary runs on Linux, macOS, Windows, Web.
Can I use Clerk for free?
Both have a free tier, so you can try either at no cost before committing.
What is Clerk best used for?
Clerk is most often used for adding sign-in and user profiles to a web or mobile app quickly, b2b saas apps needing organizations and role-based access, startups wanting prebuilt ui instead of building auth in-house, apps needing mfa and fraud detection out of the box. Of those, adding sign-in and user profiles to a web or mobile app quickly and b2b saas apps needing organizations and role-based access are not what HashiCorp Boundary is typically brought in for.
What can Clerk do that HashiCorp Boundary cannot?
Clerk covers Prebuilt UI components, Organization management, Multi-factor authentication, Social sign-on. HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.

Answered from the vendors’ own pages

Clerk: What does Clerk cost?

Clerk's Hobby plan is free with a 50,000 MRU limit; Pro is $25/month ($20/month billed annually), Business is $300/month ($250 annually), and Enterprise uses custom annual pricing.

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.

Clerk: Is there a free plan and what are its limits?

Yes, the Hobby plan is free with a 50,000 monthly retained user (MRU) limit per app, up to 3 dashboard seats, and unlimited applications, with no credit card required.

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.

Clerk: How is usage metered?

Clerk meters by monthly retained users (MRUs) — users who return to the app at least a day after signing up — with overage billed at $0.02 per MRU beyond the included 50,000 on paid plans.

Source
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

Other head to heads