Softwr

Automation Integration · head to head

jBPM vs NATS

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
NATS logo

NATS

Databases

High-performance messaging system for cloud-native applications

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.; NATS core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • They diverge on capability: jBPM covers BPMN 2.0 execution, NATS covers Very low latency.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and NATS actually diverge.

Attributes where jBPM and NATS differ
AttributejBPMNATS
PlatformsLinux, Windows, Docker, KubernetesLinux, macOS, Windows, Docker, Kubernetes
CategoryAutomation IntegrationDatabases

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 NATS

  • Very low latency
  • JetStream
  • Single binary
  • Request-reply

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

NATS

  • Service-to-service messaging where latency is the binding constraintnot jBPM
  • Edge and IoT messaging where a lightweight broker mattersnot jBPM
  • Replacing a heavier broker when the workload does not need its guaranteesnot 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.

NATS

  • Core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • JetStream adds the durability but also the operational complexity NATS is chosen to avoid
  • A much smaller ecosystem than Kafka or RabbitMQ, with fewer connectors and integrations
  • Fewer people know it, so hiring and existing organisational knowledge favour the alternatives

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

NATS

Free
  • NATSFree
    • Full functionality
    • No usage limits
    • Community support

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

  • You need very low latency.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Kubernetes.
  • You also want jetstream.
NATS review

Questions people ask

Is jBPM or NATS better?
Neither clearly leads. jBPM starts at Free and NATS at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or NATS?
jBPM starts at Free and NATS at Free.
Does jBPM or NATS run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. NATS runs on Linux, macOS, Windows, Docker, Kubernetes.
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 NATS is typically brought in for.
What can jBPM do that NATS cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. NATS covers Very low latency, JetStream, Single binary, Request-reply.

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.

NATS: Is NATS free?

Yes, open source and CNCF-graduated. Synadia sells a managed service.

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.

NATS: Does NATS persist messages?

Core NATS does not — it is fire-and-forget. JetStream adds persistence, streaming and replay when you need them.

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.

NATS: NATS or Kafka?

NATS is far lighter and lower latency, and much simpler to run. Kafka is the answer when you need a durable replayable log and a large connector ecosystem.

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 NATS

Keep looking

Other head to heads