Softwr

Automation Integration · head to head

IBM MQ vs jBPM

IBM MQ logo

IBM MQ

Automation Integration

Transactional message queuing for systems where a lost message is a lost payment

From
$312/month
Rated
-
Full reviewWebsite
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

The short version

  • Only jBPM has a free tier, so it costs nothing to try first.
  • Each has a real cost: IBM MQ virtual Processor Core licensing is capacity-based, so an over-provisioned server is charged for cores the queue manager never uses, and consumption ratios differ between MQ and MQ Advanced.; 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.
  • They diverge on capability: IBM MQ covers Assured once-only delivery, jBPM covers BPMN 2.0 execution.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which IBM MQ and jBPM actually diverge.

Attributes where IBM MQ and jBPM differ
AttributeIBM MQjBPM
Starting price$312/monthFree
Pricing modelPer virtual processor core per monthOpen source, no licence fee
Free tierNoYes

Identical on both: platforms (Linux, Windows, Docker, Kubernetes), 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 IBM MQ

  • Assured once-only delivery
  • Multi-platform queue managers
  • Native high availability
  • Advanced Message Security
  • Managed File Transfer
  • MQ Telemetry

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

What people use each for

The jobs each tool is most often brought in to do.

IBM MQ

  • Core banking or payments where a message must participate in the same transaction as a database updatenot jBPM
  • A mainframe estate that needs reliable messaging between z/OS applications and distributed Linux servicesnot jBPM
  • Regulated file movement that must be auditable end to end, using Managed File Transfernot jBPM
  • Replacing bespoke retry and idempotency code in inter-system integrations with a queue that guarantees once-only deliverynot jBPM

jBPM

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

Where each one falls short

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

IBM MQ

  • Virtual Processor Core licensing is capacity-based, so an over-provisioned server is charged for cores the queue manager never uses, and consumption ratios differ between MQ and MQ Advanced.
  • Container licensing requires Kubernetes with the IBM License Service, so Podman or plain Docker deployments cannot use the optimised metric and pay materially more.
  • Distributed and z/OS platforms use different licensing models, and organisations running both routinely misapply one to the other, which surfaces as exposure at audit.
  • Operating MQ needs specialist skills that are increasingly scarce, and the pool of engineers who understand channel and queue manager administration is shrinking with every retirement.
  • IBM’s acquisition of Confluent in March 2026 puts MQ and Kafka under one vendor, which resolves the integration story but removes the competitive tension that kept renewal negotiations honest.

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.

Pricing, plan by plan

IBM MQ

$312/month
  • IBM MQ$312/month
    • Per Virtual Processor Core subscription
    • Minimum one year term
    • Assured once-only delivery
  • IBM MQ Advanced$583/month
    • Per Virtual Processor Core subscription
    • Advanced Message Security
    • Managed File Transfer
  • Pay as you go$undefined/month
    • Approximately 1.02 USD per Virtual Processor Core per hour
    • No annual commitment
    • Suited to variable or short-lived capacity

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

Which should you pick?

Choose IBM MQ if

  • You need assured once-only delivery.
  • You work on Linux, Windows, Docker, Kubernetes.
  • You also want multi-platform queue managers.
IBM MQ review

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

Questions people ask

Is IBM MQ or jBPM better?
Neither clearly leads. IBM MQ starts at $312/month and jBPM at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, IBM MQ or jBPM?
jBPM has a free tier; the other does not. Paid plans start at $312/month for IBM MQ and Free for jBPM.
Does IBM MQ or jBPM run on more platforms?
Both run on Linux, Windows, Docker, Kubernetes, so platform support will not decide this one for you.
Can I use jBPM for free?
Yes. jBPM has a free tier, so you can try it without paying. IBM MQ starts at $312/month.
What is IBM MQ best used for?
IBM MQ is most often used for core banking or payments where a message must participate in the same transaction as a database update, a mainframe estate that needs reliable messaging between z/os applications and distributed linux services, regulated file movement that must be auditable end to end, using managed file transfer, replacing bespoke retry and idempotency code in inter-system integrations with a queue that guarantees once-only delivery. Of those, core banking or payments where a message must participate in the same transaction as a database update and a mainframe estate that needs reliable messaging between z/os applications and distributed linux services are not what jBPM is typically brought in for.
What can IBM MQ do that jBPM cannot?
IBM MQ covers Assured once-only delivery, Multi-platform queue managers, Native high availability, Advanced Message Security. jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation.

Answered from the vendors’ own pages

IBM MQ: How is IBM MQ licensed?

By Virtual Processor Core subscription, around 312 US dollars per VPC per month for MQ and 583 for MQ Advanced, minimum one year.

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.

IBM MQ: Should we replace MQ with Kafka?

Only if you actually need a replayable log. MQ is a transactional queue; replacing it with Kafka usually means rebuilding transactional semantics in application code.

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.

IBM MQ: What does MQ Advanced add?

Advanced Message Security, Managed File Transfer, MQTT telemetry and quorum-based high availability.

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.

IBM MQ: Does container deployment change the cost?

Yes. Optimised container licensing needs Kubernetes with the IBM License Service; Podman or Docker deployments do not qualify.

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 IBM MQ

More on jBPM

Keep looking

Other head to heads