Automation Integration · head to head
Flowable vs Split

Flowable
Automation Integration
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
- From
- Free
- Free plan
- Yes

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Flowable is free; Split prices on request.
- Only Flowable lists CMMN case management; only Split lists feature flags with targeting.
- 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 20 November 2026.
How do Flowable and Split differ?
Flowable and Split differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Flowable and Split actually diverge.
Identical on both: pricing model (Quote).
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 8 appear only for Flowable and 8 only for Split. 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 Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
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 Split
- A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Split
- A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Split
- A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Flowable
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Flowable
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Flowable
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Flowable
Where do Flowable and Split 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
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Flowable and Split cost?
Flowable is free to use; Split 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
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
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 Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Flowable or Split better?
- Neither clearly leads. Flowable starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Flowable or Split?
- Flowable has a free tier; the other does not. Paid plans start at Free for Flowable and On request for Split.
- Does Flowable or Split run on more platforms?
- Flowable runs on Linux, Windows, Self-hosted, Web. Split runs on Web, API, iOS, Android, Windows.
- Can I use Flowable for free?
- Yes. Flowable has a free tier, so you can try it without paying. Split 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 Split is typically brought in for.
- What can Flowable do that Split cannot?
- Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
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.
Split: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
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.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Flowable: What does Flowable Enterprise cost?
Nothing is published. It is quoted per deployment by the vendor.
Split: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
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.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
Other head to heads
- Flowable vs jBPM
- Flowable vs Activiti
- Flowable vs Camunda
- Flowable vs Temporal
- Flowable vs Nintex
- Flowable vs Kogito
- Flowable vs Airbyte
- Flowable vs Meltano
- Flowable vs Windmill
- Flowable vs Hatchet
- Flowable vs Nango
- Flowable vs RudderStack
- Flowable vs Mage AI
- Flowable vs Parabola
- Flowable vs Paragon
- Flowable vs Prefect
- Flowable vs Automation Anywhere
- Flowable vs CrewAI
- Flowable vs GrowthBook
- Flowable vs Kameleoon
- Flowable vs Eppo
- Flowable vs Katalon
- Flowable vs Selenium
- Flowable vs Sauce Labs
- Flowable vs TestRail
- Flowable vs Applitools
- Flowable vs QA Wolf
- Flowable vs BrowserStack
- Flowable vs CircleCI
- Flowable vs Xray Test Management
- Flowable vs Ranorex
- Flowable vs Detox
- Flowable vs Jest
- Flowable vs JUnit
- Flowable vs TestNG
- Flowable vs Tricentis Tosca
- Split vs jBPM
- Split vs Activiti
- Split vs Camunda
- Split vs Temporal
- Split vs Nintex
- Split vs Kogito
- Split vs Airbyte
- Split vs Meltano
- Split vs Windmill
- Split vs Hatchet
- Split vs Nango
- Split vs RudderStack
- Split vs Mage AI
- Split vs Parabola
- Split vs Paragon
- Split vs Prefect
- Split vs Automation Anywhere
- Split vs CrewAI
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs QA Wolf
- Split vs BrowserStack
- Split vs CircleCI
- Split vs Xray Test Management
- Split vs Ranorex
- Split vs Detox
- Split vs Jest
- Split vs JUnit
- Split vs TestNG
- Split vs Tricentis Tosca
