Skip to content

Camunda vs Orchestrator Zero

oz0 records agent jobs running on your infrastructure. Camunda places agents inside visual BPMN processes. oz0 focuses on operating agents across your machines, with outbound-only nodes, tenant rules, a model gateway and a verifiable audit trail.

What Camunda is

Camunda is a process orchestration platform whose agentic orchestration puts AI agents inside BPMN processes run by its Zeebe engine. The model selects activities as tools, and the engine runs each call as a step. It is available as SaaS or Self-Managed; these ratings cover the current 8.10 documentation.

docs.camunda.io
Runs
Self-hosted or managed
Checked
27 October 2026

Side by side.

Camunda's ratings come from its own pages. A column's name opens its definition and how Orchestrator Zero does it. How we rated

Where it runs

Any machine you own

Yes

Docs

Yes: Workers on hosts you choose

Tools run as job workers on hosts you choose, and in hybrid mode the connector runtime that runs the agent runs on your own machines.

docs.camunda.io docs.camunda.io

Linux, macOS and Windows

Yes

Native; hosted-runner tested

Docs

Conditional: Linux only in production

Camunda and its connector runtime are supported in production only on Linux; Windows and macOS are for development.

docs.camunda.io docs.camunda.io docs.camunda.io docs.camunda.io

Self-hosted control plane

Yes

Docs

Conditional: Enterprise licence in prod

Self-Managed runs the whole platform on Kubernetes, Docker or Linux hosts, but production use needs an Enterprise licence.

docs.camunda.io camunda.com

No inbound ports

Yes

Docs

Yes: Workers poll for jobs

Job workers and the connector runtime poll the engine for jobs, so nothing calls into the machines that run agents.

docs.camunda.io

Fleet operations

Yes

Docs

Conditional: Job types, no machine registry

A job goes to whichever worker asks for its type; there is no registry of machines to join, label, block or upgrade.

docs.camunda.io

Durability

Durable runs

Conditional

Depends on agent type

Docs

Yes

Each model call and tool call is a job the engine keeps, with the agent's conversation in a process variable; a job not completed in time goes to another worker.

docs.camunda.io docs.camunda.io

Governance

Tool policy outside the model

Conditional

Harness coverage varies

Docs

Conditional: Gates modelled per process

MCP client filters include or exclude tools, and a gateway can send chosen calls to a user task or refuse them. Each process's designer models these gates; no admin rule applies across processes.

docs.camunda.io docs.camunda.io docs.camunda.io

Approvals in chat

Conditional

Tested against stand-ins only

Docs

Conditional: CLI; Teams app in alpha

A user task stops the process until a person completes it in Tasklist, through the API or with c8 complete ut; completing tasks in Microsoft Teams is an alpha.

docs.camunda.io docs.camunda.io docs.camunda.io

Tool snapshots

Yes

Docs

Conditional: BPMN tools versioned; MCP live

BPMN tools belong to versioned process definitions. Remote MCP tools are discovered from their server; an automatic gate requiring approval of changed definitions is not documented.

docs.camunda.io docs.camunda.io

Tenants built in

Yes

Docs

Yes

Logical tenants keep each tenant's processes and data apart, with access by tenant assignment; the checks are off until an admin turns them on.

docs.camunda.io

Cost

Budgets that stop a run

Yes

Set strict reservation

Docs

Conditional: Call caps; trial LLM budget

The AI Agent connector caps model calls per agent, and the docs say to set cost limits at the provider; only the SaaS test LLM has a dollar budget.

docs.camunda.io docs.camunda.io

Security

Provider keys off the workers

Yes

Docs

Conditional: Secrets resolved on the worker

Provider keys are connector secrets, resolved for the connector runtime that runs the agent loop; only the SaaS test LLM goes through Camunda's gateway.

docs.camunda.io docs.camunda.io docs.camunda.io

Sandbox with an egress allowlist

Conditional

Linux/macOS; Windows tier 0

Docs

Not documented

Tools run in job workers or a connector runtime, and Self-Managed supports HTTP proxies. A built-in tool sandbox with an outbound host allowlist is not documented.

docs.camunda.io docs.camunda.io

Audit and compliance

Tamper-evident audit trail

Yes

Keep trusted chain heads

Docs

Conditional: Audit log, no hash chain

The audit log records who performed an operation on process instances, user tasks and identity; no hash chain or signature is documented.

docs.camunda.io

Erasure by key

Yes

Restore with erasure ledger

Docs

Conditional: Delete instances, no own keys

Finished process instances can be deleted through the API, and on SaaS one AWS KMS key covers a whole cluster, so there are no per-person keys.

docs.camunda.io docs.camunda.io

Retention with legal hold

Conditional

Capture needs source data

Docs

Conditional: Retention, no legal hold

Admins set retention for cluster data, and SaaS keeps it 30 days unless agreed otherwise; no legal hold is documented.

docs.camunda.io docs.camunda.io

Openness

Model provider choice

Yes

Docs

Yes

The AI Agent connector supports Anthropic, Bedrock, Azure OpenAI, Vertex AI, OpenAI and any OpenAI-compatible API, including local models through Ollama.

docs.camunda.io

MCP and A2A

Yes

Docs

Conditional: MCP; A2A client in alpha

Agents use MCP servers through the MCP Client connectors. The A2A Client connectors are an alpha without authentication, and no A2A server is documented.

docs.camunda.io docs.camunda.io

Where Camunda is stronger.

  • BPMN and DMN process models

    Agents, human tasks and system steps are modelled in BPMN and decisions in DMN, open standards that auditors can read without a Camunda tool.

    camunda.com
  • Human tasks in Tasklist

    User tasks wait for people in Tasklist, a ready-made task inbox, or in your own app on the API.

    docs.camunda.io
  • Connectors and RPA

    Built-in connectors cover AWS, Google, Microsoft 365, Kafka, Salesforce, SAP, Slack and RPA tools such as UiPath, with more on the Camunda Marketplace.

    docs.camunda.io
  • Hosted service with certifications

    Camunda SaaS is a hosted service, and the Camunda Trust Center lists SOC 2 Type II, ISO 27001 and TISAX.

    trust.camunda.com
  • Process tests in the real engine

    Camunda Process Test runs a process against an embedded Zeebe engine in CI, so tests can check that agents escalate and guardrails block, with a coverage report.

    camunda.com

Full in Camunda, partial in oz0: Durable runs.

Differences to examine.

Compare the scope, conditions and editions in the source notes.

Using both

Camunda's MCP Remote Client connector sends a bearer token, so a Camunda AI agent could use Orchestrator Zero agents as MCP tools, while Camunda models the process around them. Camunda's A2A client is an alpha without authentication, so connect the two over MCP.

Based on documentation; this pairing has not been tested.