Camunda

What it is

Camunda is a process orchestration platform built on BPMN, the ISO-standardised notation for drawing a business process as a diagram that a machine can execute. You model the process — approvals, timers, escalations, calls to other systems, handoffs to people — and the Zeebe engine runs that model, holding the state of every instance for as long as it takes to finish, whether that is four seconds or four months. Operate shows where each instance is stuck, Tasklist gives people their human steps, and Optimize reports on cycle times.

It is not an app-to-app automation tool. It is what you reach for when one process crosses five systems, carries a compliance requirement, and has to survive a two-week wait for a signature without losing its place. Camunda says more than 700 organisations run on it, including Atlassian, ING and Vodafone. Gartner placed it as a Visionary, not a Leader, in the Magic Quadrant for Business Orchestration and Automation Technologies published 14 September 2026 — the same position it held in the inaugural report in October 2025.

What changed for agents

Camunda’s pitch is that agents belong inside a deterministic process, not in place of one. Version 8.8, released on 14 October 2025, made agentic orchestration the headline: an AI Agent connector runs an LLM tool-calling loop inside an ad-hoc sub-process, so the model chooses which activities to run while the surrounding BPMN fixes what happens before and after, who approves, and what gets logged. It works with Anthropic, Azure OpenAI, AWS Bedrock and Google Vertex AI models, and can run on your own infrastructure.

Camunda 8.9, released on 14 April 2026, made the Orchestration Cluster MCP server generally available, so an MCP client such as Claude can start and query processes directly, and shipped three Agent2Agent (A2A) connectors for passing signed messages between agents from different vendors. The same release made a centralised audit log and global user-task listeners generally available — the governance features that actually decide whether a compliance team signs off.

Camunda’s own January 2026 survey of 1,150 decision makers at companies with more than 1,000 employees found that 73% report a gap between their agentic AI vision and reality, and that only 11% of agentic use cases reached production in the past year. Read that as the vendor’s thesis rather than neutral data, but the shape is right: most agent pilots stall because they are not wired into an end-to-end process with an owner.

A use case worth buying it for

A contract-approval workflow that spans five systems. A deal desk request in Salesforce starts a process instance; an agent reads the redlines and classifies risk; low-risk paper routes to automatic approval, while anything with non-standard indemnity waits in Tasklist for legal with a 48-hour escalation timer to the general counsel; the signed contract writes back to the CRM and the ERP; and a notification lands in Slack. Every branch, wait and override sits in one audit trail, and the diagram the lawyers approved is the same artefact the engine runs. That last point is what n8n cannot give you: an n8n flow is a sequence of API calls, and it has no native concept of a human task that waits for days, times out and escalates.

Pricing

Camunda publishes no list price. Local development is free under a non-production licence, and a 30-day SaaS trial is never billed. Any production use — SaaS or self-managed — needs an Enterprise licence, quoted by sales.

The one public anchor is Camunda’s AWS Marketplace listing: an Enterprise Plan at $175,000 for 12 months, metered on process instances, counted each time a process starts. Treat that as a ceiling-setting list price rather than what you will pay, but budget in six figures, not five. Self-managed deployments add the cost of running Kubernetes and Elasticsearch or a relational database yourself.

Best for

Ops and IT leaders at companies of 1,000 or more people automating a long-running, multi-system process with human approvals and an audit requirement — loan origination, claims, onboarding, contract approval — who have Java or platform engineers to own it.

Alternatives, and when to pick them instead

• Pega — a Leader in the inaugural 2025 BOAT Magic Quadrant and scored highest for case management in that year’s Critical Capabilities report. Pick it when the work is case-shaped, driven by unpredictable events rather than a fixed flow, and you want the vendor’s consultants to build it.
• Appian — also a Leader, ranked first for deterministic workflow automation in Gartner’s 2026 Critical Capabilities report. Pick it when business analysts, not developers, should build the process and the forms.
• Temporal — the fastest-growing entrant, with a $550M Series E at a $12.55B valuation on 14 September 2026 and more than 4,300 paying customers. Pick it when your engineers want durable workflows written as code, not diagrams, and no business stakeholder needs to read the model.
• n8n — pick it when the process finishes in minutes, has no human wait states, and one ops engineer can own it.
• UiPath — pick it when half the systems have no API and the process has to drive screens.

Watch-outs

• The open-source story changed. Since 8.6 (October 2024), every Camunda 8 self-managed component needs an Enterprise licence in production; older posts describing a free self-hosted Zeebe are out of date. Guard: get a quote before the proof of concept, not after, and budget as if no free production tier exists.
• Camunda 7 is on a clock. Community Edition reached end of life in October 2025, and Enterprise support ends in April 2030, with paid extended support to April 2032. Camunda 8 is a rearchitected platform, not an upgrade. Guard: if you run Camunda 7, scope the migration as a re-platform project with its own budget, and inventory any features your processes depend on before committing to a target version.
• BPMN is a skill, not a UI. A process modelled badly executes badly, and ops teams without a modelling owner produce diagrams nobody can maintain. Guard: name one process owner and one developer per process before go-live, and keep the first model to a single, bounded process.
• Process-instance metering scales with volume. A high-volume, low-value process — every inbound lead, every ticket — burns instances fast. Guard: put only processes with a human step, a long wait or an audit requirement on Camunda, and leave short, high-volume automations on a cheaper tool.