Softwr

Automation Integration · head to head

jBPM vs Presto

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

Presto

Databases

The Meta-lineage distributed SQL query engine, distinct from the Trino fork

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.; Presto the original creators and most of the active contributor base left for Trino in 2020, so Presto has the smaller community, fewer connectors and slower feature delivery of the two branches.
  • They diverge on capability: jBPM covers BPMN 2.0 execution, Presto covers Federated querying.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Presto actually diverge.

Attributes where jBPM and Presto differ
AttributejBPMPresto
PlatformsLinux, Windows, Docker, KubernetesLinux, 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 Presto

  • Federated querying
  • In-memory execution
  • Open table format support
  • Presto C++ workers
  • ANSI SQL
  • Pluggable connectors

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

Presto

  • An existing PrestoDB estate that needs continued upgrades rather than a migration to Trinonot jBPM
  • A team buying IBM watsonx.data, where Presto is the underlying query enginenot jBPM
  • Joining a Hive or Iceberg lake to an operational PostgreSQL database in one query without an ETL stepnot jBPM
  • Very large scale interactive SQL where the Meta-tested branch is a specific requirementnot 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.

Presto

  • The original creators and most of the active contributor base left for Trino in 2020, so Presto has the smaller community, fewer connectors and slower feature delivery of the two branches.
  • Documentation, tutorials and Stack Overflow answers for the two projects are frequently mixed up, and a solution written for Trino often does not apply, which costs real debugging time.
  • It is a query engine with no storage of its own, so query performance is dictated by your file layout, partitioning and statistics, and a badly organised lake makes Presto look slow.
  • Memory-bound execution means a single large join can fail the whole query rather than spilling gracefully, and tuning cluster memory settings is a persistent operational chore.
  • Commercial support has consolidated into IBM since the Ahana acquisition, so the independent vendor market that once existed around Presto is largely gone.

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

Presto

Free
  • PrestoFree
    • Apache 2.0 licence
    • Presto Foundation governance under the Linux Foundation
    • No node or query limits

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

  • You need federated querying.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want in-memory execution.
Presto review

Questions people ask

Is jBPM or Presto better?
Neither clearly leads. jBPM starts at Free and Presto at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, jBPM or Presto?
jBPM starts at Free and Presto at Free.
Does jBPM or Presto run on more platforms?
jBPM runs on Linux, Windows, Docker, Kubernetes. Presto runs on Linux, 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 Presto is typically brought in for.
What can jBPM do that Presto cannot?
jBPM covers BPMN 2.0 execution, Drools integration, Human task service, Kogito compilation. Presto covers Federated querying, In-memory execution, Open table format support, Presto C++ workers.

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.

Presto: Is this Presto or Trino?

This is PrestoDB, the branch that stayed at Facebook and moved to the Linux Foundation. Trino is the 2020 fork by the original creators.

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.

Presto: Which should I choose for a new project?

Trino, in most cases. It has the larger community, more connectors and more commercial options.

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.

Presto: Who maintains Presto now?

Principally Meta, Uber and IBM, which acquired the Presto vendor Ahana in 2023.

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.

Presto: Is it still actively released?

Yes, releases continue on a regular cadence under the Presto Foundation.

Share

Related pages

More on jBPM

More on Presto

Keep looking

Other head to heads