Softwr

Automation Integration · head to head

jBPM vs Split

jBPM logo

jBPM

Automation Integration

Long-running Java BPMN engine, now developed inside Apache KIE with commercial support from IBM

From
Free
Free plan
Yes
Split logo

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

  • jBPM is free; Split prices on request.
  • Only jBPM lists BPMN 2.0 execution; only Split lists feature flags with targeting.
  • Prices and features on this page were last checked on 20 November 2026.

How do jBPM and Split differ?

jBPM and Split differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which jBPM and Split actually diverge.

Attributes where jBPM and Split differ
AttributejBPMSplit
Starting priceFreeOn request
Pricing modelOpen source, no licence feeQuote
Free tierYesNo
PlatformsLinux, Windows, Self-hostedWeb, API, iOS, Android, Windows
CategoryAutomation IntegrationTesting

Which features does each one have?

They share no listed features; 8 appear only for jBPM 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 jBPM

  • BPMN 2.0 execution
  • Drools integration
  • Human task service
  • Kogito compilation
  • Process designer
  • Timers and signals
  • REST and Java APIs
  • Case management

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.

jBPM

  • A Java organisation already running jBPM 7 that needs to decide between the Apache KIE line, Kogito or migration awaynot Split
  • A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot Split
  • A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot Split
  • A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot Split

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot jBPM
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot jBPM
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot jBPM
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot jBPM

Where do jBPM and Split fall short?

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

jBPM

  • The project moved to the Apache Software Foundation as Apache KIE and is still in incubation, which is a weaker governance signal than a vendor-owned product and a harder case to make to an architecture board
  • The classic jBPM 7.x line has not had a Red Hat-sponsored release since 2023, so staying on it means running effectively frozen software while the development happens under a different name
  • Kogito is architecturally different from the classic runtime, using ahead-of-time compilation, so moving forward is a migration project rather than a version upgrade
  • Commercial support has shifted to IBM Business Automation Manager Open Editions, which means renegotiating with a different vendor under different terms than Red Hat customers signed
  • The tooling and workbench have long been the weakest part, and organisations routinely build their own process administration interfaces because the shipped ones are dated

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 jBPM and Split cost?

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

jBPM

Free
  • jBPMFree
    • Apache 2.0 licence with no usage restrictions
    • Full BPMN engine, human tasks and Drools integration
    • Community support via Apache KIE mailing lists

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

  • You need bpmn 2.0 execution.
  • You want to start without paying.
  • You work on Linux, Windows, Self-hosted.
  • You also want drools integration.

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 jBPM or Split better?
Neither clearly leads. jBPM 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, jBPM or Split?
jBPM has a free tier; the other does not. Paid plans start at Free for jBPM and On request for Split.
Does jBPM or Split run on more platforms?
jBPM runs on Linux, Windows, Self-hosted. Split runs on Web, API, iOS, Android, Windows.
Can I use jBPM for free?
Yes. jBPM has a free tier, so you can try it without paying. Split starts at On request.
What is jBPM best used for?
jBPM is most often used for a java organisation already running jbpm 7 that needs to decide between the apache kie line, kogito or migration away, a team that wants bpmn processes and drools business rules executing in one runtime without integrating two products, a government or banking system with long-running processes needing durable timers and full audit history at no licence cost, a quarkus estate adopting kogito to run compiled processes with container-appropriate startup times. Of those, a java organisation already running jbpm 7 that needs to decide between the apache kie line, kogito or migration away and a team that wants bpmn processes and drools business rules executing in one runtime without integrating two products are not what Split is typically brought in for.
What can jBPM do that Split cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

jBPM: Is jBPM dead?

No. Development continues as part of Apache KIE, with releases through 2025, but the Red Hat-sponsored 7.x line has been static since 2023.

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.

jBPM: Who provides commercial support?

IBM, through Business Automation Manager Open Editions, following the transition away from Red Hat Process Automation Manager as a growth product.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

jBPM: What is Kogito?

The cloud-native successor that compiles processes ahead of time for Quarkus and Spring Boot, architecturally different from the classic jBPM runtime.

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.

jBPM: Does it cost anything?

No. It is Apache 2.0 licensed with no fee. Costs are support contracts and the engineering effort to run it.

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.

Share

Related pages

Other head to heads