Softwr

Automation Integration · head to head

Integromat vs Kogito

Integromat logo

Integromat

Automation Integration

Automate your workflow

From
Free
Rated
-
Full reviewWebsite
Kogito logo

Kogito

Automation Integration

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Integromat the free plan enforces a 15 minute minimum interval between runs, so nothing near real time is possible without paying; 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.
  • They diverge on capability: Integromat covers Visual workflow builder, Kogito covers Build-time code generation.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Integromat and Kogito actually diverge.

Attributes where Integromat and Kogito differ
AttributeIntegromatKogito
Pricing modelfreemiumOpen source, no licence fee
PlatformsWeb, ApiLinux, Docker, Kubernetes
Founded2013Unknown

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 Integromat

  • Visual workflow builder
  • Webhooks
  • Data transformation
  • Error handling
  • Conditional logic
  • Scheduling
  • Team collaboration
  • 1000+ apps

Only in Kogito

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

What people use each for

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

Integromat

  • workflow automationnot Kogito
  • integration between appsnot Kogito
  • task automationnot Kogito

Kogito

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

Where each one falls short

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

Integromat

  • The free plan enforces a 15 minute minimum interval between runs, so nothing near real time is possible without paying
  • Free is limited to 2 active scenarios, a 5 MB file size and 7 days of execution logs
  • Billing is per credit where each module action counts as one, so a scenario with many steps consumes credits far faster than its run count suggests
  • Make API access requires a paid plan
  • Priority execution and full text log search are Pro features
  • Overage protection is Enterprise only, so cheaper plans can run up charges

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.

Pricing, plan by plan

Integromat

Free
  • FreeFree
    • 1000 credits monthly
    • basic workflow builder
    • access to 3000+ apps
  • Core$9/month
    • 10k credits
    • unlimited active scenarios
    • scheduled scenarios down to the minute
  • Pro$16/month
    • 10k credits
    • priority execution
    • custom variables
  • Teams$29/month
    • 10k credits
    • team collaboration
    • team roles

Kogito

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

Which should you pick?

Choose Integromat if

  • You need visual workflow builder.
  • You want to start without paying.
  • You work on Web, Api.
  • You also want webhooks.
Integromat review

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

Questions people ask

Is Integromat or Kogito better?
Neither clearly leads. Integromat starts at Free and Kogito at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Integromat or Kogito?
Integromat starts at Free and Kogito at Free.
Does Integromat or Kogito run on more platforms?
Integromat runs on Web, Api. Kogito runs on Linux, Docker, Kubernetes.
Can I use Integromat for free?
Both have a free tier, so you can try either at no cost before committing.
What is Integromat best used for?
Integromat is most often used for workflow automation, integration between apps, task automation. Of those, workflow automation and integration between apps are not what Kogito is typically brought in for.
What can Integromat do that Kogito cannot?
Integromat covers Visual workflow builder, Webhooks, Data transformation, Error handling. Kogito covers Build-time code generation, Quarkus and Spring Boot support, DMN decision services, Drools rules engine.

Answered from the vendors’ own pages

Integromat: What is the free tier for Make?

Make's free tier provides 1,000 credits monthly, access to 3,000+ apps, a basic no-code workflow builder, and a 15-minute minimum interval between scenario runs.

Source
Kogito: Is Kogito still maintained?

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

Integromat: Can I save money with annual billing on Make?

Yes, Make offers 15% or more savings when paying annually instead of monthly billing.

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.

Integromat: How does Make's credit system work?

Each module action in Make consumes credits, with most basic actions using one credit per execution. Credits expire monthly for monthly plans or annually for yearly subscriptions.

Source
Kogito: Does it need Quarkus?

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

Kogito: Is there commercial support?

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

Share

Related pages

More on Integromat

More on Kogito

Keep looking

Other head to heads