Softwr

Automation Integration · head to head

Camunda vs Thredd

Camunda logo

Camunda

Automation Integration

BPMN process orchestration engine, now source-available rather than open source

From
On request
Free plan
No
Thredd logo

Thredd

APIs

Issuer processing platform for fintechs and digital banks, formerly Global Processing Services

From
On request
Free plan
No

The short version

  • Only Camunda lists BPMN 2.0 execution; 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 Camunda and Thredd differ?

Camunda and Thredd differ on platforms and category. Only the attributes on which Camunda and Thredd actually diverge.

Attributes where Camunda and Thredd differ
AttributeCamundaThredd
PlatformsWeb, Linux, Self-hostedWeb, API
CategoryAutomation IntegrationAPIs

Identical on both: starting price (On request), pricing model (Quote), free tier (No).

Not yet recorded: founded for Thredd.

Which features does each one have?

They share no listed features; 6 appear only for Camunda 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 Camunda

  • BPMN 2.0 execution
  • DMN decision tables
  • Zeebe engine
  • Operate console
  • Job workers
  • Optimize

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.

Camunda

  • Long-running business processes crossing several services where the state must be visible to non-developersnot Thredd
  • Insurance claims or loan origination where the process model is itself a compliance artefactnot Thredd
  • Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot Thredd
  • A regulated organisation that needs an auditable record of how each process instance actually executednot Thredd

Thredd

  • A digital bank or fintech needing issuer processing across many countries under one contractnot Camunda
  • A BNPL, lending or crypto product needing certified card processing behind its own brandnot Camunda
  • A company that finds outdated Global Processing Services (GPS) material and needs to confirm it is now Threddnot Camunda
  • An embedded finance platform wanting a processor already integrated with core banking systems such as Mambunot Camunda

Where do Camunda 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.

Camunda

  • Camunda 7 Community Edition stopped receiving security patches after the 7.24 release in October 2025, so free production deployments are now running unpatched software
  • Camunda 8 Self-Managed is source-available under the Camunda License 1.0, not open source: production use requires a paid licence, and organisations that adopted Camunda for its Apache licence have to renegotiate that decision
  • Migrating from Camunda 7 to 8 is a rewrite rather than an upgrade because the engine, the API and the persistence model all changed, and there is no in-place migration for running instances
  • Camunda 8 Self-Managed has substantial infrastructure requirements including Zeebe brokers, Elasticsearch and Identity, which is a considerable operations burden compared with the single database that Camunda 7 needed
  • Pricing is not published at all, so evaluating total cost requires a sales process, and there is no way to size a budget before committing engineering time to a proof of concept

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 Camunda and Thredd cost?

Camunda is priced on request; Thredd is priced on request. Plan by plan below, from each vendor's own pricing page.

Camunda

On request
  • Camunda 8On request
    • Self-Managed under Camunda License 1.0, production licence required
    • SaaS with a thirty day full trial
    • Free unlimited BPMN and DMN modelling after the trial

Thredd

On request
  • ThreddOn request
    • Volume and programme-based pricing, not published
    • Custom quote required via sales

Which should you pick?

Choose Camunda if

  • You need bpmn 2.0 execution.
  • You work on Web, Linux, Self-hosted.
  • You also want dmn decision tables.

Choose Thredd if

  • You need issuer processing.
  • You work on Web, API.
  • You also want multi-country reach.

Questions people ask

Is Camunda or Thredd better?
Neither clearly leads. Camunda starts at On request and Thredd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Camunda or Thredd?
Camunda starts at On request and Thredd at On request.
Does Camunda or Thredd run on more platforms?
Camunda runs on Web, Linux, Self-hosted. Thredd runs on Web, API.
What is Camunda best used for?
Camunda is most often used for long-running business processes crossing several services where the state must be visible to non-developers, insurance claims or loan origination where the process model is itself a compliance artefact, replacing orchestration logic scattered across microservices with one engine that owns the state machine, a regulated organisation that needs an auditable record of how each process instance actually executed. Of those, long-running business processes crossing several services where the state must be visible to non-developers and insurance claims or loan origination where the process model is itself a compliance artefact are not what Thredd is typically brought in for.
What can Camunda do that Thredd cannot?
Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.

Answered from the vendors’ own pages

Camunda: Is Camunda still open source?

No. Camunda 8 Self-Managed ships under the Camunda License 1.0, which is source-available and requires a paid production licence.

Thredd: Is Thredd the same company as Global Processing Services?

Yes, GPS rebranded as Thredd in 2023; it is the same company and platform.

Camunda: What happened to Camunda 7?

Its final feature release, 7.24, was in October 2025 and the Community Edition receives no further patches. Enterprise support runs to April 2030.

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.

Camunda: Can I upgrade from 7 to 8?

Not in place. The engine, API and persistence changed, so it is a rewrite of the integration layer.

Thredd: Is pricing published?

No, it requires a sales conversation.

Camunda: What does it cost?

Camunda does not publish prices. Both self-managed production and SaaS require a quote.

Share

Related pages

Other head to heads