Softwr

Automation Integration · head to head

Camunda vs etcd

Camunda logo

Camunda

Automation Integration

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

From
On request
Free plan
No
etcd logo

etcd

Databases

A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.

From
On request
Free plan
No

The short version

  • Only Camunda lists BPMN 2.0 execution; only etcd lists raft consensus.
  • Prices and features on this page were last checked on 13 November 2026.

How do Camunda and etcd differ?

Camunda and etcd differ on pricing model (Quote against Open-source), platforms and category. Only the attributes on which Camunda and etcd actually diverge.

Attributes where Camunda and etcd differ
AttributeCamundaetcd
Pricing modelQuoteOpen-source
PlatformsWeb, Linux, Self-hostedWeb
CategoryAutomation IntegrationDatabases

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

Which features does each one have?

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

  • Raft consensus
  • Linearizable reads
  • Transactions
  • Leases
  • Watches
  • MVCC revision history
  • Role-based access control
  • Snapshot backup and restore

What is each one used for?

etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL. 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 etcd
  • Insurance claims or loan origination where the process model is itself a compliance artefactnot etcd
  • Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot etcd
  • A regulated organisation that needs an auditable record of how each process instance actually executednot etcd

etcd

  • Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot Camunda
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Camunda
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Camunda
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Camunda

Where do Camunda and etcd fall short?

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

etcd

  • It is sized for coordination data, not application data: the default backend quota is 2 GB and 8 GB is the documented recommended maximum, and exceeding it puts the cluster into a NOSPACE alarm where it accepts no writes until an operator compacts, defragments and clears the alarm by hand
  • Every write is replicated and fsynced before acknowledgement, so cluster performance is bounded by the slowest disk in it; a member on network-attached storage with high fsync latency causes leader elections and cluster-wide latency spikes that look like network problems and are not
  • Adding members increases availability but reduces write throughput, because each write must reach a larger quorum; you run three or five members for fault tolerance, and increasing capacity means faster hardware rather than more nodes
  • There is no sharding and no multi-tenancy, so isolating workloads means running separate clusters, each with its own quorum, certificates, backup schedule and upgrade path, and that operational multiplication is often unexpected
  • Running it yourself is a real job: periodic compaction and defragmentation, snapshot backups you have actually rehearsed restoring, and rotation of both peer and client TLS certificates, none of which happens automatically outside a managed Kubernetes service
  • Losing quorum is not self-healing; recovering a cluster that has lost a majority means restoring from a snapshot and accepting that everything written since that snapshot is gone, which makes backup frequency a data-loss budget decision rather than a routine setting

How much do Camunda and etcd cost?

Camunda 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

etcd

On request

No published plan breakdown. See the etcd review.

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 etcd if

  • You need raft consensus.
  • You also want linearizable reads.

Questions people ask

Is Camunda or etcd better?
Neither clearly leads. Camunda starts at On request and etcd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Camunda or etcd?
Camunda starts at On request and etcd at On request.
Does Camunda or etcd run on more platforms?
Camunda runs on Web, Linux, Self-hosted. etcd runs on Web.
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 etcd is typically brought in for.
What can Camunda do that etcd cannot?
Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.

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.

etcd: Can I use etcd as an application database?

No. It is designed for metadata and coordination, with a recommended maximum store size of around 8 GB, no sharding and a write path deliberately optimised for durability rather than throughput. Application data belongs in a database built for it.

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.

etcd: How many members should a cluster have?

Three for most cases, five where you need to survive two simultaneous failures. Always an odd number, because an even-sized cluster gains no additional fault tolerance while making quorum harder to reach.

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.

etcd: What happens when the store fills up?

The cluster raises a NOSPACE alarm and stops accepting writes, becoming effectively read-only. Recovery requires compacting old revisions, defragmenting each member and then explicitly disarming the alarm, all done by an operator.

Camunda: What does it cost?

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

etcd: Why is my etcd cluster slow or unstable?

Almost always disk latency. Because every write is fsynced before acknowledgement, slow or shared storage causes heartbeat timeouts, leader elections and cascading latency. Local SSDs with low fsync latency are effectively a requirement.

etcd: How does it compare with Consul or ZooKeeper?

All three provide consensus-backed coordination. etcd has the simplest data model and the Kubernetes ecosystem behind it; Consul bundles service discovery, health checking and a service mesh; ZooKeeper is older, JVM-based and still common under Kafka and Hadoop-era systems.

Share

Related pages

Other head to heads