Camunda

I have been using Camunda for five years. My use case involves BPMN and workflow automation for onboarding corporate customers and lending workflows.

Regarding AI agents or AI in Camunda, we are currently in the inception phase. It is not yet used in production, but we are in the architecture approval stage, so it is not yet live.

The best features and what I appreciate most about Camunda are the simplicity in using BPMN representations and the framework overall. Camunda provides excellent tools, including the modeler, web apps for application administration and process monitoring, and the ability to generate reports using Camunda Optimize. These are the main features we use and why we were attracted to Camunda.

Camunda is very capable of running complex orchestrations and end-to-end business processes. The lending use case is somewhat complex, and Camunda made it very easy and handy to implement.

Camunda's ability to observe and control processes at runtime is very good and perfect. All of these capabilities can be used in Camunda in production, allowing us to monitor and observe runtime processes.

Camunda handles long-running processes very well. We have processes that might be stuck for months, and Camunda works on them without any issues.

The latest feature is Process OS. The idea is very good, but it still needs more elaboration on how it operates and how it will help the business and technical aspects. This needs more demonstration because it is not easy to understand Process OS.

I have been using Camunda for almost five years.

Approximately 5,000 users use Camunda.

The return on investment I see is almost 40 to 50%, and I am looking forward to investing more.

Camunda is fairly priced at a mid-level. It is not cheap, and it is not that much expensive.

When we started working with Camunda, we had a consultant who helped us compare Camunda with most of the solutions in the market. At that time, Camunda was the best choice due to the usability and simplicity it offered.

Camunda is deployed as an on-premises solution. It was purchased directly through Camunda itself, not through a vendor or partner. Maintaining Camunda is easy and can be achieved in a straightforward way. I would recommend Camunda to others looking to implement this product, and they should consider doing a proof of concept. I would give this product a rating of 9 out of 10.

My main use case for Camunda is intelligent document processing. I use Camunda for intelligent document processing in the banking business process around all kinds of documents, and it is used to orchestrate classification, extraction, and business decisions.

My impressions of Camunda for orchestrating complex end-to-end business processes are that it is a very good tool to handle the complexity of business cases.

The best features Camunda offers include high performance and excellent modeling capabilities.

The modeling experience stands out for me due to the interface, the respect for industry standards, and also the integration capabilities with templates of services named connectors.

Camunda has positively impacted my organization by simplifying business process management and improving time to market. We have reduced the code by 50% and improved time to market.

Camunda can be improved with current features and development that are interesting, such as process design using generative AI or agentic orchestration.

I have been using Camunda for four years.

Regarding Camunda's AI capabilities, I consider its accuracy and reliability of output to be very reliable. It is a high-performance orchestration engine, and we have had very few production incidents over the span of a few years.

Camunda is deployed in my organization as a private cloud. I use Red Hat OpenShift as the cloud provider for the private cloud deployment. My overall rating for Camunda is 10 based on the overall quality, performance, and vision.

Camunda is used for workflow digitalization, which I would call business process orchestration. I do use AI or AI agents with my people and systems, but not within Camunda as of now.

The best features of Camunda include the way it integrates into existing application landscapes and the stability. My thoughts on orchestrating complex end-to-end business processes with Camunda are definitely positive, as it can handle every process, especially within the financial context.

Camunda can orchestrate the systems we already run without forcing us to replace or migrate them, which is one of the major advantages I have mentioned. With Camunda, it works very well for long-running processes, so it keeps us updated with full status and visibility.

The area where we are struggling with Camunda is currently the Optimize module, which does not have all the features that we need for fully-fledged process analytics.

Regarding maintenance, I would say it is currently not so easy, especially since we do this on-premises and our IT team is struggling with migrating it to OpenShift.

I have been working with Camunda since 2022, so for four years.

My thoughts on the stability of Camunda are that we do have downtimes, but they are usually not caused by Camunda, so I think the general stability is good. I would rate it a nine.

Currently, we have about 700 users using Camunda. Camunda is definitely scalable for our company and business needs, and I would rate it a ten.

When I rate the technical support for Camunda from one to ten, I would give them an eight.

When it comes to return on investment for Camunda, regarding process lead time reduction, we see something between 50 to 80 percent easily. On average over all the processes that we have, I would say it is between 5 to 10 percent.

My thoughts on the pricing of Camunda are that it is worth its price, with a touch towards expensive. On pricing, I would rate Camunda as a seven.

In comparing Camunda with other vendors, we have not reassessed since we decided to go for Camunda, so we basically use it exclusively, making it difficult for me to answer.

I can definitely recommend Camunda, especially within the financial industry. I would rate this review a nine overall.

I do not use Camunda agents personally, but I am aware that people within the organization have started using them.

I find it valuable that Camunda is built on open standards such as BPMN and connects openly with different models, agents, and frameworks, as it does not limit me in terms of skills. It allows for easier access to resources or people in the market, and it will be easier for them to learn from their past experiences. This makes things straightforward.

The areas in Camunda that have room for improvement are primarily the front-end capabilities. However, we had a discussion with Brandon, the Camunda founder, who highlighted that this is not his focus. I think if Camunda can improve the overall front-end capabilities, that will help them. They have also pushed for Camunda being able to extend its forms using different applications.

I have been working with Camunda for two years.

Regarding stability, we have not had a solution running heavily in production, but so far, I would rate it as fairly stable. This is not a production environment; it is more of a QA prod environment. Although we do have a production environment, we do not have a solution running there, so I cannot rate it fairly based on production performance. Based on what we have tested, it is quite stable.

I would say that we are looking at having more than a thousand users using the solution.

I note that we have not tested scalability very much, as we do not have a product in production right now.

I rate their technical support as a nine; it is good.

I find that pricing is not inexpensive based on the fact that enterprise applications can easily generate millions of process instances. Camunda charges per process instance, which is a constraint compared to other engines. It is different in that regard.

I compare Camunda with other solutions or vendors such as Pega, IBM, or Bizagi and find that technically, it is actually good and almost in the lead. However, the drawback is the two things I mentioned: the financial model of licensing or charging, and the front-end capabilities.

I find that it is easy to maintain Camunda because we have already upgraded and patched it with ease, so it is quite straightforward and does not require days of planning and preparation.

Overall, I rate Camunda a score of eight.

Our use case for Camunda is primarily workflow automation and rule management, utilizing both DMN cases.

In my opinion, the best features of Camunda include the data scientist side where we have Optimize that can help us analyze the processes and see where the heat map is, which is useful in everyday business to know regarding the volumes and workflows that are taking more time than expected.

The overall solution with Camunda is very convenient regarding the connectors with Salesforce, Workday, and other tools, which helps expedite projects and achieve good returns on investment, meaning that under six or nine months, you can implement a project. For example, we started a project in January and delivered it in May, something traditional development cannot provide.

I see improvements with Camunda mainly in quality and service. I feel the best return on investment is less work for internal teams and enhanced value for end customers, allowing less experienced personnel to effectively work with Camunda and understand their responsibilities, alleviating dependence on specific knowledgeable employees.

In Camunda, I believe the process mining side has room for improvement. Before modeling or implementing a new process, understanding existing workflows in the company is vital, suggesting that process mining would be beneficial starting from a previous step.

In addition to process mining, there are technical demands from internal teams wanting to execute queries on SGBD or within our elastic database in Camunda. Although I feel a database demand may not be as relevant since a performant tool relies on having a modern database, improvements on the .NET field are desired, as existing connectors are supported by editors while others come from the community. It would be helpful to have supported .NET connectors by the editor.

My experience with Camunda spans three or four years.

For stability, I would rate it a nine, noting that while several releases occur every six months, which can be difficult for some customers, it remains very stable. Frequent updates necessitate staying up to date.

From one to ten, I would rate the technical support for Camunda a nine. The support is excellent, but communication barriers may arise for French customers due to the need for English during technical issues.

As a partner, we implement Camunda for customers and gather feedback on their satisfaction and project outcomes.

In our organization, we have about 30 specialists working with Camunda, mainly focusing on ETI companies, typically below 5,000 employees, but we also handle projects with CAC 40 companies and public firms on the stock market.

Regarding pricing for Camunda, I believe it is cheap when considering the cost of the volumes, but planning constraints are crucial. Regulatory changes or implementation needs should not take years to resolve, as the value is not just the license cost per number of cases run in the workflow, but how you achieve service enhancement for your company.

Comparing Camunda to vendors such as Pega or Bizagi is challenging. I find Camunda to be particularly trendy, with many coming projects and a strong sales team, positioning it to boom in 2025 and 2026. Other tools do not share the same dynamic, which is why I consider Camunda agile.

We do not use AI agents broadly, but when implementing them, they help us analyze cases and understand customer intent through some first-step analysis, with the last decision remaining human. Engaging users remains difficult, since a workflow tool is already a revolution and AI adds complexity in understanding its decision-making process.

With Camunda, it is very easy to observe and control processes during runtime. Implementing transversal processes requires company-level engagement, but once established, transformation becomes straightforward. The challenge lies in human engagement and internal communication to convey forthcoming changes. However, Camunda offers smooth and visually appealing tools that are comprehensible and well-presented compared to other solutions.

I would recommend implementing Camunda, advising to work with a partner, as it fosters an easier acceptance of change among internal teams when an external company navigates the transition. Regarding communication, having a contractor to lead the changes simplifies the process. I give this review a rating of 10.