Softwr

Automation Integration · head to head

jBPM vs Trigger.dev

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
Trigger.dev logo

Trigger.dev

Automation Integration

Build and deploy fully managed AI agents and workflows

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.; Trigger.dev unclear scaling costs beyond included limits; pricing becomes complex beyond base plan features
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which jBPM and Trigger.dev actually diverge.

Attributes where jBPM and Trigger.dev differ
AttributejBPMTrigger.dev
Pricing modelOpen source, no licence feefreemium
PlatformsLinux, Windows, Docker, KubernetesWeb

Identical on both: starting price (Free), free tier (Yes), 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 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 Trigger.dev

Nothing recorded that jBPM does not also cover.

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

Trigger.dev

  • Job automation and workflow orchestrationnot jBPM
  • API-driven task schedulingnot jBPM
  • Background job processing for applicationsnot 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.

Trigger.dev

  • Unclear scaling costs beyond included limits; pricing becomes complex beyond base plan features
  • No published Enterprise pricing; requires contacting sales
  • HIPAA BAA compliance requires separate add-on request
  • Pro plan uses conditional language that obscures exact overage costs
  • Compute billing granularity is unclear; waits under 5 seconds still consume compute resources

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

Trigger.dev

Free
  • FreeFree
    • $5 monthly credits
    • 20 concurrent runs
    • 1 day log retention
  • Hobby$10/month
    • $10 monthly credits
    • 50 concurrent runs
    • 7 day log retention
  • Pro$50/month
    • $50 monthly credits
    • 200+ concurrent runs
    • 30 day log retention
  • Enterprise$null/month
    • Custom discounts
    • RBAC and SSO
    • SOC 2 reports

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 Trigger.dev if

  • You want to start without paying.
Trigger.dev review

Questions people ask

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

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.

Trigger.dev: Is there a free plan for Trigger.dev?

Yes, the Free plan offers $5 in monthly credits, 20 concurrent runs, 1 day log retention, and community support at no cost.

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.

Trigger.dev: What's the starting price for a paid plan?

The Hobby plan costs $10 per month USD and includes $10 monthly credits, 50 concurrent runs, and 7 day log retention.

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.

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 Trigger.dev

Keep looking

Other head to heads