Softwr

Automation Integration · head to head

jBPM vs Kong Gateway

jBPM logo

jBPM

Automation Integration

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

From
Free
Rated
-
Kong Gateway logo

Kong Gateway

APIs

Open-source and cloud API gateway for managing microservices traffic

From
Free
Rated
-

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.; Kong Gateway the free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Kong Gateway covers API request routing.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Kong Gateway actually diverge.

Attributes where jBPM and Kong Gateway differ
AttributejBPMKong Gateway
Pricing modelOpen source, no licence feefreemium
PlatformsLinux, Windows, Docker, Kubernetesweb, linux, api
CategoryAutomation IntegrationAPIs
FoundedUnknown2017

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 Kong Gateway

  • API request routing
  • Plugin ecosystem
  • Developer portals
  • AI Gateway
  • Analytics and observability
  • SSO and audit logs

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

Kong Gateway

  • Routing and securing traffic across microservicesnot jBPM
  • Publishing internal or external developer portalsnot jBPM
  • Managing rate limits and authentication at the API edgenot jBPM
  • Gateway-level routing to multiple LLM providersnot 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.

Kong Gateway

  • The free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
  • Plus tier caps API requests at 1M/month before incurring per-million overage charges.
  • Enterprise pricing is custom and not published, making budgeting harder without sales contact.
  • Configuration and plugin management can require significant operational expertise to run at scale.

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

Kong Gateway

Free
  • Free TrialFree
    • 30-day enterprise functionality trial
    • Unlimited gateways
    • 30-day analytics retention
  • Plus$undefined/month
    • Up to 5 serverless, 2 hybrid, 2 dedicated cloud gateways
    • 1M API requests/month included
    • Up to 2 developer portals
  • Enterprise$undefined/month
    • Unlimited hybrid and dedicated cloud gateways
    • Unlimited developer portals
    • SSO and audit logs

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.

Choose Kong Gateway if

  • You need api request routing.
  • You want to start without paying.
  • You work on web, linux, api.
  • You also want plugin ecosystem.

Questions people ask

Is jBPM or Kong Gateway better?
Neither clearly leads. jBPM starts at Free and Kong Gateway at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Kong Gateway?
jBPM starts at Free and Kong Gateway at Free.
Does jBPM or Kong Gateway run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Kong Gateway runs on web, linux, api.
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 Kong Gateway is typically brought in for.
What can jBPM do that Kong Gateway cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Kong Gateway covers API request routing, Plugin ecosystem, Developer portals, AI Gateway.

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.

Kong Gateway: Is Kong Gateway free?

Kong's core gateway is open source and free to self-host. Kong Konnect, the managed cloud platform, offers a 30-day free trial before moving to paid Plus or custom Enterprise pricing.

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.

Kong Gateway: How is usage metered on the Plus plan?

The Plus plan includes 1M API requests per month, with additional usage billed at $200 per extra 1 million requests up to a 10M/month cap, plus per-gateway and per-LLM-model charges.

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.

Kong Gateway: What support is included?

Plus includes email support with a 2-business-day SLA, while Enterprise adds dedicated success managers and professional services.

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

Other head to heads