Softwr

Automation Integration · head to head

Kogito vs Merge

Kogito logo

Kogito

Automation Integration

Cloud-native business automation for Quarkus, now an Apache KIE component

From
Free
Rated
-
Full reviewWebsite
Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Kogito kogito is a developer framework, not a product, so there is no equivalent of Camunda Operate for business users and any process monitoring interface has to be built or bought separately.; Merge cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • They diverge on capability: Kogito covers Build-time code generation, Merge covers Unified API.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Kogito and Merge actually diverge.

Attributes where Kogito and Merge differ
AttributeKogitoMerge
Pricing modelOpen source, no licence feeusage-based
PlatformsLinux, Docker, KubernetesApi
FoundedUnknown2020

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 Kogito

  • Build-time code generation
  • Quarkus and Spring Boot support
  • DMN decision services
  • Drools rules engine
  • Serverless workflow
  • Kubernetes operator

Only in Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

What people use each for

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

Kogito

  • A Quarkus microservice that must expose a DMN decision model as a REST endpoint with millisecond start-upnot Merge
  • Serverless deployment of business rules where a traditional BPM server would be far too heavynot Merge
  • A Red Hat shop that wants the upstream of Red Hat process automation with the option of a supported build laternot Merge
  • Replacing hand-coded conditional logic with DMN tables that business analysts can review and amendnot Merge

Merge

  • Workflow Automationnot Kogito
  • Data Integrationnot Kogito
  • Process Automationnot Kogito
  • App Integrationnot Kogito
  • API Connectivitynot Kogito

Where each one falls short

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

Kogito

  • Kogito is a developer framework, not a product, so there is no equivalent of Camunda Operate for business users and any process monitoring interface has to be built or bought separately.
  • Long-running stateful processes need external persistence and messaging that you configure and operate yourself, which removes much of the convenience a BPM server normally provides.
  • It sits inside the Apache KIE incubator, and incubating status means graduation is not guaranteed and the project name and artefact coordinates have already changed once.
  • Red Hat is by far the dominant contributor despite ASF stewardship, so the roadmap follows Red Hat product priorities rather than community demand.
  • Documentation is spread across legacy JBoss sites, the old Kogito site and the new Apache KIE site, and search results routinely land on outdated versions, which costs real time during adoption.

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

Pricing, plan by plan

Kogito

Free
  • KogitoFree
    • Apache 2.0 licence
    • Apache KIE incubating project
    • No usage limits

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/month
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2500/month
    • Unlimited accounts
    • Priority support
    • SLA
  • Enterprise$undefined/month
    • Dedicated support
    • Custom contracts
    • Advanced security

Which should you pick?

Choose Kogito if

  • You need build-time code generation.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes.
  • You also want quarkus and spring boot support.
Kogito review

Choose Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on Api.
  • You also want hris integrations.
Merge review

Questions people ask

Is Kogito or Merge better?
Neither clearly leads. Kogito starts at Free and Merge at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kogito or Merge?
Kogito starts at Free and Merge at Free.
Does Kogito or Merge run on more platforms?
Kogito runs on Linux, Docker, Kubernetes. Merge runs on Api.
Can I use Kogito for free?
Both have a free tier, so you can try either at no cost before committing.
What is Kogito best used for?
Kogito is most often used for a quarkus microservice that must expose a dmn decision model as a rest endpoint with millisecond start-up, serverless deployment of business rules where a traditional bpm server would be far too heavy, a red hat shop that wants the upstream of red hat process automation with the option of a supported build later, replacing hand-coded conditional logic with dmn tables that business analysts can review and amend. Of those, a quarkus microservice that must expose a dmn decision model as a rest endpoint with millisecond start-up and serverless deployment of business rules where a traditional bpm server would be far too heavy are not what Merge is typically brought in for.
What can Kogito do that Merge cannot?
Kogito covers Build-time code generation, Quarkus and Spring Boot support, DMN decision services, Drools rules engine. Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations.

Answered from the vendors’ own pages

Kogito: Is Kogito still maintained?

Yes. It is an Apache KIE incubating project with active commits, with Red Hat as the dominant contributor.

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
Kogito: How does it differ from jBPM?

Kogito compiles process and rule definitions into application code at build time; jBPM was a runtime engine that loads definitions.

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
Kogito: Does it need Quarkus?

It is designed for Quarkus and supports Spring Boot; both are Java frameworks rather than a standalone server.

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

Kogito: Is there commercial support?

Not from Apache. Red Hat sells supported builds of this lineage as part of its subscriptions.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

Share

Related pages

More on Kogito

More on Merge

Keep looking

Other head to heads