Softwr

Automation Integration · head to head

Flowable vs Immuta

Flowable logo

Flowable

Automation Integration

Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti

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

  • Flowable is free; Immuta prices on request.
  • Only Flowable lists BPMN 2.0 engine; only Immuta lists attribute-based policy.
  • Where Flowable falls short: enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
  • Prices and features on this page were last checked on 31 August 2026.

How do Flowable and Immuta differ?

Flowable and Immuta differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Flowable and Immuta actually diverge.

Attributes where Flowable and Immuta differ
AttributeFlowableImmuta
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, Windows, Self-hosted, WebWeb, API
CategoryAutomation IntegrationDatabases

Identical on both: pricing model (Quote).

Which features does each one have?

They share no listed features; 8 appear only for Flowable and 8 only for Immuta. 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 Flowable

  • BPMN 2.0 engine
  • CMMN case management
  • DMN decision tables
  • Spring Boot integration
  • Modelling studio
  • Task and case application
  • REST APIs
  • History and audit

Only in Immuta

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

What is each one used for?

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

Flowable

  • An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Immuta
  • A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Immuta
  • A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Immuta
  • A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Immuta

Immuta

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

Where do Flowable and Immuta fall short?

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

Flowable

  • The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it
  • It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical
  • Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives
  • The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one
  • Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe

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

How much do Flowable and Immuta cost?

Flowable is free to use; Immuta is priced on request. Plan by plan below, from each vendor's own pricing page.

Flowable

Free
  • Flowable Open SourceFree
    • Apache 2.0 licensed BPMN, CMMN and DMN engines
    • Embeddable Java library or standalone apps
    • No modelling studio or enterprise applications
  • Flowable EnterpriseOn request
    • Modelling studio, work application and admin console
    • Connectors, forms and advanced identity management
    • Support with SLA and version maintenance

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

  • You need bpmn 2.0 engine.
  • You want to start without paying.
  • You work on Linux, Windows, Self-hosted, Web.
  • You also want cmmn case management.

Choose Immuta if

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

Questions people ask

Is Flowable or Immuta better?
Neither clearly leads. Flowable 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, Flowable or Immuta?
Flowable has a free tier; the other does not. Paid plans start at Free for Flowable and On request for Immuta.
Does Flowable or Immuta run on more platforms?
Flowable runs on Linux, Windows, Self-hosted, Web. Immuta runs on Web, API.
Can I use Flowable for free?
Yes. Flowable has a free tier, so you can try it without paying. Immuta starts at On request.
What is Flowable best used for?
Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Immuta is typically brought in for.
What can Flowable do that Immuta cannot?
Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering.

Answered from the vendors’ own pages

Flowable: Is Flowable open source?

Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.

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.

Flowable: How does it relate to Activiti and jBPM?

The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.

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.

Flowable: What does Flowable Enterprise cost?

Nothing is published. It is quoted per deployment by the vendor.

Immuta: Is Immuta still independent?

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

Flowable: Why choose it over Camunda?

CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.

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.

Share

Related pages

Other head to heads