Camunda vs Cloudflare Workflows

Camunda has no write-up on Specifiction yet; its figures are above.

Cloudflare Workflows lets developers build durable, multi-step applications on Cloudflare Workers without managing infrastructure. It automatically retries failed tasks, handles errors, and preserves state for minutes, hours, or weeks. Workflows can pause for seconds, hours, or days, or wait for webhooks, user input, or external system responses before continuing. Instances may be triggered, paused, resumed, or terminated through code or an API. A workflow can call Fetch API requests and Cloudflare services including R2, KV, and D1, and can be invoked through the Workers API, Wrangler CLI, or REST API. Billing covers CPU time, requests, persisted storage, and executed steps; waiting or sleeping does not incur CPU time. Workers Free includes a free plan with usage limits, while paid pricing starts at $5/mo. Paid plans allow up to five minutes of CPU time per invocation. The service has a cloud deployment model, supports human tasks and approvals, long-running workflows, versioning, and up to 50,000 concurrent runs. Workflows cannot be deployed to Workers for Platforms namespaces.