Camunda Reviews

We have a team that analyzes our existing processes. We discuss the manual processes currently in place within our company. We work on defining and representing these processes through block diagrams. This helps us to automate them. The processes in which we use the solution include customer order processing and quotation requests. 

Using the BPMN helps us to have a common shared communication language when discussing processes.

The tool's most valuable feature is BPMN diagrams and the possibility to automate processes.

The Camunda Modeler installation poses a challenge, requiring local installation, which doesn't help collaboration like other online tools, for instance. Camunda needs to improve its user interface.

I have been working with the product for 4 months.

The tool is very stable since we run it on-premises. 

Camunda is scalable. At present, my company has three users. By next week, four more users will be added. Over a couple of weeks, a few more users will be added. 

I have not contacted the technical support yet. 

Camunda's deployment is easy. You need to click some buttons. 

I did the tool's deployment myself. 

We use Camunda's community edition, which is free. 

I rate the overall product a seven out of ten. 

We use the Camunda platform for workflow management.

The architecture is good because it's a headless workflow. I can create my own frontend, and it's fully API-based. Our approach is more flexible, so I can use the Camunda API to generate my own workflow blueprint. 

Additionally, it's cloud-ready as we have deployed it on the Kubernetes container platform, which aligns with our cloud-first architecture. These are the aspects we like about Camunda from the IT side.

Camunda lacks sufficient dashboards for operations and reporting. Although I can create dashboards and reports using the provided framework, it's not as enterprise-ready as some of the competitors in the market. They offer ready-made dashboards that are easier to create compared to Camunda. That's an area where Camunda can improve.

So, in future releases, I would like to see better dashboards.

I have been using Camunda Platform for a year. 

I would rate it around seven out of ten. We haven't encountered significant issues or unavailability of services.

In my organization, at least 100 users are using this solution. I would rate it an eight out of ten in terms of scalability.

It requires maintenance such as patching and other regular tasks.

I would definitely recommend it. 

Overall, I would rate the solution a six out of ten because Camunda does not provide a prebuilt interface. I have to develop it myself. To provide a comprehensive product to my business users, I need a frontend. The frontend provided by Camunda vendors is very basic. Most of the vendor's customers develop their own UI or frontend using technologies like React, React Native, or JavaScript frameworks. 

So I rate Camunda Platform a six out of ten due to the incomplete delivery of a frontend. Without a proper frontend, the business cannot effectively use the platform. This is an area where I'm still exploring how well the competition performs. That's why I'm giving a slightly lower rating. However, in terms of orchestration, API capabilities, and cloud compatibility, Camunda is very good.

I have used IBM BPM and Newgen in the past. We are still using IBM BPM alongside Camunda.

We're using Camunda as an SI integrator. We are currently working on becoming partners with Camunda but for now, we're customers.

Camunda provides an easy way to integrate with the architectural environment and it offers us flexibility.  

I'd like to see a number of preset features and configurations included in the solution to make it more of a plug-and-play kind of product. That would help us in terms of our customers. 

We've been using this solution for six months. 

The solution is stable. 

Camunda is not a huge company and they haven't yet reached a critical mass of users but the customer service is good and efficient. 

In my previous job, we used Appian and I've also used IBM BPM. When I switched jobs I chose Camunda because I found the initial setup to be easier and it's very user-friendly for the projects I'm working on. In some instances, it might not be suitable such as in a bank where there are over 300 processes. In that case, IBM BPM might be a preferable solution, but I don't see much advantage. 

I was responsible for the deployment; we had one person dealing with the structure and another for the implementation. The initial setup was straightforward and fast. Everyone in the company uses it, we have around 200 employees. 

We've seen a return on investment in terms of processes and that was apparent quite quickly.

There's a community version where you only pay for the support or you can choose the enterprise version depending on your needs. 

We evaluated Appian for my current job but it's less beneficial if your aim is to have your customers at the front end. We took the middle road when we went with Camunda and the flexibility it offers is a big advantage for us. Appian and IBM don't provide a community version and for the enterprise version, Camunda is an affordable solution. 

If you're looking for flexibility, this is the solution. There's no super bullet that does everything but the flexibility Camuna provides is a good start. 

I rate this solution eight out of 10. 

I use Camunda Platform for trainings. I teach people how to develop process application. I am helping people understand what Business Process Management Suites are, what they can use it for, and their advantages. I am a trainer and a consultant, but not a reseller.

We use the open-source free version so we do not pay for support.

Because Camunda has various versions, there is the Platform itself, which contains the process server, and there is the Modeler, and it is distributed differently and used for different purposes.

I think that the positives of Camunda Platform are that our customers can start with the free version. I think it is the most important.

I do not recommend anybody use the free version for production without paying for a support subscription. I always recommend to use the free version only for testing and learning purposes. And I think for that purpose, it is perfect.

There are a few things that I'm missing. For instance, the user interface creator, which I know other systems have, like Aurea or Lombardi, which are IBM solutions. The interface creator, including the data model creator or some module which would allow the users who are not programmers or business consultants and who are not technically skilled in database and Java programming, to create data models and user interfaces. I used to use have this with Savvion and Aurea BPMs.

I am using the Camunda Platform for about six years.

Because we use it only for learning purposes and the solution is not used by more than four - six people at once, we haven't faced any issues.

Our purpose is very simple, it is only for trainings for our customers who come to us to learn how to create process application. I do about four trainings a year and they usually have from four to six attendees. So it's about 20 people per year who have access for only two months each.

They receive the access to their personal account for two months. They receive it when they attend the course and they have access two months after the course and then the account is closed and the tenant is deleted.

In terms of how much staff is needed for deployment and maintenance, it is just me and one programmer.

Hard to say if we will increase usage. I am in communication with another company which is developing their own process platform, so maybe I will switch from Camunda to their platform in the future.

We have been using the community very often, but we haven't tried to contact support because we do not pay for the support.

I did use two platforms intensely in the past. I worked with the IBM Business Process Suite. It was later replaced by the Lombardi solution. Then I was working with and implementing Savvion, which was later bought by Banerjee and now is represented by Aurea Business Process Management Suite, which is still my favorite.

I met in-person with Mr. Ketabchi, who is the father of Savvion Business Process Management Platform and I really believe that it is a very well designed solution and very user-friendly for the business consultants and business process analysts. It is my favorite one. After Progress Software divested this solution and created the Aurea company and distributed it from there, Aurea managers decided that our market is too small for their interest, and we had to search for new solutions.

Then we switched to Cordys and we became a partner Cordys for Central Europe, Poland, Czech Republic, Slovakia Republic and Hungary.

We implemented Cordys to at least one important customer which is East European broadcasting, TV broadcasting corporation. But then Cordys was diverted by Mr. Baan, the founder of Cordys to OpenText, and again OpenText changed their sales policy. So again, our market is too small for them.

We were searching again for another solution. So the next in the queue was with Bonita and Bizagi, but finally I decided for the free version of Camunda because at that time I only needed something for training purposes because six years ago I started to concentrate on trainings for business process analysts and consultants and for trainings in the area of process automation.

The initial setup is not too complicated.

We started with the analysis. The implementation depends on what you are asking for. We had a few discussions with the developers about what I expect and they developed and implemented it in about two months with about 10 days of work.

I have to say that the developers I cooperated with had previous experience with Camunda.

The price is for support, because as far as I know, Camunda doesn't sell licenses, it provides service support, not the licenses. It is a difference. Because you don't buy a license, but you do buy the support services. I think that for the support services, the price is very fair. And if I would go for the project, I would surely decide for Camunda because the yearly support price is very fair. I don't remember exactly. But at that time, when we did the calculation, it was about €20,000 per year.

My advice to anyone considering Camunda is that I recommend to use the free version for trainings and for testing and for not very crucial process automation for pilot project purposes, but not for production and not for key processes. For key processes and for production, I always recommend to buy the support.

On a scale of one to ten, I would give Camunda Platform a 10 for sure.

It's very good. But it depends on what you are expecting.

For other purposes, there might be something else which is preferable. It is not easy to say there is one business process management for all purposes, for all companies. I would recommend Camunda for either small or middle-sized companies.

I would not recommend it for corporate uses because to integrate in this scenario requires much more extensive and intensive technical work for integration with the usual applications, et cetera. Therefore, Bonita or IBM Business Management Suite, for example, already have many thousands of connectors to Salesforce, SAP, ERP Systems, Microsoft systems, et cetera, whereas with Camunda, you are almost in the beginning and you have to develop everything by yourself. So for larger companies, the implementation might be too long and too expensive.

I use the solution in my company for process modeling and collaborations with other users.

The most valuable feature of the solution stems from the area revolving around process modeling. It is possible to take care of the process modeling with BPMN. I think the most beneficial feature of the product is that the tool serves as a process orchestration platform and also helps in the area of process automation.

Camunda should be able to automate the processes in any department, like the ones in HR that are related to procurement or any others, which are repeated in the same manner without any significant changes in the process, as it is one area where the product faces certain shortcomings.

I have been using Camunda for about three years. I am a customer of Camunda.

It is a stable solution. I have not faced any trouble when using the product in my company.

Camunda is a scalable product.

Around 10 to 15 people in my company use the product.

I have never contacted the solution's technical support.

The product's initial setup phase is difficult for beginners.

The solution is deployed on the cloud.

The product's price depends on the number of processes that need to be automated or where the orchestration part needs to be used. The product is affordable for medium and large enterprises.

My company chose Camunda since we wanted a tool for process modeling with BPMN so that we could automate some of our processes.

I recommend the product to those who plan to use it, as it is a simple and practical tool with powerful capabilities.

The product helps achieve operational efficiency in our company since it helps with the process modeling area. The product also helps automate and orchestrate processes effectively.

Camunda's user interface's contribution to process modeling and deployment stems from the fact that it is pretty intuitive and simple.

It is easy for someone to learn to use Camunda.

I rate the overall tool an eight out of ten.

We process credit card applications using Camunda.

Camunda's process diagram creation and deployment is very easy. You can model the business processes very easily in Camunda.

The solution's pricing and scalability could be improved. It's very difficult to know how to really scale the solution. It would be nice if information is made available about case studies where people have scaled Camunda to a larger set of requests per second and how they did it. We really struggle to scale up the solution.

I have been using Camunda for one and a half years.

I rate Camunda ten out of ten for stability.

We have a back-end integration. So, no user logs in to Camunda on a day-to-day basis. One or two developers log in to the solution when there is some issue, or some application gets stuck.

I rate Camunda a five or six out of ten for scalability.

I posted some things on Camunda's community channel, and I found the community helpful and nice.

I previously used Apache Activiti. Apache Activiti does not have much community activity, but Camunda's community support is very nice.

It took around a week to deploy Camunda by one or two people.

Camunda is deployed on the cloud in our organization. I would recommend Camunda for low to medium-scale businesses. I would not recommend the solution to high-scale businesses because of the lack of documentation.

Camunda is the right choice for long-running business processes instead of ones that can be finished in a few seconds or minutes.

Overall, I rate Camunda an eight out of ten.

Our deployment is not live yet. We are in the process of building it.

We make basic use of this solution. It is embedded within a code module that requires workflows. Essentially, Camunda is used to keep track of workflow activity. So, we're not making massive use of it. Rather, we're making use of it as an embedded microservice.

The most valuable features are that it's lightweight, can be embedded in existing Java code, and keeps track of the workflow state and the instances that we need.

The development team had a lot of issues at the start. Guaranteeing the execution times that it will work to is difficult. It's an embedded state machine, although it doesn't give you guarantees of when it will update the state. It can be quite difficult because you can get into timing issues, which is a real pain to sort out. We were able to resolve this by writing a wrapper around it. You have to be very certain that the transactional integrity is provided to the API user.

In the future, I would like to see better transactional integrity.

We have been building the Camunda Platform for approximately two and a half years.

We use it on a daily basis and apart from the timing issues, we haven't had any problems. We have been doing a lot of heavy testing because it's a big, National system.

Scalability-wise, it's fine. It sites within the Kubernetes nodes and scales with those.

I am the technical design authority that chose the product. A whole team of developers is working on it. As it's not live yet, the users are testers and developers, and there are approximately 40 of them.

When it goes live, there will be several thousand users, but that won't be until next year. In terms of expanding usage, potentially, we might because there are a lot of workflows that we could map out of the current one. The one that we are doing now is quite complex and we needed to embed the service. Potentially, it could go across the whole of this business area, which is something that we are thinking about.

We contacted technical support when we had the initial problems with timing, and they were below average. We ended up having to resolve the problem ourselves by writing a wrapper.

We did not use another solution prior to this one. It was all greenfield development.

Camunda is easy to set up. The initial setup was fine until we had an issue with execution times not being guaranteed. That took quite a number of weeks to resolve. 

We developed this platform on-premises and we deploy through AWS.

We brought some people in to assist with our implementation. They were supposed to be experts, but they weren't that great. They wanted us to make much wider use of it, and we only wanted to use it quite in a small way. So, we paid for a bit of consultancy, but then we didn't keep them on.

They were typical London consultants. At £1,800 (approximately $2,400) per day, they were ridiculously expensive.

It is only a small team that maintains it. Right now, we only have one person for that.

We are using the open-source version, free of charge. We didn't bother with the enterprise features. We did look at the enterprise features for the MI component but we ended up writing our own.

More than two years ago, we did a lot of work evaluating Camunda and other products. The two other solutions that we looked at were Pega and Appian.

Pega and Appian were much larger than Camunda, so they didn't meet the criteria of being lightweight. They had a lot of features, which is something that we took into consideration. However, if we were going to extend it to all of the other workflows then these other products were not quite right.

My advice for anybody who is implementing Camunda is to pay attention to transaction integrity. The biggest lesson that I have learned from using it is to do a little bit more architectural spike work before committing to all of the development.

Overall, it is a pretty good product but there is room for improvement.

I would rate this solution a seven out of ten.

The majority of my research work pertains to financial organizations, specifically, credit processes, loan origination, and appraisal of loan decisions. The majority of my clients are financial institutions.

Having knowledge of the BPM and monitoring process has proven to be very beneficial, as I am currently engaged in documenting processes for Clientele. 

The BPM has been of real help because I'm knowledgeable about the BPM and monitoring process. I've been in the process of documenting processes for Clientele. 

Although I have acquired knowledge about process automation, I am facing a challenge in implementing it for one of my clients due to various reasons such as some of them still using legacy systems or undergoing changes in their core banking software. However, I am eagerly looking forward to the opportunity to implement a process automation solution for one of my clientele.

The primary issue regarding the Camunda platform is its high cost of training. This is why I haven't discussed it extensively, as compared to other products that are more affordable in terms of developer training.

For instance, if I were to compare a Process Maker who provides free training with UiPath, which is also free, and then with the Camunda Platform, the latter requires payment for its services and verification procedures. The amount charged by Camunda is quite substantial and not negligible.

As you can see, I am unable to carry out any implementation without having received prior training, and this has been a major disadvantage of using the Camunda Platform.

I would like to see the pricing improved.

I have been using the Camunda Platform for approximately a year now.

I am working with the community edition. 

I am not aware of the version that we are using, but I don't believe that it is the most recent version.

I haven't had the opportunity to test the solution in an actual working environment yet, as it seems that you haven't deployed it either. Although I have used a modeler extensively, I haven't been able to deploy a solution to a client, so I can't speak to its stability.

It is my understanding, that the solution is highly scalable, but I haven't had the chance to test its scalability. 

I haven't encountered any issues with the solution crashing, so I don't have any experience in troubleshooting such problems. 

However, I'm willing to experiment with the different versions I have and try to find a solution if any issues arise. 

We currently have three users.

Our original plan was to implement this solution for a client. However, I found it challenging to promote the product without having the necessary technical expertise to modify the code in certain areas. I had to go through additional training, which, as I mentioned earlier, was a disadvantage since it made me hesitant to deploy the solution in a financial institution.

I don't believe I have the necessary accreditation or certification to deploy the solution. I haven't undergone the required training or been formally verified as competent in this area.

I haven't reached out to technical support since the community version doesn't offer it unless I seek assistance from the forum.

Setting up the software development process is not difficult for me because I am knowledgeable in this area.

Since the process is mostly Java-based, there is no need for me to do any training. However, the aspect of training poses a challenge due to its high cost.

The initial setup was straightforward. That was what I was able to accomplish. 

It took me approximately two to three hours to complete the task. I had to refer to tutorials and make some adjustments on my computer, which consumed some time. As a developer, I found the task relatively easy to handle.

I deployed it. But it was not a major inconvenience for me. It was deployed a year ago.

In Africa, the cost of deployment is an important factor to consider since it adds to the overall cost. This might be the only drawback to using it.

Licensing fees are paid on a yearly basis.

It's an expensive solution.

Having learned about BPM, I gained valuable insights from one of the key contributors to the ONG group, a prominent founder of the organization who is also involved in the development of Camunda. Based on my experience, I would strongly suggest this solution to anyone seeking to implement a robust Camunda Platform.

My recommendation is to ensure proper documentation of the initial processes. This is because one of the challenges faced by our clients is the lack of documentation for their processes.

The challenge lies not only in defining policies but also in documenting end-to-end processes. During the documentation process, it becomes apparent that some knowledge is retained by individuals rather than being stored in a centralized procedure. 

Before considering automation, I recommend prioritizing process documentation. This ensures that all critical information and expertise are centralized and easily accessible, resulting in a more successful automated implementation.

I would rate Camunda Platform a six out of ten.