What do you like best about Camunda?
What I like best about Camunda is its developer-friendly approach to process automation—especially its strong foundation in BPMN (Business Process Model and Notation), combined with its open architecture. A few standout aspects:
1. BPMN-first design: Camunda treats BPMN not just as a diagram but as executable code. That makes it easy for business and tech teams to collaborate without losing precision or control.
2. Open and flexible: Unlike many automation platforms, Camunda doesn’t lock you into a rigid ecosystem. You can integrate it with virtually anything—REST APIs, Kafka, RPA bots, microservices, legacy systems, etc.
3. Camunda 8 (SaaS + Zeebe): The move to Zeebe as the process engine brought true horizontal scalability and made it easier to run in cloud-native environments (like Kubernetes).
4. Operate, Tasklist & Optimize: These built-in tools provide great visibility into process execution, human task management, and data-driven insights—without needing to bolt on third-party software.
5. Community and Documentation: Camunda has a strong developer community, excellent docs, and a transparent product roadmap. It’s easy to get started, and there’s lots of shared knowledge out there.
In short: Camunda offers the power of enterprise-grade orchestration without sacrificing developer autonomy or flexibility. That’s rare. Review collected by and hosted on G2.com.
What do you dislike about Camunda?
What I dislike about Camunda (short and honest):
• Steep learning curve for BPMN newcomers.
• Operate UI can feel clunky for large-scale monitoring.
• Connector development sometimes lacks polish and flexibility.
• Cloud pricing for Camunda 8 SaaS may be high for smaller teams.
• Limited built-in support for long-running human tasks compared to alternative Review collected by and hosted on G2.com.