
Camunda is pretty interesting because it sits right at the intersection of business and tech. What I like best about it is:
1. Clarity & Visualization – You can map business processes visually using BPMN (flowcharts), DMN (decision tables), and CMMN (case management). This makes it easy for both business users and developers to understand what’s going on.
2. Developer-Friendly – Unlike many heavy enterprise workflow tools, Camunda is lightweight, open, and integrates well with microservices, REST APIs, and external systems. Developers can actually enjoy using it instead of feeling locked into a rigid system.
3. Separation of Concerns – Business stakeholders can design the workflow, while engineers hook it into real systems. This reduces misunderstandings and speeds up delivery. Review collected by and hosted on G2.com.
Good question 🙂 — no tool is perfect, and Camunda has its drawbacks too. Here are some of the main things people often dislike about it:
1. Steep Learning Curve –
BPMN/DMN diagrams can look simple, but mastering them (and modeling correctly) takes time. New users sometimes feel overwhelmed by the notation and technical details.
2. Complex Setup & Infrastructure –
Especially with Camunda 8 (the newer SaaS / Zeebe engine), it can feel heavy. Running clusters, configuring Operate/Tasklist/Optimize, or handling Kubernetes adds operational complexity.
3. Limited Low-Code / No-Code –
Compared to some competitors (like Power Automate or Outsystems), Camunda doesn’t try to be a full “citizen developer” tool. Business users often need technical help to go beyond simple workflows. Review collected by and hosted on G2.com.