Camunda Reviews

We use the BPMN flows for order capturing of our end-to-end customer journey. There are many intermediate flows and we mainly use the tax delegate part of it.

We have been able to save costs using this solution compared to the product we used before.

I have faced problems in bringing up the Cockpit in terms of GUI processes. I think that there is room for improvement in those areas.

We have used this solution for one year. 

This is a stable solution. 

We have a support contract this has been working fine for us till now.

We previously used a product from Ericsson. 

The initial setup is a bit complex.

The learning curve is a bit steep. I would rate this solution an eight out of ten. 

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. 

Our primary use case for Camunda is as a process orchestration layer to help prioritize tasks for users as they were designing downstream systems. Camunda is a way to push the rules to the downstream systems. We are partly a reseller, but we also implement and we are the systems integrator. I'm the vice president and account CCO of our company. 

One valuable feature of Camunda is that it's an open BPM, so it was easier for users and developers to work together to define the rules and define the process, given their BPM and standard architecture. This also allowed us to expose the rules and the business process itself into a standard model, which wasn't possible with other tools and softwares we've used in the past. Finally, the engine itself is lightweight so it was easier for us to handle deployments and in production it didn't have a great demand of the infrastructure.

I think there is room for improvement along with the process. Camunda doesn't have a strong forms designer. While that is an advantage in one scenario in that we were able to bring a third party UI, it was lacking in forms visualization and it would be good to have some kind of a strong forms designer that allows development along with the process.

More often, we are seeing BPM used in conjunction with other automation technologies like RPA and AI. If Camunda were to be placed as a central BPM, it would need a better integration mechanism.

I've been using this solution for two years. 

I would rate this solution a seven out of 10. 

We're planning and exploring moving to the Enterprise Edition. We find some functionality for the migration to be helpful for us. This is why we might move to the Enterprise Edition.

We are currently using Community Edition and then looking to move to Enterprise Edition possibly soon.

We are using the latest version of Camunda BPM. We keep upgrading to each new release. We keep always moving with less change. There are a lot of features in Camunda BPM.

We are documenting all of the processors and VPN. Then we share it with our business users so they can approve our other process. From the technical part, what we did was exposing Camunda BPM as a web service.

We configured a split between the process and the business. If there are any changes in the business, we are changing it in the process. If there is no impact, we don't need to redeploy our configuration settings again and again. 

This was something that saved us time and improved our data center processes.

We were discussing Alfresco. They were saying that their product is much better than Camunda BPM. We signed the governance policy for "Cloud First". 

When you search for Camunda BPM resources or books on how to utilize Camunda BPM, it is lacking. When it comes to Alfresco, there are thousands of resources that can help you to utilize within AWS and its Group Services. I would like to see the usage of Camunda BPM on Amazon Web Services be improved.

For Camunda BPM, the sense of community is lacking. The company itself is based in Germany. Alfresco is a very small company with an open source community. It is really good and it works perfectly. It was easy for us to adopt it. 

We are proposing that Camunda BPM can be offered as a web service. What could be improved is better support for AWS and training provided with the platform to make it easier to use.

Camunda BPM is very stable.

We didn't experience any issues with the scalability of Camunda BPM. It has good scalability by default. We are in Information Authority and we're looking on behalf of other government agencies, i.e., the civil service correspondence system.

We are creating different systems for the VPN to meet the processes. We are using Camunda BPM for 200 to 300 users. We use it almost every day.

We took responsibility for the setup and it was straightforward with community help

We implemented the setup of Camunda BPM on our own. We did everything in-house. Within a week, it was done. We implemented pretty fast.

We're very strongly recommending Camunda BPM. It is good. It is easy. The community is good. There is a lot of support if you are stuck anywhere. You can Google it and find the answers. Many people are using Camunda BPM worldwide and finding the responses was easy. 

I would rate it an eight out of ten. The reason why I wouldn't rate it a 10/10 or higher is that there are some other features available within other tools that can improve the algorithms they are not aware of yet.

Camunda BPM satisfies our requirements and we have been using it for a year.

We use the free version because our organization is a consulting organization and we work normally for customers. My primary use case is for training and modeling purposes.

I use the BPMN and the DMN model. 

The most valuable feature is that it is easy to use. I train my colleagues and customers and I don't want them to need to learn how the solution works. I want to be the one who learns about the product and teach them BPMN. 

It's user friendly, much better than most tools I have seen.

The documentation could use improvement. 

I have been using Camunda for two years. 

For modeling it's very stable. At the execution level, I don't have experience.

I think it is scalable, but I don't have experience with scaling it. 

The initial setup of this platform was very simple.

Often more functions will make a model or tool more complex. I like the simplicity of Camunda. It is very easy to use. 

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 a bank and use this solution for process modeling, organizing, and process architecture like line of business, and to be able to make process interfaces between each diagram. Activities include client enrollment, or a client account opening with a process for loan granting, which can't be done in Modeler. We are customers of Camunda and I'm a process analyst. 

The most valuable features are the ease of use and the ability to streamline a process model on a BPM diagram.

Process interfaces between diagrams could be improved. I'd like to see process interfaces and structure in order to make process architecture. Not only to lift diagrams, but to make new diagrams and new data. You can make new diagram and new data but if the client wants to open a current account, then it must be a process interface. It would also be helpful if they would publish processes in a format that can be easily viewable and understandable. The main area would be in publishing because we want to have all the processes published on our intranet. 

I've been using this solution for six months. 

The stability is fine although we did have some initial problems with it. 

The solution is quite scalable and functional. We have seven to 10 users doing process modelling. They're focused on archiving processes.  

Technical support is fine, although a little slow. 

The initial setup was very easy, I did it myself. 

As a process analyst, I'm into IT development, so my advice is not to make processes highly detailed. The value added here is the freeware version that can give you the best tool to get the job done as a process analyst. 

I would rate this solution an eight out of 10.