Softwr

Automation Integration · head to head

jBPM vs Salesforce Flows

jBPM logo

jBPM

Automation Integration

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

From
Free
Rated
-
Full reviewWebsite
Salesforce Flows logo

Salesforce Flows

Automation Integration

Automation inside Salesforce

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Salesforce Flows not suitable for highly complex scenarios with intricate decision-making or bulk data processing
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Salesforce Flows covers Visual flow builder.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Salesforce Flows actually diverge.

Attributes where jBPM and Salesforce Flows differ
AttributejBPMSalesforce Flows
Pricing modelOpen source, no licence feeUnknown
PlatformsLinux, Windows, Docker, KubernetesSalesforce Cloud, Web, Mobile
FoundedUnknown1999

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Automation Integration).

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 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 Salesforce Flows

  • Visual flow builder
  • Approvals
  • Scheduled actions
  • Screen flows
  • Multi-step workflows
  • Conditional logic
  • Error handling
  • Salesforce native

What people use each 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 Salesforce Flows
  • A team that wants BPMN processes and Drools business rules executing in one runtime without integrating two productsnot Salesforce Flows
  • A government or banking system with long-running processes needing durable timers and full audit history at no licence costnot Salesforce Flows
  • A Quarkus estate adopting Kogito to run compiled processes with container-appropriate startup timesnot Salesforce Flows

Salesforce Flows

  • Workflow Automationnot jBPM
  • Data Integrationnot jBPM
  • Process Automationnot jBPM
  • App Integrationnot jBPM
  • API Connectivitynot jBPM

Where each one falls 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.

Salesforce Flows

  • Not suitable for highly complex scenarios with intricate decision-making or bulk data processing
  • No automatic record locking, causing conflicts when multiple users update same records
  • Limited error handling compared to Apex
  • Requires Enterprise edition or higher for full capabilities
  • Auto-launched Flows cannot display screens to users
  • Complex dependency management and configuration challenges when deploying between environments

Pricing, plan by plan

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

Salesforce Flows

Free
  • Salesforce FreeFree
    • 2 user licenses
    • Basic workflows
    • Limited automation
  • Starter$25/user/month
    • Sales flows
    • Lead routing
    • Email marketing analytics
  • Professional$100/user/month
    • Sales quoting
    • Forecasting
    • AppExchange access
  • Enterprise$165/user/month
    • Full Flow Builder
    • Custom objects
    • Sandboxes

Which should you pick?

Choose jBPM if

  • You need bpmn 2.0 execution.
  • You want to start without paying.
  • You work on Linux, Windows, Docker, Kubernetes.
  • You also want drools integration.
jBPM review

Choose Salesforce Flows if

  • You need visual flow builder.
  • You want to start without paying.
  • You work on Salesforce Cloud, Web, Mobile.
  • You also want approvals.
Salesforce Flows review

Questions people ask

Is jBPM or Salesforce Flows better?
Neither clearly leads. jBPM starts at Free and Salesforce Flows at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Salesforce Flows?
jBPM starts at Free and Salesforce Flows at Free.
Does jBPM or Salesforce Flows run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Salesforce Flows runs on Salesforce Cloud, Web, Mobile.
Can I use jBPM for free?
Both have a free tier, so you can try either at no cost before committing.
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 Salesforce Flows is typically brought in for.
What can jBPM do that Salesforce Flows cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Salesforce Flows covers Visual flow builder, Approvals, Scheduled actions, Screen flows.

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.

Salesforce Flows: Which Salesforce editions include Flows?

Salesforce Flow Builder is included in Enterprise Edition ($165/user/month) and above. Professional Edition lacks advanced automation capabilities and Flow Builder access. Starter and lower editions have limited Flow support.

Source
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.

Salesforce Flows: What are the main limitations of Salesforce Flows?

Flows are limited by DML operations (max 150 data elements that modify data), SOQL queries (max 100 data elements that retrieve data), and are not designed for bulk processing. Auto-launched Flows do not support screens and have limited error handling compared to Apex.

Source
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.

Salesforce Flows: Can Salesforce Flows integrate with external systems?

Yes, through MuleSoft connectors and Salesforce API Catalog. Pre-built connectors exist for systems like Asana, and admins can create custom connectors. Complex integrations may still require Apex or third-party platforms.

Source
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.

Salesforce Flows: When was Salesforce Flow redesigned?

Flow Builder was introduced in Spring '19 as a replacement for the previous Flow Designer, providing a more familiar interface similar to other Salesforce Lightning Builder tools.

Source
Share

Related pages

More on jBPM

More on Salesforce Flows

Keep looking

Other head to heads