Softwr

Databases · head to head

Immuta vs JMP

Immuta logo

Immuta

Databases

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

From
On request
Free plan
No
JMP logo

JMP

Machine Learning

Desktop statistical and design of experiments software from a SAS subsidiary

From
Free
Free plan
Yes

The short version

  • JMP starts at $1785/yr; Immuta prices on request.
  • Only Immuta lists attribute-based policy; only JMP lists custom design of experiments.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Immuta and JMP actually diverge.

Attributes where Immuta and JMP differ
AttributeImmutaJMP
Starting priceOn requestFree
Pricing modelQuoteSubscription
Free tierNoYes
PlatformsWeb, APImacOS, Windows
CategoryDatabasesMachine Learning

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 Immuta

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

Only in JMP

  • Custom design of experiments
  • Linked interactive graphics
  • Analysis platforms
  • Quality and process tools
  • Graph Builder
  • JSL scripting
  • Scoring code export
  • Predictive modelling in JMP Pro

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

JMP

  • Planning a physical experiment where each run is expensive, and the question is which twelve runs to perform rather than how to model data you already havenot Immuta
  • Process capability and control chart work in a manufacturing quality function that has to produce evidence for a customer or regulatornot Immuta
  • Exploratory analysis by an engineer or scientist who will not write code but needs more than a spreadsheetnot Immuta
  • Semiconductor, chemical and pharmaceutical development groups where JMP is already the shared language for reporting resultsnot 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

JMP

  • It is a desktop application holding the working table in memory, so a data set that outgrows the workstation has no in-place upgrade path, only a move to a different tool and a different skill set
  • There is no Linux build and no server edition for running analyses, so JMP cannot sit in a scheduled pipeline the way an R or Python script can, and recurring reports depend on a named person running them on a laptop
  • The predictive modelling capability most buyers mean when they call this machine learning software is in JMP Pro, a separate and more expensive licence, so the base product's price is not the price of the thing being evaluated
  • JSL is proprietary to JMP, so the scripts, add-ins and automation a group accumulates over a decade do not port anywhere and become sunk cost the moment anyone questions the renewal
  • Deployment ends at exported scoring code with no registry, monitoring or retraining, so a model that runs in production is maintained by another team in another language and steadily diverges from the version the analyst still has open

Pricing, plan by plan

Immuta

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

JMP

Free
  • TrialFree
    • 30-day trial
    • Full features
  • JMP$1,785/yr
    • Core JMP
    • Standard features

Which should you pick?

Choose Immuta if

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

Choose JMP if

  • You need custom design of experiments.
  • You want to start without paying.
  • You work on macOS, Windows.
  • You also want linked interactive graphics.

Questions people ask

Is Immuta or JMP better?
Neither clearly leads. Immuta starts at On request and JMP at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Immuta or JMP?
JMP has a free tier; the other does not. Paid plans start at On request for Immuta and Free for JMP.
Does Immuta or JMP run on more platforms?
Immuta runs on Web, API. JMP runs on macOS, Windows.
Can I use JMP for free?
Yes. JMP 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 JMP is typically brought in for.
What can Immuta do that JMP cannot?
Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering. JMP covers Custom design of experiments, Linked interactive graphics, Analysis platforms, Quality and process tools.

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.

JMP: Is JMP the same thing as SAS?

No. JMP is a separate desktop product from a SAS subsidiary, with its own interface, its own scripting language and its own licence. Knowing SAS does not transfer to it beyond the statistics.

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.

JMP: Do I need JMP Pro?

If you want cross validation, penalised regression, boosted trees or neural networks, yes. The base edition covers classical statistics, graphics and design of experiments well and stops short of predictive modelling.

Immuta: Is Immuta still independent?

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

JMP: Does it run on Linux?

No. Windows and macOS only, as an installed application.

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.

JMP: Can I put a JMP model into production?

Only by exporting the scoring formula as SQL, C, Python or similar and running it in another system. JMP itself does not serve, monitor or retrain models.

JMP: Who actually uses it?

Process and quality engineers, and scientists in R&D, particularly in semiconductor, chemicals, pharmaceutical and medical device work. It is not usually chosen by data engineering or platform teams.

Share

Related pages

Other head to heads