Softwr

Databases · head to head

Immuta vs Rhombus Systems

Immuta logo

Immuta

Databases

Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery

From
On request
Rated
-
Full reviewWebsite
Rhombus Systems logo

Rhombus Systems

Cybersecurity

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

From
$149/year
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Immuta contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate.; 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: Immuta covers Attribute-based policy, 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 Immuta and Rhombus Systems actually diverge.

Attributes where Immuta and Rhombus Systems differ
AttributeImmutaRhombus Systems
Starting priceOn request$149/year
Pricing modelquotePer camera per year licence plus hardware
PlatformsWeb, API, CloudWeb, iOS, Android
CategoryDatabasesCybersecurity

Identical on both: free tier (No), 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 Immuta

  • Attribute-based policy
  • Native enforcement
  • Dynamic masking
  • Row-level filtering
  • Purpose-based access
  • Sensitive data tagging
  • Audit logging
  • Multi-platform

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.

Immuta

  • A bank whose Snowflake estate has grown to tens of thousands of roles that no one can review before an auditnot Rhombus Systems
  • A healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recordednot Rhombus Systems
  • A multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasetsnot Rhombus Systems
  • An organisation running both Snowflake and Databricks that wants one policy set rather than two divergent implementationsnot Rhombus Systems

Rhombus Systems

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

Where each one falls short

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

Immuta

  • Contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate.
  • Policy is only as good as the data classification underneath it, so an organisation with poorly tagged columns will spend months on classification before Immuta enforces anything useful.
  • Native enforcement means capability varies by platform, and a feature available on Snowflake may be absent or behave differently on BigQuery, which undermines the promise of one policy set everywhere.
  • Adding an access governance layer creates a new dependency in the path to data: a misconfigured policy silently returns fewer rows rather than erroring, and analysts can act on incomplete results without noticing.
  • It governs cloud data platforms, so personal data in operational databases, files and SaaS applications sits outside its scope and needs separate controls, meaning Immuta is rarely the whole answer.

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

Immuta

On request
  • Immuta Platform$undefined/year
    • Attribute-based policy authoring
    • Native enforcement in supported data platforms
    • Dynamic masking and row-level security

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

  • You need attribute-based policy.
  • You work on Web, API, Cloud.
  • You also want native enforcement.
Immuta review

Choose Rhombus Systems if

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

Questions people ask

Is Immuta or Rhombus Systems better?
Neither clearly leads. Immuta starts at On request and Rhombus Systems at $149/year, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Immuta or Rhombus Systems?
Immuta starts at On request and Rhombus Systems at $149/year.
Does Immuta or Rhombus Systems run on more platforms?
Immuta runs on Web, API, Cloud. Rhombus Systems runs on Web, iOS, Android.
What is Immuta best used for?
Immuta is most often used for a bank whose snowflake estate has grown to tens of thousands of roles that no one can review before an audit, a healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recorded, a multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasets, an organisation running both snowflake and databricks that wants one policy set rather than two divergent implementations. Of those, a bank whose snowflake estate has grown to tens of thousands of roles that no one can review before an audit and a healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recorded are not what Rhombus Systems is typically brought in for.
What can Immuta do that Rhombus Systems cannot?
Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering. Rhombus Systems covers On-camera storage, No NVR or server, AI search, Access control.

Answered from the vendors’ own pages

Immuta: Does Immuta sit in the query path?

No. It compiles policies into the data platform's own native controls, so queries run at normal speed through your existing tools.

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.

Immuta: What does it cost?

Not published. Market data suggests roughly 100,000 to 200,000 US dollars a year for mid-market deployments and considerably more at enterprise scale.

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.

Immuta: Is Immuta still independent?

Yes. It remains independently owned, unlike several competitors in data access governance that have been acquired.

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.

Immuta: Does it work across more than one warehouse?

Yes, one policy set can target Snowflake, Databricks, BigQuery and Starburst, though enforcement capability varies by platform.

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

More on Immuta

More on Rhombus Systems

Keep looking

Other head to heads