Softwr

Automation Integration · head to head

jBPM vs Node-RED

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
Node-RED logo

Node-RED

Smart Home

Flow-based programming tool for IoT and home automation

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.; Node-RED the Node-RED editor ships unsecured: anyone who can reach its IP address can open the editor and deploy changes until adminAuth is configured
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Node-RED covers Visual Editor.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Node-RED actually diverge.

Attributes where jBPM and Node-RED differ
AttributejBPMNode-RED
Pricing modelOpen source, no licence feeopen-source
PlatformsLinux, Windows, Docker, KubernetesNode.js, Docker, Cloud, Edge devices
CategoryAutomation IntegrationSmart Home
FoundedUnknown2013

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

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 Node-RED

  • Visual Editor
  • Flow-Based Programming
  • Extensible
  • HTTP Integration
  • MQTT
  • REST API
  • WebSocket
  • Database

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

Node-RED

  • Low-code event-driven application developmentnot jBPM
  • IoT and device integration workflowsnot jBPM
  • Visual programming for server-side integrationsnot 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.

Node-RED

  • The Node-RED editor ships unsecured: anyone who can reach its IP address can open the editor and deploy changes until adminAuth is configured
  • HTTPS is off by default and must be enabled through the https setting
  • HTTP endpoints and dashboards exposed by flows are unauthenticated unless httpNodeAuth is configured separately
  • All three security layers are optional additions the administrator must implement by editing the settings file

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

Node-RED

Free
  • Community EditionFree
    • Visual editor
    • Extensible
    • REST API

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 Node-RED if

  • You need visual editor.
  • You want to start without paying.
  • You work on Node.js, Docker, Cloud, Edge devices.
  • You also want flow-based programming.
Node-RED review

Questions people ask

Is jBPM or Node-RED better?
Neither clearly leads. jBPM starts at Free and Node-RED at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Node-RED?
jBPM starts at Free and Node-RED at Free.
Does jBPM or Node-RED run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Node-RED runs on Node.js, Docker, Cloud, Edge devices.
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 Node-RED is typically brought in for.
What can jBPM do that Node-RED cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Node-RED covers Visual Editor, Flow-Based Programming, Extensible, HTTP Integration.

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.

Node-RED: Is Node-RED free?

Yes, Node-RED is completely free and open source. It is available under the MIT License through GitHub and npm package manager. The project is maintained by the OpenJS Foundation.

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.

Node-RED: Does Node-RED offer commercial support?

Node-RED itself is free and community-supported. FlowFuse, Inc. was founded in 2021 as a separate commercial entity offering enterprise support and a professional platform for Node-RED deployment, but FlowFuse is not Node-RED.

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.

Node-RED: What is Node-RED pricing model?

Node-RED has no pricing model. It is completely free open source software. Commercial support and hosting options may be available separately through third-party providers like FlowFuse, but the core software is not sold.

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.

Share

Related pages

More on jBPM

More on Node-RED

Keep looking

Other head to heads