

Camunda and Temporal are prominent players in the workflow automation and business process management sector. Temporal appears to have the upper hand with its focus on simplifying complex workflows and handling distributed transactions, enhancing developer convenience.
Features: Camunda boasts lightweight architecture, compliance with BPMN standards, and open-source access, providing flexibility for developers. Its active community and robust Java integration also stand out. Temporal caters significantly to developers with features focused on distributed transactions and durable application state, making it ideal for long-running workflows and microservices environments. Its abilities in retry mechanisms and fault tolerance are also noteworthy, particularly for simplifying complex workflow management.
Room for Improvement: Camunda could improve its UI/UX, integration support, and documentation. Expanding community support and flexible licensing are additional areas to focus on. Temporal's documentation and visualization tools could be more beginner-friendly, with potential enhancements to dashboard features. Further educational resources and improvements in data management and authentication for on-premise setups are needed for Temporal.
Ease of Deployment and Customer Service: Camunda supports multiple deployment models, including on-premises and cloud environments, yet faces performance and integration challenges. Its technical support is mixed, highlighting the need for improved sales support. Temporal offers open-source deployment with effective direct technical support but has limitations in advanced integration and configuration options.
Pricing and ROI: Camunda's open-source model is cost-effective for startups, but its enterprise edition could pose scalability challenges. While Temporal's open-source nature leads to cost savings in self-managed settings, infrastructure costs might increase with complexity. Both platforms promise quick ROI through enhanced process management; however, cost management remains a critical factor in scaling.
The ROI is apparent in terms of business case automation; previously, a bunch of people filled in data in NetSuite or managed stocks between warehouses and Amazon, but now everything is automated, saving time.
They really understand deeply and in detailed fashion the solution.
AWS provides the best support, followed by Microsoft, and then Google.
They provide better support for the enterprise edition.
Camunda offers a high level of scalability, especially when using its SaaS model, which manages and scales implementations automatically.
It allows for easy scaling, especially with ECS service configurations.
They have that REST layer, REST APIs layer that makes it easy to integrate and make it part of a microservices ecosystem and APIs.
There haven't been any significant outages in my experience with Camunda.
We measured the time for each step individually because each activity in the process was an API call to an external API in a different legacy system.
Since they made the move to cloud deployment in a more SaaS-oriented way, they do not invest too much in the community version.
There is an issue where, in some situations, I need to scale up by observing both CPU and memory usage of containers, yet under the current options available at Amazon, this is not possible.
More open documentation would be beneficial to understand the deployment process better and facilitate easier setup.
For some services, such as hosting databases, Google is really expensive.
There is a licensing cost for using the SaaS model and Enterprise edition of Camunda.
ECS also allows for horizontal scalability with thresholds that can be configured for CPU or memory.
Camunda's support for BPMN 2.0 is a great advantage because it allows us to have a common language to discuss technology and business in the same perspective.
The biggest difference between Camunda and Bonita might be that Camunda is simpler and more flexible for setting.
The deployment process is quite straightforward as it provides both Kubernetes and Docker Compose versions, allowing us to run it in ECS containers.
| Product | Mindshare (%) |
|---|---|
| Camunda | 12.0% |
| Temporal | 4.4% |
| Other | 83.6% |

| Company Size | Count |
|---|---|
| Small Business | 43 |
| Midsize Enterprise | 15 |
| Large Enterprise | 29 |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 4 |
| Large Enterprise | 6 |
Camunda offers a process orchestration platform that automates and streamlines AI processes while integrating human tasks and diverse systems without sacrificing security, governance, or innovation.
Camunda empowers businesses and IT to collaborate effectively, addressing complexity, enhancing efficiency, and maintaining competitiveness at any speed or scale. Trusted by over 700 organizations including Atlassian, ING, and Vodafone, it designs, orchestrates, automates, and improves critical business processes to accelerate digital transformation. It is flexible and lightweight, easily integrating with APIs and microservices, while adhering to BPMN, CMMN, and DMN standards for comprehensive process modeling and automation.
What are Camunda's standout features?Organizations use Camunda to automate business processes across industries like banking, logistics, telecommunications, and retail. It supports complex workflows such as loan approvals and integrates third-party applications. Known for managing tasks and process automation, it fits seamlessly with existing systems on-premise or in cloud environments like Azure and AWS.
Temporal automates and manages workflows efficiently, offering resilience in distributed systems with features like retry and fault tolerance. Its capabilities in handling complex workflows and integrating with programming languages make it a valuable tool for managing diverse business logic.
Temporal excels in workflow orchestration, automating tasks across multiple platforms, and ensuring durability in asynchronous operations. It supports long-running workflows and simplifies handling distributed transactions, reducing boilerplate code. Temporal is noted for its durable execution and built-in retry policies, enhancing resilience. Despite its complexity and steep learning curve, it is valued for its integration with popular programming languages and relatively easy setup process, though it requires improvements in user-friendly features, documentation, community support, and security.
What are Temporal's key features?Temporal is implemented in sectors requiring robust workflow orchestration, such as managing data pipelines, API integration, and scheduling tasks. Organizations in a Kubernetes environment leverage it for its scalability and infrastructure management capabilities, securing integrations and enhancing reliability across IT operations.
We monitor all Process Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.