Automation Integration · head to head
Camunda vs Envoy

Camunda
Automation Integration
BPMN process orchestration engine, now source-available rather than open source
- From
- On request
- Free plan
- No

Envoy
Developer Tools
A high-performance L7 proxy written in C++ that is configured by an API rather than a config file, and is usually deployed under a control plane.
- From
- Free
- Free plan
- Yes
The short version
- Envoy is free; Camunda prices on request.
- Only Camunda lists BPMN 2.0 execution; only Envoy lists xDS dynamic configuration.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Camunda and Envoy actually diverge.
What each one covers
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 Envoy
- xDS dynamic configuration
- Protocol breadth
- Filter chain architecture
- Observability by default
- Outlier detection
- Traffic shaping
- mTLS termination and origination
- Hot restart
What people use each for
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 Envoy
- Insurance claims or loan origination where the process model is itself a compliance artefactnot Envoy
- Replacing orchestration logic scattered across microservices with one engine that owns the state machinenot Envoy
- A regulated organisation that needs an auditable record of how each process instance actually executednot Envoy
Envoy
- Acting as the data plane under a service mesh or Gateway API implementation, which is how the overwhelming majority of deployments use itnot Camunda
- An edge or API gateway that needs per-route retry budgets, circuit breaking and outlier detection rather than round-robin proxyingnot Camunda
- Migrating traffic between service versions or between a monolith and its replacement, using weighted splits and shadow trafficnot Camunda
- Standardising observability across a polyglot estate, so that latency, error rates and tracing look the same regardless of the language a service is written innot Camunda
Where each one falls 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
Envoy
- The configuration surface is very large and hand-written bootstrap YAML runs to hundreds of lines for routing that Nginx expresses in twenty, which is why nearly every production deployment sits under a control plane and inherits that control plane's constraints as well
- xDS is the real API and it is not stable in the comfortable sense; the v2 API set was removed outright, resource types continue to be deprecated, and your control plane and Envoy binaries have to be upgraded roughly in step or the proxies stop accepting configuration
- Extending it properly means writing a C++ filter and building and maintaining your own Envoy binary; the alternatives are Lua, which adds per-request overhead, and proxy-wasm, whose ABI has remained effectively experimental for years with a real performance cost
- At sidecar density the per-proxy memory and CPU footprint is a measurable share of cluster capacity, since thousands of workloads each carry a full proxy, and this is precisely the cost that has pushed mesh projects towards node-level or ambient architectures
- There is no single vendor selling support for Envoy itself; you get the community plus control-plane vendors such as Solo.io and Tetrate, so an Envoy-level production bug is your own engineers in a C++ codebase unless a support contract happens to cover it
- Diagnosing why a request got a particular response involves reading config dumps, the stats endpoint and the RESPONSE_FLAGS codes in access logs rather than a readable error, which is a specific skill you must hire or spend months growing
Pricing, plan by plan
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
Envoy
FreeNo published plan breakdown. See the Envoy 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 Envoy if
- You need xds dynamic configuration.
- You want to start without paying.
- You also want protocol breadth.
Questions people ask
- Is Camunda or Envoy better?
- Neither clearly leads. Camunda starts at On request and Envoy at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Camunda or Envoy?
- Envoy has a free tier; the other does not. Paid plans start at On request for Camunda and Free for Envoy.
- Does Camunda or Envoy run on more platforms?
- Camunda runs on Web, Linux, Self-hosted. Envoy runs on Web.
- Can I use Envoy for free?
- Yes. Envoy has a free tier, so you can try it without paying. Camunda starts at On request.
- 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 Envoy is typically brought in for.
- What can Camunda do that Envoy cannot?
- Camunda covers BPMN 2.0 execution, DMN decision tables, Zeebe engine, Operate console. Envoy covers xDS dynamic configuration, Protocol breadth, Filter chain architecture, Observability by default.
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.
Envoy: Should I run Envoy on its own, or under a control plane?
Almost always under one. Directly authoring xDS or static bootstrap configuration is viable for a handful of routes and becomes unmanageable beyond that. Envoy Gateway, Istio, Contour, Gloo and Consul all exist to generate that configuration for you.
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.
Envoy: How does it compare with Nginx or HAProxy?
Envoy is dynamically configured over an API and instrumented far more heavily; Nginx and HAProxy are faster to configure and lighter for straightforward reverse proxying. If you never need to change routing without a reload, Envoy is more machinery than the problem requires.
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.
Envoy: What does it cost?
Nothing to licence; it is Apache 2.0 and there is no paid edition. The cost is engineering time and, for most organisations, a commercial control plane or cloud service that packages it.
Camunda: What does it cost?
Camunda does not publish prices. Both self-managed production and SaaS require a quote.
Envoy: Can I write extensions without C++?
You can write Lua filters or proxy-wasm modules in Rust, Go, C++ or AssemblyScript. Both carry per-request overhead compared with a native filter, and the Wasm path has been slower to stabilise than the project originally projected.
Envoy: Is it a CNCF project?
Yes, it is a graduated CNCF project licensed under Apache 2.0, which means the trademark and governance sit with the foundation rather than with Lyft or any vendor.
Related pages
Other head to heads
- Camunda vs n8n
- Camunda vs Temporal
- Camunda vs Flowable
- Camunda vs Activiti
- Camunda vs Kogito
- Camunda vs jBPM
- Camunda vs Parabola
- Camunda vs Blue Prism
- Camunda vs UiPath
- Camunda vs Zapier
- Camunda vs Microsoft Power Automate
- Camunda vs Paragon
- Camunda vs SnapLogic
- Camunda vs Stitch
- Camunda vs Talend
- Camunda vs Tealium
- Camunda vs Tines
- Camunda vs Xano
- Camunda vs Istio
- Camunda vs Ona (formerly Gitpod)
- Camunda vs Spacelift
- Camunda vs Atlantis
- Camunda vs Jenkins
- Camunda vs Restate
- Camunda vs Hookdeck
- Camunda vs Helix
- Camunda vs Turborepo
- Camunda vs StackBlitz
- Camunda vs Webpack
- Camunda vs Backstage
- Camunda vs PyCharm
- Camunda vs Vite
- Camunda vs Buildkite
- Camunda vs Daytona
- Camunda vs Deno
- Camunda vs Earthly
- Envoy vs n8n
- Envoy vs Temporal
- Envoy vs Flowable
- Envoy vs Activiti
- Envoy vs Kogito
- Envoy vs jBPM
- Envoy vs Parabola
- Envoy vs Blue Prism
- Envoy vs UiPath
- Envoy vs Zapier
- Envoy vs Microsoft Power Automate
- Envoy vs Paragon
- Envoy vs SnapLogic
- Envoy vs Stitch
- Envoy vs Talend
- Envoy vs Tealium
- Envoy vs Tines
- Envoy vs Xano
- Envoy vs Istio
- Envoy vs Ona (formerly Gitpod)
- Envoy vs Spacelift
- Envoy vs Atlantis
- Envoy vs Jenkins
- Envoy vs Restate
- Envoy vs Hookdeck
- Envoy vs Helix
- Envoy vs Turborepo
- Envoy vs StackBlitz
- Envoy vs Webpack
- Envoy vs Backstage
- Envoy vs PyCharm
- Envoy vs Vite
- Envoy vs Buildkite
- Envoy vs Daytona
- Envoy vs Deno
- Envoy vs Earthly
