Softwr

Machine Learning · head to head

Dataiku vs Immuta

Dataiku logo

Dataiku

Machine Learning

Browser-based platform where visual data preparation and written code share one pipeline

From
Free
Free plan
Yes
Immuta logo

Immuta

Databases

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

From
On request
Free plan
No

The short version

  • Dataiku is free; Immuta prices on request.
  • Only Dataiku lists visual Flow; only Immuta lists attribute-based policy.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Dataiku and Immuta actually diverge.

Attributes where Dataiku and Immuta differ
AttributeDataikuImmuta
Starting priceFreeOn request
Pricing modelFreemiumQuote
Free tierYesNo
PlatformsLinux, macOS, Windows, WebWeb, API
CategoryMachine LearningDatabases

Not yet recorded: founded for Immuta.

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 Dataiku

  • Visual Flow
  • Visual recipes
  • Code recipes and notebooks
  • Computation pushdown
  • Automated machine learning
  • Scenarios
  • Node topology
  • Governance features

Only in Immuta

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

What people use each for

The jobs each tool is most often brought in to do.

Dataiku

  • Organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extractsnot Immuta
  • Regulated model risk environments needing documented lineage, sign-off and a record of how a production model was producednot Immuta
  • Pushing heavy transformations down into a cloud warehouse while keeping the pipeline definition in one reviewable placenot Immuta
  • Large enterprises replacing a sprawl of spreadsheets and unmanaged scripts with something a governance function will acceptnot Immuta

Immuta

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

Where each one falls short

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

Dataiku

  • Visual recipes are stored as Dataiku's own configuration and do not export as runnable SQL or Python, so a Flow with hundreds of visual steps has to be rebuilt from scratch if the organisation ever leaves, and that cost rises with every project added
  • Production requires separate automation and API nodes, each installed and licensed, so the figure quoted for building models is not the figure for running them
  • Licensing is per user across tiers, and the lower tiers are constrained enough that occasional contributors frequently end up needing a full seat, which makes a wide rollout cost more than the initial estimate suggested
  • A self-hosted installation needs a dedicated administrator for upgrades, connection management, permissions and node topology, so the licence is a fraction of the real cost of ownership
  • Computation pushes down to the warehouse or Spark cluster where it is billed by that provider, so a platform sold on making analysts self-sufficient can generate a large warehouse bill that nobody attributes back to it

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

Pricing, plan by plan

Dataiku

Free
  • Free EditionFree
    • Single user
    • Core features
  • EnterpriseFree
    • Full platform
    • Collaboration
    • MLOps

Immuta

On request
  • Immuta PlatformOn request
    • Attribute-based policy authoring
    • Native enforcement in supported data platforms
    • Dynamic masking and row-level security

Which should you pick?

Choose Dataiku if

  • You need visual flow.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want visual recipes.

Choose Immuta if

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

Questions people ask

Is Dataiku or Immuta better?
Neither clearly leads. Dataiku starts at Free and Immuta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dataiku or Immuta?
Dataiku has a free tier; the other does not. Paid plans start at Free for Dataiku and On request for Immuta.
Does Dataiku or Immuta run on more platforms?
Dataiku runs on Linux, macOS, Windows, Web. Immuta runs on Web, API.
Can I use Dataiku for free?
Yes. Dataiku has a free tier, so you can try it without paying. Immuta starts at On request.
What is Dataiku best used for?
Dataiku is most often used for organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extracts, regulated model risk environments needing documented lineage, sign-off and a record of how a production model was produced, pushing heavy transformations down into a cloud warehouse while keeping the pipeline definition in one reviewable place, large enterprises replacing a sprawl of spreadsheets and unmanaged scripts with something a governance function will accept. Of those, organisations where analysts and data scientists must collaborate on the same pipeline rather than exchanging extracts and regulated model risk environments needing documented lineage, sign-off and a record of how a production model was produced are not what Immuta is typically brought in for.
What can Dataiku do that Immuta cannot?
Dataiku covers Visual Flow, Visual recipes, Code recipes and notebooks, Computation pushdown. Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering.

Answered from the vendors’ own pages

Dataiku: Is there a free version?

There is a free edition with limits on users and features, adequate for evaluation and personal work. Anything a team runs in production is a negotiated commercial agreement.

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.

Dataiku: Do I have to write code to use it?

No. That is the premise. An analyst can build a complete pipeline through visual recipes, and a data scientist can write Python next to it in the same Flow.

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.

Dataiku: Where does the computation actually run?

Wherever you connect it. Transformations are pushed down into the warehouse, database or Spark cluster where the data lives, which is efficient and also means the compute cost appears on that provider's bill rather than Dataiku's.

Immuta: Is Immuta still independent?

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

Dataiku: Can I export my work if we leave?

Code recipes are your code and leave with you. Visual recipes do not export as equivalent code, so the visual portion of a Flow has to be reimplemented, and that portion tends to be the majority in the projects where the platform succeeded best.

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.

Dataiku: Self-hosted or cloud?

Both are offered. Self-hosting gives control over data residency and networking and requires an administrator; the managed cloud removes that work and moves the constraint to what the vendor's environment supports.

Share

Related pages

Other head to heads