Camunda Reviews

We have multiple B2B services running for our customers. We have approximately 120 workflows and are eventually migrating everything to the Camunda Platform. We have approximately 25 workflows on Camunda currently running.

The headless nature of the Camunda Platform is something that has helped us to build our own logic and platforms on it.

The cockpit features of the Camunda Platform can be improved to make it a bit more user-friendly, in terms of providing a bit more user experience for non-technical users. There could be some additional documentation added.

I have been using the Camunda Platform for approximately one year.

I would rate the stability of the Camunda Platform an eight out of ten.

There are some improvements needed.

The solution is scalable, it can fit any size business.

The technical support is good. However, the agent is not in the position to understand our use case for them to report to us on time. The speed and training of the support agents could improve.

I rate the support of the Camunda Platform a seven out of ten.

I have used K2 and some other workflow solutions previously.

The initial installation was not difficult for us because we had already some experience with the solution.

The price of the solution is reasonable. 

My advice is you have to be a bit optimistic and you need to see if this solution is the right fit. You have to determine if you are looking for a low-code platform or a headless platform. There is a misunderstanding between multiple products and the Camunda Platform being a headless BPMN, it is not a low-code platform.

I rate Camunda Platform an eight out of ten.

I'm the Leader of the Center of Excellence at my company with 18 years of experience in BPM platforms, and my team works with Camunda on several different projects where we deploy Camunda either on-premises at our clients' sites or through the cloud.

Our clients that are using Camunda range from a large enterprise media company in Brazil to banks and central industry (e.g. energy industry). We have found it to be very useful in multiple segments of any enterprise. We now have about 1,000 users of Camunda in all.

I love that Camunda is a very developer-friendly platform, and my customers have evaluated the pricing as reasonable. Personally, I also like that the Camunda platform as a whole helps us to easily measure the life cycle of all the relevant processes. For example, the Camunda platform includes Cawemo for business analysts, Cockpit for process engine configuration, and modeling tools for developers. Then you have Optimize, which is helpful in managing processes and continuously improving on them.

We haven't run into many problems, because Camunda provides everything we need to delegate solutions for all the technologies (for example, Java clusters) and programming languages that we use. However, I do think that Camunda can try to do better when it comes to solving the complexities of all the products in its software stack.

I have been using Camunda for eight years.

Camunda is very reliable but you need to understand the process engineer execution in order to provide solutions that are synchronized and, thus, stable.

It's a very scalable platform in my experience. 

The Camunda installation is very simple. For example, if your project requires standalone applications, Camunda can provide the necessary external components to complete the installation. The setup can be a little more complex when compared with other applications such as JBoss, but overall it only needs a few extra configuration steps.

The evaluation of my customers on pricing is that it is reasonable.

I feel that the Camunda engine is a very scalable platform, and compares well with many other BPM platforms that I work with.

I would rate Camunda a ten out of ten.

Our primary use case of Camunda is for following a process in our applications. Camunda is a work process product. We are developing some applications and when we want them to follow a specific process, we use Camunda to help the programmers follow that process we want to achieve. 

We are using a version of the free service they provide, but I'm unsure which version it is. Camunda is deployed on-premise. 

The most valuable feature is that, with a visual system, you can try to have a process client before beginning the programming for the application. 

Camunda could be improved by making it easier to modify a process. You can program it to follow a process, but it is difficult to modify the process when the application is in use. It could also be improved by making it easier to use the visual platform without needing to be informed on that. Sometimes, we programmers haven't used it in the past, and it's a bit difficult to learn it. 

I have been using Camunda for two years. 

The stability is quite good. It's not used on a daily basis right now, but when we deploy the application, which is massive, it will be used daily. Camunda is stable, but there is some difficulty in changing the process. 

We will see how the scalability is in a few weeks, but we are going to do some trials and testing on the scalability. For the past two years, Camunda has been used to develop a new system, a very big system application, that is going to be used here in Spain. In a few weeks, it will be used by about 1,000 final users. As far as the programmers and technical people working with it, there are about 50 people. 

We haven't contacted technical support yet, but in the future, we will try to contact them in order to improve the platform and have new versions. We may go for the paid version, so we will have to contact them. We have been able to resolve any issues without contacting their technical support. 

I think the setup process is simple. It's not very complex because we have installed it several times for the development area and for the production and we have not had any problems. I think deployment took no more than about two or three days—it was not difficult. 

We implemented this solution through an in-house team. The installation was done internally, by the systems area in our company. 

Camunda has a free service as well as a commercial service. We are using the free service. 

In the future, we may pay for maintenance services. We haven't had to do any maintenance yet, but we plan to buy some package or product in order to handle the maintenance. 

I rate Camunda a seven out of ten. I would recommend the paid version of Camunda because of the difficulties we have had with the free version. It's easy to start using, but it's difficult to make changes. 

We are currently concentrating majorly on our clients in telecommunication. We are also working with new and existing federal clients and proposing Camunda Platform to them.

We are using its latest version. We are currently in the development phase. It is in our local environment, but we are planning to be cloud-based. Going forward, we will create a Jenkins Pipeline and deploy it onto the Azure cloud.

It is open-source. It supports microservice orchestration. This is what we are really interested in. We can customize our products depending on the use cases.

They have a migration plugin that can be used to migrate from one BPM to another BPM. It is in the beta stage since last year. If they can make it available in the market, it would be great. We are going to have a couple of migration projects for migrating from IBM BPM to Camunda, and this plugin would be useful. I have already discussed this with them two weeks ago and asked them to look into this and add it as a feature. We are expecting this plugin to be available in the next version. This is the only requirement we have at present. They keep on coming up with different features, which is helping us a lot. Its latest release that came out last month was awesome.

I have been using this solution for five years.

It is stable. I didn't face any issues in the production or development phase.

I have interacted with their technical support, and they are very helpful. When I have to work on any POC, I also directly work with the product team.

Its initial setup is straightforward.

I would advise others to verify the technology stack that they already have in place. They should check the orchestration part and see if they need to take care of any redesigning.

I would rate Camunda Platform a nine out of ten.

We have integrated Camunda workflow and decision engine into our solution that enables management and digital sales of products – Digital Product Center. We use mainly Camunda Modeler and Camunda Cockpit. For some implementations, we also used Camunda Tasklist.

Camunda is used to model and orchestrate processes. We have developed a module where for selected process steps, the user can build forms that will be used to present or gather data by the end-user.

Another module is responsible for defining the products, with business parameters, that an end-user will be able to buy on the platform. The link between product definition and process definition is also configured.

This solution did improve our product significantly. We were able to focus on the development of other modules that integrate with Camunda, and together provide a powerful tool for our clients. Using such a solution gives our clients great flexibility and a short time to market for new product implementations. 

Next to our product, we are also using the Camunda workflow and decision engine in other custom implementations. Our partners can benefit from open-source, as we did with our product, and thanks to that, we get more custom development contracts.

It is very important for us to have an engine that understands the model defined in the modeler, according to BPMN 2.0. This way, we can use the model for business and development purposes without extra workload. We noticed that the project team collaboration is more effective when we use a working process model.

Last but not least I can mention robust and flexible Camunda Rest API Integration, the lightweight process engine can be easily distributed as a microservice, multiple database support, pluggable architecture, and bpmn.io.

In the future, I would definitely like to see the process administration (migration, audit, tracking) and process evaluation (optimize) features added to the community edition. Right now, thanks to the pluggable architecture, we have built features that partially substitute the enterprise edition features.

We have been using Camunda Community Edition for six years.

We didn’t have any problems with the Camunda Community Edition on production installations. We do have experience with process instance volumes starting in hundreds a year and up to 10 million a year.

The Camunda BPMN Platform is very flexible and gives several options to deploy and scale it. Process Engine can be deployed as:

• Embedded process engine – in your custom application (ex. Spring boot application)
• Shared – Camunda deployed in Application Server or Servlet Container (can be a Spring boot app)
• Standalone instance - it can be deployed as a microservice

These options give you a wide range of possibilities to scale your application. From horizontal scaling to vertical. Moreover, it can be deployed on-premises, cloud, or private cloud, including autoscaling mechanisms.

We did not use another similar solution but we did have experience with homegrown workflow engines, embedded in business applications.

The initial setup is straightforward, especially with Spring Boot Camunda Starter. The configuration is in application.yml files.

We have an in-house team for deployment and maintenance.

There is an open-source version available, that in its core features (workflow and decision engine, modeler) is exactly the same as in the enterprise version.

My advice is to think about what is most important to your business case and choose the right version. You can always migrate to Enterprise edition.

When we started to build Digital Product Center, we evaluated several options available at that time. We decided to use Camunda due to several reasons, but primarily due to the most valuable features mentioned above.

We are using the community edition so it is hard to ask for extra features ;-) I fully understand that if we still want to benefit from the open-source version, there has to be a paid premium version, so that the product can be further developed.

The primary use case of this solution is for migrating IBM BPM to Camunda.

We helped our customer to reduce their licensing and operational costs to a larger extent by proposing Camunda BPM to replace existing BPM solution. They were very much impressed with the capabilities of Camunda BPM and started migrating to Camunda BPM

I like everything about the entire BPM that comes with the BPM suite. It's more intuitive and they are enhancing the product very effectively year after year.

It's a customizable product and it's user-friendly.

I don't see many issues with this product.

The migration strategy needs to be improved. Most of the financial institutions in North America are looking towards open source BPM to replace their existing existing BPM platform.Camunda has already started working on a plugin to mgirate any kind of BPM workflows to Camunda BPM seamlessly. They have just released a beta plugin to migrate Legacy BPM processes to Camunda BPM. If they make it as a full-featured version, that would be a lot of help with migration projects. 

I have been using Camunda BPM for six years.

We are using the latest version of this solution.

It's a stable solution. We have not had any issues.

It's highly scalable and offers high availability. We used eight in a containerless server and also on a shared server.

I have work with different organizations, particularly with Camunda BPM. These organizations that we have recently started with are still in the beginning stages of the practice. Previously, we had heavy usage and had to support two to three clients simultaneously.

Technical support has been very helpful, even during the RFP phase. If we needed to verify anything then we could speak to the sales head directly, as well as to the product team.

Previously, I worked with JBPM, which was an open-sourced BPM.

The initial setup was straightforward. We didn't have any issues.

The only issues we could have would be with our code.

When compared with the proprietary products, the pricing costs are much less, even though it is an enterprise edition. It's very minimal. 

My customers and I are very happy with the pricing cost and the features.

Pricing depends on the number of tasks we use.

Yes. We evaluated JBPM and Activiti BPM before finalizing Camunda

I would definitely recommend this solution, especially if they are spending a large amount of money using proprietary BPM tools, such as Pega BPM.

I would rate this solution an eight out of ten.

We had a client who wanted to use a BPM to track user subscriptions on their website. They had 20 steps from different areas and different people who wanted to join as new users of their services. 

We had to use Camunda BPM to track those services because they used to lose track of some clients in the past. They then had to spend more, add some more steps, and add new user subscriptions for months. 

The key here was always to track a new user and guarantee that they will get subscribed to their service in good time.

There's this graphic that tells you how many lines or how many tickets are in each step. In that way, you know where you stand. I find this feature very valuable.  

These are your bottlenecks, and you can see what the tasks are, the problems, see how much time must be spent on them. Then you can propose to fix it or make some improvements to make things go faster.

Documentation can be improved. Right now, the documentation isn't properly organized. We have a lot of documentation. We follow the instructions. We follow some blogs and videos on YouTube. But it doesn't feel like we have all the information we need to implement Camunda BPM.

I have been using Camunda BPM for two years.

Camunda BPM is a stable solution.

Camunda BPM is a scalable solution. It's a JAVA-based application, and we were able to install it in AWS and do all the things we wanted to do. 

The initial setup was complex. We really needed to study and understand how it worked. It was difficult because we didn't have enough information in the manuals.

We did what was said in the manual and then wanted to do more. We watched several videos, and we started to connect the dots. With our own solutions or conclusions, we were able to implement Camunda BPM.

We implemented Camunda BPM by ourselves, in-house. 

I think Camunda BPM can improve their licensing costs. It isn't easy to find clients with Camunda BPM licenses mainly because it's quite expensive. I think the license for an on-premise system is about $50,000, and that's expensive when you have only 100 users.

I used Bizagi before. It's easier to implement, but the problem is that you have to use their suite. You have to use their screen, their admin screens, or user screens. The UX and UI experience is also not good.

We decided to go with Camunda BPM because it gave us what we needed. That is, we can get inside Camunda and use only the tracker of the application. We don't need to use mandatory things like your pages or your web forms.

We can really code what we want and use it. We can create our own UI while using Camunda BPM at the same time. We really liked that because in my company specifically, we use a lot of UX, so all the UIs were very important for us.

Camunda BPM allows us to have a BPM bot with our own UI, and that's what we liked most about Camunda.

I would advise potential Camunda BPM customers to be patient. Perhaps all the information isn't available in one click, but it's possible to implement Camunda BPM, and it's quite flexible. It's worth a try.

On a scale from one to ten, I would give Camunda BPM an eight. 

We recently finished a proof of concept with Comunda, and it was successful.

Because it's a complete solution, you can start modeling to automate processes. We can also develop projects with a high degree of collaboration, which is precious for us, especially during this pandemic when we are often isolated.

Within our organization, there are roughly 20 employees using this solution.

The collaboration capabilities have proven to be a great asset during this pandemic. We can share, discuss, and develop the model together — from a distance. It's really helped us during these times of isolation.

As I mencioned, we've just finished a proof of concept, so our experience with the tool is still very recent. In general, it mets ours expectations.

Something that could be improoved is the capabilitie of integranting different modeling tools, in order to facilitate both the import and export of models.

I have been using Camunda BPM since January 2020. 

As we are still relatively new to this solution, I can't really comment on the stability; however, I know some people in the government who use this solution and they are very satisfied with the stability.

We have actually never need to consult technical support, so I can't comment on them.

I know that the IT team needed some help, fortunately, we have a good connection with them, so we worked together to set things up. In the beginning, it was kind of hard.

As we experienced some difficulties in the beginning, deployment took almost a month.

My advice: try it because it's a great solution.

On a scale from one to ten, I would give Camunda BPM a rating of nine. If the initial setup was easier, I would give it a ten.