Camundavs
Temporal


Temporal: Temporal if developers own the process definitions and a code-first workflow model suits better than BPMN.

BPMN process orchestration engine, now source-available rather than open source
As of 31 August 2026, Camunda's pricing is not published; the vendor quotes on request. The standard developer-facing BPMN engine, but the ground has moved: Camunda 7 Community Edition stopped receiving patches in October 2025 and Camunda 8 Self-Managed requires a paid production licence. Softwr lists it under Automation Integration. Camunda is available on Web, Linux, Docker, Kubernetes.
Overview
Camunda executes BPMN process models and DMN decision tables as running software. Developers model a process in a graphical editor, deploy it to the engine, and implement each task as a worker in Java, Node, C#, Python or Go. The engine holds process state, handles timers, retries, incidents and compensation, and exposes an operations console showing exactly where every instance is stuck. Camunda 8 replaced the earlier relational engine with Zeebe, a horizontally scalable event-sourced runtime. The licence change is the fact that should drive any decision here. Camunda 7 was Apache 2.0 with a genuinely usable Community Edition, and a large number of organisations ran it in production for free. The final Camunda 7 feature release, 7.24, shipped on 14 October 2025, after which the Community Edition receives no further security patches; Enterprise support for Camunda 7 was extended to 9 April 2030. Since October 2024 all Camunda 8 Self-Managed components ship under the Camunda License 1.0, which allows reading the source and using it for development and testing but requires a paid production licence to run. That is source-available, not open source, and procurement teams that catalogued Camunda as Apache 2.0 years ago are frequently unaware. The buyer is an enterprise development team orchestrating long-running processes across services, typically in insurance, banking, telecommunications and logistics. The trade off is now largely commercial rather than technical: Camunda 8 is a better engine than Camunda 7 at scale, and the migration path from 7 to 8 is a rewrite of the integration layer rather than an upgrade.
The honest half
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Camunda.
Cross-shopped
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.


Temporal: Temporal if developers own the process definitions and a code-first workflow model suits better than BPMN.


n8n: n8n if the requirement is integration automation rather than modelled, auditable business processes.


Conductor: Conductor for a workflow orchestration engine with a code and JSON definition model rather than BPMN.
Pricing
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Camunda 8
On request
Capabilities
BPMN 2.0 execution
Standards-based process models that run directly rather than being translated to code
DMN decision tables
Business rules maintained as tables separate from the process logic
Zeebe engine
Event-sourced, horizontally partitioned runtime for high process-instance throughput
Operate console
Live view of every running instance, incidents and stuck tokens
Job workers
Task implementations in Java, Node, Python, Go and C# polling the engine
Optimize
Historical process analytics for cycle time and bottleneck reporting
Answered, with sources
Each answer names the page it came from, so you can check it rather than take our word for it.
No. Camunda 8 Self-Managed ships under the Camunda License 1.0, which is source-available and requires a paid production licence.
Its final feature release, 7.24, was in October 2025 and the Community Edition receives no further patches. Enterprise support runs to April 2030.
Not in place. The engine, API and persistence changed, so it is a rewrite of the integration layer.
Camunda does not publish prices. Both self-managed production and SaaS require a quote.
Keep looking
Durable execution platform for fault-tolerant workflows.
Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti
Apache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked
Cloud-native business automation for Quarkus, now an Apache KIE component
Long-running Java BPMN engine, now developed inside Apache KIE with commercial support from IBM
Automate tasks across cloud and on-premises apps
Data pipeline platform with AI-generated workflows and governance
Embedded integration platform and unified API, repositioned from ecommerce automation towards AI agent connectivity
Softwr does not host reviews and shows no star rating for Camunda, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
What people switch to, and what they give up
Every tier, and where the cost actually lands
Put it head to head with anything we hold
Its rating, and an embed for your own site
Industrial DataOps middleware that models and contextualises OT data before it reaches IT systems
Per site per yearManaged Apache Flink and Debezium with credit-based pricing and a free tier
Per credit by task hourEmbedded integration platform that SaaS vendors ship inside their own product
Per month by API call volumeApache 2.0 BPMN engine under Hyland, from which Flowable and Camunda were forked
Open source, no licence feeTransactional message queuing for systems where a lost message is a lost payment
Per virtual processor core per monthPostgres-backed distributed task queue and workflow engine for Python, TypeScript and Go
Per month by task run count