Softwr

Cybersecurity · head to head

HashiCorp Boundary vs Rhombus Systems

HashiCorp Boundary logo

HashiCorp Boundary

Cybersecurity

Identity-aware session broker for infrastructure access without distributing credentials

From
Free
Rated
-
Rhombus Systems logo

Rhombus Systems

Cybersecurity

Cloud-managed cameras, sensors and access control with a per-camera annual licence

From
$149/year
Rated
-

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.; Rhombus Systems the per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.
  • They diverge on capability: HashiCorp Boundary covers Identity-based access, Rhombus Systems covers On-camera storage.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which HashiCorp Boundary and Rhombus Systems actually diverge.

Attributes where HashiCorp Boundary and Rhombus Systems differ
AttributeHashiCorp BoundaryRhombus Systems
Starting priceFree$149/year
Pricing modelOpen source, no licence feePer camera per year licence plus hardware
Free tierYesNo
PlatformsLinux, macOS, Windows, WebWeb, iOS, Android

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

  • On-camera storage
  • No NVR or server
  • AI search
  • Access control
  • Environmental sensors
  • Unlimited users
  • Ten year hardware warranty
  • Optional cloud archiving

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

Rhombus Systems

  • A school district running video across dozens of buildings with no local IT at each sitenot HashiCorp Boundary
  • A clinic group needing door access and cameras in one console under a single audit trailnot HashiCorp Boundary
  • A logistics operator that wants to search for a specific vehicle across sites without scrubbing footagenot HashiCorp Boundary
  • An office estate replacing ageing NVRs where nobody remains who knows how to maintain 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.

Rhombus Systems

  • The per-camera annual licence never ends and a camera without an active licence stops working, so the total cost over a ten-year hardware life is several times the hardware price.
  • Cameras must be Rhombus, so there is no reuse of existing IP cameras and migrating away means replacing every device rather than changing software.
  • Cloud archiving is priced separately by retention and stream count, and long retention on multisensor cameras runs into five figures per camera, which can dwarf everything else in the quote.
  • On-camera storage is the default retention, so a camera physically stolen or destroyed takes its unarchived footage with it unless cloud archiving was paid for on that camera.
  • Analytics and integrations are good for mid-market needs but shallower than a dedicated enterprise VMS with a large third-party ecosystem, so specialist requirements like advanced LPR or forensic search hit limits.

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

Rhombus Systems

$149/year
  • Professional$149/year
    • Per camera per year
    • Cloud console and management
    • On-camera storage retention
  • Enterprise$199/year
    • Per camera per year
    • Everything in Professional
    • Flexible cloud archiving options
  • Cloud archiving$undefined/year
    • Priced separately by retention period and stream count
    • Multisensor cameras cost several times a single sensor camera
    • Long retention on multisensor models can reach five figures per camera

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 Rhombus Systems if

  • You need on-camera storage.
  • You work on Web, iOS, Android.
  • You also want no nvr or server.

Questions people ask

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

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.

Rhombus Systems: Do I need an NVR or a server?

No. Cameras record on board and connect directly to the cloud console, which is the main operational reason organisations pick it.

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.

Rhombus Systems: What does the licence cost?

Roughly $149 per camera per year for Professional and about $199 for Enterprise, typically sold in one, three, five or ten year terms.

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.

Rhombus Systems: Is cloud storage included?

No. On-camera storage is the default. Cloud archiving is a separate charge priced by retention duration and number of streams.

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.

Rhombus Systems: Can I use my existing cameras?

No. The platform works only with Rhombus hardware, which is the trade-off for the zero-server architecture.

Share

Related pages

Other head to heads