Softwr

Databases · head to head

Immuta vs Timeplus

Immuta logo

Immuta

Databases

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

From
On request
Rated
-
Full reviewWebsite
Timeplus logo

Timeplus

Databases

Streaming SQL engine built on ClickHouse internals, shipping as one small binary

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Timeplus has a free tier, so it costs nothing to try first.
  • 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.; Timeplus proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • They diverge on capability: Immuta covers Attribute-based policy, Timeplus covers Streaming SQL.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Immuta and Timeplus actually diverge.

Attributes where Immuta and Timeplus differ
AttributeImmutaTimeplus
Starting priceOn requestFree
Pricing modelquotePer month for cloud, quoted for self-hosted
Free tierNoYes
PlatformsWeb, API, CloudLinux, macOS, Docker, Kubernetes, Web

Identical on both: user rating (Not yet rated), category (Databases).

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 Timeplus

  • Streaming SQL
  • Unified streaming and historical
  • ClickHouse-based engine
  • Single binary deployment
  • External streams
  • Materialised views

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 Timeplus
  • A healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recordednot Timeplus
  • A multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasetsnot Timeplus
  • An organisation running both Snowflake and Databricks that wants one policy set rather than two divergent implementationsnot Timeplus

Timeplus

  • Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot Immuta
  • Fraud or anomaly detection that must join a live event stream against recent history in one querynot Immuta
  • Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot Immuta
  • A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot 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.

Timeplus

  • Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller.
  • Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines.
  • Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money.
  • Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand.

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

Timeplus

Free
  • Timeplus ProtonFree
    • Apache 2.0 licence
    • Single node only
    • Full streaming SQL engine
  • Timeplus Cloud$199/month
    • One to thirty-two CPUs
    • 4 GB to 128 GB memory
    • From 250 GB SSD storage
  • Self-hosted or BYOC$undefined/year
    • Multi-node clustering
    • Kubernetes or bare metal
    • Customisable compute and storage

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

  • You need streaming sql.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Kubernetes, Web.
  • You also want unified streaming and historical.
Timeplus review

Questions people ask

Is Immuta or Timeplus better?
Neither clearly leads. Immuta starts at On request and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Immuta or Timeplus?
Timeplus has a free tier; the other does not. Paid plans start at On request for Immuta and Free for Timeplus.
Does Immuta or Timeplus run on more platforms?
Immuta runs on Web, API, Cloud. Timeplus runs on Linux, macOS, Docker, Kubernetes, Web.
Can I use Timeplus for free?
Yes. Timeplus has a free tier, so you can try it without paying. Immuta starts at On request.
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 Timeplus is typically brought in for.
What can Immuta do that Timeplus cannot?
Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.

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.

Timeplus: Is Timeplus open source?

The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.

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.

Timeplus: What is the difference from Flink?

Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.

Immuta: Is Immuta still independent?

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

Timeplus: Can Proton run in production?

It can, but it is single-node only, so there is no high availability without the commercial edition.

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.

Timeplus: How much is the cloud?

From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.

Share

Related pages

More on Immuta

More on Timeplus

Keep looking

Other head to heads