Camunda Reviews

We are using it for one of our workflows. We are not using the user interface per se. We are making use of JavaScript Angular for the UI. So, we're just using the engine part of Camunda.

We are using its latest version.

The ease with which I can define workflows is most valuable. The latest updates and flexibility that it provides around a task activity are interesting for me.

Community support is basically what I'm looking for. Other than that, it is okay for now.

I have been using this solution for the past one and a half years.

Its stability is okay. As far as the performance is concerned, we have our internal architectural constraints, and because of them, it is unstable, but it specifically has nothing to do with Camunda.

It is easy to scale. We have about 50 to 60 users, and it is used on a daily basis.

We used to use K2. We changed from K2 to Camunda mainly due to the licensing cost issues.

It was simple. It took us about three or four weeks to deploy the first portion or first draft of BPM.

In terms of maintenance, it is okay. It doesn't require anything specific.

We did it internally.

Its price is decent. Everything is included in the license.

The Community version is also good to start with. We are using the Community version.

It is loosely coupled. Therefore, there is a lot of flexibility in the way we want to restrict the usage of Camunda. 

I would rate it a nine out of 10.

We ran two proofs of concept, but it was on internal processes. Both processes were related to the human resources area. Right now, the IT central area is working on a service to optimize using Camunda.

We use the community version, and we use Cawemo Platform to start modeling and involving the areas. We pass the models to the IT central area, and they go on with the job. I work for the government of my state. I work in a central area, and we work with BPM, so we were trying to find a solution for automatization. That's when we found Camunda.

We are trying to transition the environment and trying to see the use for it in the future, but right now we are running one project specifically.

When we ran our first proof of concept, we had some aid from an external company called Memora, which is a representative here in Brazil. They have high-quality technicians. The first project was really a success.

We don't have specific key users because we are trying to understand how to use the solution in order to provide public services for the citizens of our state. They are solving some technical issues and trying to integrate the solution with our internal IT environment.

The idea is using the community version in order to provide public services, but not all services, because we have a traditional program system development. They are considering buying a local tool, and they are considering Camunda Platform.

We are using the newest version of the solution.

We like the idea of working with Cawemo because it enables us to keep on working, remotely or not. It allows us to collaborate between areas. It's easy to model and easy to use. It's a great tool for communicating at the beginning of a project.

The business model could be easier to understand.

We started using Camunda at the beginning of 2020. We started researching and using the Cawemo solution for modeling, getting the idea, and knowing the environment. That's when we decided to run a proof of concept. It happened in the middle of 2020.

During 2021, we had some issues concerning coronavirus, so things stopped for a while. Right now, the central area responsible for IT restart is considering running another proof of concept on Camunda.

It is stable.

The solution is scalable.

I tried to get some information about buying the license for the solution, but I found it kind of hard to understand the business model. That's why we're currently using the community version.

I would rate this solution 10 out of 10. 

My advice is try to understand and use it because it's really an amazing solution. I only have nice words to say about it. I really hope our central IT area runs this proof of concept, and that it becomes successful in the near future so that we really start offering public services on Camunda Platform. It's easy to use, stable, it integrates areas, and you can use the community version.

We use it for the public sector. Currently, we are only modeling the processes, but in the future, we would be automating all the processes. We are at the first phase of the process.

It is simple to use. The user experience is very good.

In terms of features, it meets my needs, but I would like Camunda to have an office in Brazil and provide training in Portuguese. They should provide regional support and training courses in Portuguese.

We have been using this solution for a year and a half.

It is very stable.

It is scalable for what we need. We have five people who are using this platform, and we plan to increase its usage. We are implementing it in some of the remote offices, and we would be able to expand it next year.

We are using the community version, so we are not using their support.

It was very simple. We are using the web solution, and it was very easy and quick. We could start using it in one week.

We are using the community version. There is no licensing cost.

We are beginning to use it for modeling some areas in the public sector, and there is no problem. I am yet to use all the features that Camunda has. For me, it is a complete solution at this time.

I would rate it an eight out of 10.

It is used in the same way that Azure and IBM BPM work.

We use the Camunda Platform for Banking services.

Camunda Platform is better than IBM BPM, and Azure. It is more elaborate. 

It is divided across the platform.

The integration is separated as well as the UI, and the internal work.

It also integrates well.

I would like to see better pricing.

I have been using the Camunda Platform for a couple of months.

Camunda Platform can be deployed both on-premises and on the cloud.

We are not using the most recent version, but an internet version while the Cloud version is being developed.

We are currently using the Enterprise Edition.

The Camunda Platform is stable enough.

Camunda is a scalable solution.

We have 10 to 15 users per site.

We have not contacted technical support.

The installation is quite straightforward.

You log into the Camunda website and download the folder to install it directly.

The installation process took 20 to 25 minutes.

We configured the integration and the UI.

Generally, the price could be better, as well as the licensing fees. 

We have not yet explored all that Camunda Platform offers.

We would recommend this solution to others who are considering using it.

I would rate Camunda Platform a nine out of ten.

We use Camunda for the automation of the workflow and business process designer. We use the module cockpit and the workflow engine to orchestrate the process. We are a consulting company and we're not doing this for internal purposes. We mostly do this for projects, and these projects are for our clients.

The environment where we work is very dynamic and is changing a lot. So based on the circumstances, we mostly work on the delivery parts, as in project deliveries. At the beginning of the year, we have a clear scope, clear targets, but down the road, we face a lot of challenges where we face many dependencies. We need to constantly go around the dependencies and change things back and forth.

We have a lot of experience in the development, on the ERP, and so forth. We have seen that investing in a tool like Camunda is valuable, especially because it's an open-source product. When you do the customization, you'll be enriching and increasing the automation possibility of the product. So, the value is always increasing.

The best feature is the automation.

Camunda supports microservices and you can do multiple things. The most important thing is that you can reuse components that you have within the product. For example, let's say that I developed a workflow for a quality review; that is a workflow that can be reused in any new process. I can just ship it, plug-and-play, copy it, and reuse all of the features and components that are there. It means that I won't be spending too much time in terms of development to put it in place. To me, that is the most valuable thing about the product.

The only drawback is the time that it takes to have a complete set of workflows implemented on the Camunda platform. This is from drawing the modeling and the workflow up to the production release.

The support definitely has to be improved.

Second, it needs to be more intuitive. As it is now, to develop an automated process in Camunda, you would need to involve a front end developer, backend developer, and sometimes, someone who has experience with modeling. Where in Appian and Pega, you would be able to simply reduce these overheads by creating the process, the flow, and converting it within certain boundaries into the automated process.

The visualization part can definitely be improved. You can see the process moving live, but if you have a complex design where you would like to show the process in a different shape, that takes a lot of customization and a lot of coding effort to put this in place. The visualization needs not a little or a medium amount of work, but rather, it requires a lot of improvement. At the end of the day, we have the process, we have the workflow, we have the event, we have everything. However, what the people see at the end of the day is what they believe. So sometimes we know that we do have a lot of data and a lot of information, but we fail to represent this information in a way that meets or addresses the business requirements. Better visualization capabilities would help in this regard.

I have been working with Camunda BPM for almost two years.

I would say that it is stable, at least up to a certain extent. Whenever there is an update to the product available, we go ahead and update it to the latest.

This is a scalable platform. We have about 600 users and about 20 superusers. The superusers are developers, admins, and process engineers. They are a mix of process, business support, mobile app developers, and so forth.

Support is an area that is in need of improvement.

First, they don't have a strong knowledge center. If there is a challenge or there is an issue and you would like to look around, it's not straightforward. Their knowledge center does not address most of the challenges that a person who goes through the cycle from scratch. In building the process and building the products and building the workflow, a person will go through a painful process if they don't have enough experience.

When I say enough experience, I mean a minimum of 16 to 18 months. If someone doesn't have this experience on Camunda, it will be difficult and they will suffer to get things up to speed. The learning curve is too high, so they can do more if they enrich their knowledge center.

The second problem is that the support services from Camunda are not straightforward. When we communicate with them, they have to evaluate you. Sometimes they charge you per workflow, but there is no standard model. It is difficult for us because we have an agreement with the client that at the beginning of that project, we put in our estimation as to the required resources in terms of the infrastructure resources, and in terms of logistic resources, and support. With Camunda, because of the undefined or non-standard costing, that becomes a challenge.

So sometimes we go to a client and we see that the support costs will be much higher than the benefit of the digitalization. That's an example where we decide to do only the modeling for that client using Camunda and the classic workflow development will take place. This is the case, especially for small and medium businesses. For enterprise clients, definitely, we always go with full-fledged support.

I have limited experience with Appian and Pega BPM, but my most in-depth experience is with Camunda BPM. We did a pilot project with Appian for one or two months and we did one with Pega for about one month.

During our evaluation, we have seen that there are pros and cons to all of them.

We also used K2 as one of the platforms, as well as Microsoft BPM. The Microsoft product was a combination between Dynamics and SharePoint and so forth, it was really rigid. Similarly, K2 has a lot of limitations.

This is important because once we get the business requirements, we adapt to the system. We don't force the business to change, especially in this region. We are in the Middle East, Gulf area, and working with the government sector means that they have their own standards that we need to comply with. They have their own procedures where the tools, the IT, and the process have to be adjusted to meet their requirements. For example, consider a supply chain and the procurement process. This is different from one organization to another.

This is the main thing that holds us back from investing in a system like Pega. Pega, to a certain extent, is good. It has most of the capabilities. It also gives you the room to customize to the extent that you feel fit. However, the cost is too high. When we talk about the licensing costs and the customization costs, it's extremely expensive and out of reach.

The initial setup was not straightforward. The complex part was to load or update the backlogged events. So if I have a process, which is already past the flow to a certain stage, after the implementation, if I did not start from scratch, you would need to make the data or the workflow that you have current with the process. Making it current with the live process monitoring is a nightmare. It takes a lot of development effort, a lot of data validation, and a lot of workarounds to bring this up to speed.

I have not seen that there is too much support in being able to bring in existing services. For example, if someone has an existing process, an existing instance with existing data, which is not linked, there is no explanation of what the best approach is and how to load and how to bring this into the new process and make it current, covering the backlog.

This is especially true if the backlog is something that would be crucial for some of the processes that are down-line. For example, in the case where you have a successor process where it depends on the predecessor too much in terms of the decision, and also in terms of that project. Normally, we deal with delivery on projects, so we look at the delivery and the forecast and the delays. So to see the project delays, sometimes we need to go back in time to see whether the delay was in the first stage or on the second stage or on the third stage. Based on this analysis, we always create our baseline by the end of the year and reiterate on our scopes at the beginning of the year.

We have an in-house team of two resources that maintain the product.

The cost of this solution is better than some competing products.

My advice for anybody who is considering Camunda BPM is that they implementing a PoC first.

I would rate this solution a six out of ten.

We use Camunda Platform for automating networking business processes.

The most valuable feature of Camunda Platform is its Microservices architecture, which is easily integrable with APIs.

Camunda Platform's customer support could be improved because their response is quite slow.

I have been using Camunda Platform for approximately one year.

Camunda Platform is a stable solution. However, we recently lost a lot of data because the solution's database was down.

I rate Camunda Platform a seven to eight out of ten for stability.

The solution's initial setup is quite straightforward. I rate Camunda Platform a six or seven out of ten for the ease of its initial setup.

Camunda Platform's deployment was done in a day.

Compared to other software, Camunda Platform is quite cost-effective.

Overall, I rate Camunda Platform a seven or eight out of ten.

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. 

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.