Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Sourcegraph

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Free plan
Yes
Sourcegraph logo

Sourcegraph

Developer Tools

Code search and intelligence platform for large codebases with Cody AI assistant

From
$16000/year
Free plan
No

The short version

  • Only HashiCorp Boundary has a free tier, so it costs nothing to try first.
  • 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.; Sourcegraph enterprise pricing starting at $16k annually creates significant barrier for small teams
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where HashiCorp Boundary and Sourcegraph differ
AttributeHashiCorp BoundarySourcegraph
Starting priceFree$16000/year
Pricing modelOpen source, no licence feesubscription
Free tierYesNo
PlatformsLinux, macOS, Windows, WebCloud, Self-hosted
CategoryCybersecurityDeveloper Tools

Identical on both: 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 Sourcegraph

Nothing recorded that HashiCorp Boundary does not also cover.

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

Sourcegraph

  • Large-scale code migrations across hundreds of repositoriesnot HashiCorp Boundary
  • Enterprise governance and code ownership trackingnot HashiCorp Boundary
  • AI-assisted bug hunting and security pattern detectionnot HashiCorp Boundary
  • Onboarding engineers into large unfamiliar codebasesnot HashiCorp Boundary
  • Regulatory compliance and code audit trailsnot 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.

Sourcegraph

  • Enterprise pricing starting at $16k annually creates significant barrier for small teams
  • No free tier or standard plan published; all options require custom sales engagement
  • Complex enterprise-only positioning limits adoption compared to GitHub Copilot's pervasiveness
  • Requires indexing entire codebase; not suitable for small or ephemeral projects

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

Sourcegraph

$16000/year
  • Enterprise$16000/year
    • Scales with team size
    • Credits for AI features per user
    • Deep Search

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.

Choose Sourcegraph if

  • You work on Cloud, Self-hosted.

Questions people ask

Is HashiCorp Boundary or Sourcegraph better?
Neither clearly leads. HashiCorp Boundary starts at Free and Sourcegraph at $16000/year, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, HashiCorp Boundary or Sourcegraph?
HashiCorp Boundary has a free tier; the other does not. Paid plans start at Free for HashiCorp Boundary and $16000/year for Sourcegraph.
Does HashiCorp Boundary or Sourcegraph run on more platforms?
HashiCorp Boundary runs on Linux, macOS, Windows, Web. Sourcegraph runs on Cloud, Self-hosted.
Can I use HashiCorp Boundary for free?
Yes. HashiCorp Boundary has a free tier, so you can try it without paying. Sourcegraph starts at $16000/year.
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 Sourcegraph is typically brought in for.
What can HashiCorp Boundary do that Sourcegraph cannot?
HashiCorp Boundary covers Identity-based access, Just-in-time credentials, Dynamic host catalogues, Session recording.

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.

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.

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