Automation Integration · head to head
Kogito vs Thredd

Kogito
Automation Integration
Cloud-native business automation for Quarkus, now an Apache KIE component
- From
- Free
- Free plan
- Yes

Thredd
APIs
Issuer processing platform for fintechs and digital banks, formerly Global Processing Services
- From
- On request
- Free plan
- No
The short version
- Kogito is free; Thredd prices on request.
- Only Kogito lists build-time code generation; only Thredd lists issuer processing.
- Where Thredd falls short: pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.
- Prices and features on this page were last checked on 20 November 2026.
How do Kogito and Thredd differ?
Kogito and Thredd differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Kogito and Thredd actually diverge.
Not yet recorded: founded for Thredd.
Which features does each one have?
They share no listed features; 6 appear only for Kogito and 6 only for Thredd. 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 Thredd
- Issuer processing
- Multi-country reach
- Scheme certification
- Programme support across verticals
- High platform availability
- Global office footprint
What is each one used 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 Thredd
- Serverless deployment of business rules where a traditional BPM server would be far too heavynot Thredd
- A Red Hat shop that wants the upstream of Red Hat process automation with the option of a supported build laternot Thredd
- Replacing hand-coded conditional logic with DMN tables that business analysts can review and amendnot Thredd
Thredd
- A digital bank or fintech needing issuer processing across many countries under one contractnot Kogito
- A BNPL, lending or crypto product needing certified card processing behind its own brandnot Kogito
- A company that finds outdated Global Processing Services (GPS) material and needs to confirm it is now Threddnot Kogito
- An embedded finance platform wanting a processor already integrated with core banking systems such as Mambunot Kogito
Where do Kogito and Thredd fall short?
Thredd's most cited limit: pricing is entirely unpublished, so cost comparison against competing processors requires a sales process. 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
Thredd
- Pricing is entirely unpublished, so cost comparison against competing processors requires a sales process
- The 2023 rebrand from GPS to Thredd means research under either name alone can miss relevant material, and partner or press references before 2023 will still say GPS
- Issuer processing does not include the banking licence itself, so a fintech still needs a separate BIN sponsor or bank partner, adding a second relationship to manage
- As shared infrastructure behind many fintech brands, an outage or processing delay at Thredd becomes a simultaneous incident for every programme running on it, with limited visibility for any single customer into root cause
- Its verticals span crypto, BNPL and remittance broadly, so depth of specialist support in any one vertical may be thinner than a processor focused narrowly on that niche
How much do Kogito and Thredd cost?
Kogito is free to use; Thredd is priced on request. Plan by plan below, from each vendor's own pricing page.
Kogito
Free- KogitoFree
- Apache 2.0 licence
- Apache KIE incubating project
- No usage limits
Thredd
On request- ThreddOn request
- Volume and programme-based pricing, not published
- Custom quote required via sales
Which should you pick?
Choose Kogito if
- You need build-time code generation.
- You want to start without paying.
- You work on Linux, Self-hosted.
- You also want quarkus and spring boot support.
Choose Thredd if
- You need issuer processing.
- You work on Web, API.
- You also want multi-country reach.
Questions people ask
- Is Kogito or Thredd better?
- Neither clearly leads. Kogito starts at Free and Thredd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Kogito or Thredd?
- Kogito has a free tier; the other does not. Paid plans start at Free for Kogito and On request for Thredd.
- Does Kogito or Thredd run on more platforms?
- Kogito runs on Linux, Self-hosted. Thredd runs on Web, API.
- Can I use Kogito for free?
- Yes. Kogito has a free tier, so you can try it without paying. Thredd starts at On request.
- 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 Thredd is typically brought in for.
- What can Kogito do that Thredd cannot?
- Kogito covers Build-time code generation, Quarkus and Spring Boot support, DMN decision services, Drools rules engine. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.
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.
Thredd: Is Thredd the same company as Global Processing Services?
Yes, GPS rebranded as Thredd in 2023; it is the same company and platform.
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.
Thredd: Does it hold the banking licence for programmes it processes?
No, Thredd is the issuer processor; a separate bank or BIN sponsor holds the actual issuing licence.
Kogito: Does it need Quarkus?
It is designed for Quarkus and supports Spring Boot; both are Java frameworks rather than a standalone server.
Thredd: Is pricing published?
No, it requires a sales conversation.
Kogito: Is there commercial support?
Not from Apache. Red Hat sells supported builds of this lineage as part of its subscriptions.
Related pages
Other head to heads
- Kogito vs Camunda
- Kogito vs n8n
- Kogito vs Temporal
- Kogito vs Flowable
- Kogito vs Activiti
- Kogito vs Decodable
- Kogito vs Zapier
- Kogito vs Dagster
- Kogito vs Nintex
- Kogito vs UiPath
- Kogito vs Mage AI
- Kogito vs CrewAI
- Kogito vs Dify
- Kogito vs Hevo Data
- Kogito vs Meltano
- Kogito vs Pipedream
- Kogito vs SnapLogic
- Kogito vs Windmill
- Kogito vs Lithic
- Kogito vs Tribe Payments
- Kogito vs Marqeta
- Kogito vs Paymentology
- Kogito vs Enfuce
- Kogito vs i2c
- Kogito vs Unit
- Kogito vs Highnote
- Kogito vs Weavr
- Kogito vs Treasury Prime
- Kogito vs Synctera
- Kogito vs Toqio
- Kogito vs Episode Six
- Kogito vs GraphQL Apollo
- Kogito vs Rutter
- Kogito vs Treblle
- Kogito vs Vodeno
- Kogito vs Volt
- Thredd vs Camunda
- Thredd vs n8n
- Thredd vs Temporal
- Thredd vs Flowable
- Thredd vs Activiti
- Thredd vs Decodable
- Thredd vs Zapier
- Thredd vs Dagster
- Thredd vs Nintex
- Thredd vs UiPath
- Thredd vs Mage AI
- Thredd vs CrewAI
- Thredd vs Dify
- Thredd vs Hevo Data
- Thredd vs Meltano
- Thredd vs Pipedream
- Thredd vs SnapLogic
- Thredd vs Windmill
- Thredd vs Lithic
- Thredd vs Tribe Payments
- Thredd vs Marqeta
- Thredd vs Paymentology
- Thredd vs Enfuce
- Thredd vs i2c
- Thredd vs Unit
- Thredd vs Highnote
- Thredd vs Weavr
- Thredd vs Treasury Prime
- Thredd vs Synctera
- Thredd vs Toqio
- Thredd vs Episode Six
- Thredd vs GraphQL Apollo
- Thredd vs Rutter
- Thredd vs Treblle
- Thredd vs Vodeno
- Thredd vs Volt
