Automation Integration · head to head
Flowable vs Kong Gateway

Flowable
Automation Integration
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
- From
- Free
- Rated
- -

Kong Gateway
APIs
Open-source and cloud API gateway for managing microservices traffic
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Flowable the open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.; Kong Gateway the free open-source gateway lacks the analytics, portals, and support of the paid Konnect tiers.
- They diverge on capability: Flowable covers BPMN 2.0 engine, 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 Flowable and Kong Gateway actually diverge.
| Attribute | Flowable | Kong Gateway |
|---|---|---|
| Pricing model | quote | freemium |
| Platforms | Linux, Windows, Docker, Kubernetes, Cloud | web, linux, api |
| Category | Automation Integration | APIs |
| Founded | Unknown | 2017 |
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 Flowable
- BPMN 2.0 engine
- CMMN case management
- DMN decision tables
- Spring Boot integration
- Modelling studio
- Task and case application
- REST APIs
- History and audit
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.
Flowable
- An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Kong Gateway
- A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Kong Gateway
- A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Kong Gateway
- A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Kong Gateway
Kong Gateway
- Routing and securing traffic across microservicesnot Flowable
- Publishing internal or external developer portalsnot Flowable
- Managing rate limits and authentication at the API edgenot Flowable
- Gateway-level routing to multiple LLM providersnot Flowable
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Flowable
- The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it.
- It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical.
- Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
- The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one.
- Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe.
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
Flowable
Free- Flowable Open SourceFree
- Apache 2.0 licensed BPMN, CMMN and DMN engines
- Embeddable Java library or standalone apps
- No modelling studio or enterprise applications
- Flowable Enterprise$undefined/year
- Modelling studio, work application and admin console
- Connectors, forms and advanced identity management
- Support with SLA and version maintenance
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 Flowable if
- You need bpmn 2.0 engine.
- You want to start without paying.
- You work on Linux, Windows, Docker, Kubernetes, Cloud.
- You also want cmmn case management.
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 Flowable or Kong Gateway better?
- Neither clearly leads. Flowable 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, Flowable or Kong Gateway?
- Flowable starts at Free and Kong Gateway at Free.
- Does Flowable or Kong Gateway run on more platforms?
- Flowable runs on Linux, Windows, Docker, Kubernetes, Cloud. Kong Gateway runs on web, linux, api.
- Can I use Flowable for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Flowable best used for?
- Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Kong Gateway is typically brought in for.
- What can Flowable do that Kong Gateway cannot?
- Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Kong Gateway covers API request routing, Plugin ecosystem, Developer portals, AI Gateway.
Answered from the vendors’ own pages
Flowable: Is Flowable open source?
Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.
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.
SourceFlowable: How does it relate to Activiti and jBPM?
The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.
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.
SourceFlowable: What does Flowable Enterprise cost?
Nothing is published. It is quoted per deployment by the vendor.
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.
SourceFlowable: Why choose it over Camunda?
CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.
Related pages
More on Kong Gateway
Other head to heads
- Flowable vs Temporal
- Flowable vs Nintex
- Flowable vs jBPM
- Flowable vs Activiti
- Flowable vs Camunda
- Flowable vs Kogito
- Flowable vs Airbyte
- Flowable vs Nango
- Flowable vs Windmill
- Flowable vs Hatchet
- Flowable vs Meltano
- Flowable vs RudderStack
- Flowable vs HighLevel
- Flowable vs Grouparoo
- Flowable vs Hevo Data
- Flowable vs HighByte Intelligence Hub
- Flowable vs IBM MQ
- Flowable vs Tyk
- Flowable vs Moesif
- Flowable vs Treblle
- Flowable vs Convoy
- Flowable vs Janus Gateway
- Flowable vs Spring Cloud Gateway
- Flowable vs Gravitee
- Flowable vs Strapi
- Flowable vs WSO2 API Manager
- Flowable vs AWS API Gateway
- Flowable vs GraphQL Apollo
- Flowable vs Appwrite
- Flowable vs Payload CMS
- Flowable vs Portkey
- Flowable vs Prisma
- Flowable vs RapidAPI
- Flowable vs REST Client VSCode
- Flowable vs Rutter
- Kong Gateway vs Temporal
- Kong Gateway vs Nintex
- Kong Gateway vs jBPM
- Kong Gateway vs Activiti
- Kong Gateway vs Camunda
- Kong Gateway vs Kogito
- Kong Gateway vs Airbyte
- Kong Gateway vs Nango
- Kong Gateway vs Windmill
- Kong Gateway vs Hatchet
- Kong Gateway vs Meltano
- Kong Gateway vs RudderStack
- Kong Gateway vs HighLevel
- Kong Gateway vs Grouparoo
- Kong Gateway vs Hevo Data
- Kong Gateway vs HighByte Intelligence Hub
- Kong Gateway vs IBM MQ
- Kong Gateway vs Tyk
- Kong Gateway vs Moesif
- Kong Gateway vs Treblle
- Kong Gateway vs Convoy
- Kong Gateway vs Janus Gateway
- Kong Gateway vs Spring Cloud Gateway
- Kong Gateway vs Gravitee
- Kong Gateway vs Strapi
- Kong Gateway vs WSO2 API Manager
- Kong Gateway vs AWS API Gateway
- Kong Gateway vs GraphQL Apollo
- Kong Gateway vs Appwrite
- Kong Gateway vs Payload CMS
- Kong Gateway vs Portkey
- Kong Gateway vs Prisma
- Kong Gateway vs RapidAPI
- Kong Gateway vs REST Client VSCode
- Kong Gateway vs Rutter
