Camunda Reviews

We use the solution for workflow processes of different sectors.

The workflow builder is valuable. The graphical interface is very beneficial. We can build whatever workflow we need. Currently, we are integrating the solution with our document management system. It acts as a repository for the documents. Inbound and outbound integrations are very easy.

The solution fulfills our implementation needs. The interface is user-friendly compared to Oracle. The solution is well-known in Egypt. Even government sectors are switching to Camunda. There are a lot of materials available. The technical team did a lot of self-study. Now, we can integrate the solution with our document management system and implement the processes we need. I rate the documentation a nine out of ten.

The product must provide more videos and training materials.

I have been using the solution for one year.

The tool is very stable.

All our implementations have 50 to 100 users.

We use the forums when we need support. The product has a big community.

We did not encounter any issues during the installation or while building the workflows. We implement the tool for our customers.

The most attractive feature of the product is that it is open source.

We are currently promoting the product to our customers. They are using Oracle BPEL, which is a licensed solution. They need an open-source tool. So, we are suggesting Camunda to them. Camunda is comparable with the licensed products. The competitors might provide more features compared to Camunda, but they are not that valuable.

I recommend using the product. Overall, I rate the product 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.

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 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.

We use the product to automate business processes for our clients.

Camunda's most valuable feature is its ability to integrate with different products.

They could provide more documentation regarding the integration of different programming languages. We encounter challenges finding recommendations or online documents while developing processes.

We have been using Camunda for more than five years.

I rate the platform's stability a nine out of ten.

The platform is more suitable for medium companies. Enterprises might need more automated and customizable solutions. I rate Camunda's scalability a nine out of ten.

We encounter challenges in finding examples for particular programming languages. Apart from that, the technical support documentation is good.

Positive

The setup process is easy. It was the primary reason to opt for Camunda.

The product is expensive for a small or medium-sized company. I rate the pricing a two or three out of ten.

Setting up or translating business processes using the Camunda platform is easy. It provides flexibility for integrating with different third-party systems. We have implemented the product to optimize internal business processes and improve API communication between different units.

I rate it an eight 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.

We use an open-source version of this product. In some cases we install on-premises, in some cases, we install on Dockers. How we install the product depends on the use cases and the needs of the projects that we engage in.  

One client may be in logistics. Another client may be involved with internal communication. Another one is in retail. Some will be in business project management. We have to treat each of these to fit their unique needs.  

I like the product since we are a Java-oriented company. Our solutions can be compact with Java. We found it quite useful because we can merge microservices together. It is a different kind of architecture but it is a flexible product that we can use to go live with solutions quickly.  

From my point of view, there is a lot that has room for improvement. But one option that they should focus on most is improving the basic parts of the BPM tools. One example is that they should offer some additional options in terms of employing connectors. We implemented most of our solutions in Java through delegation. We could have done a better job of that with connectors. So connectors are one of the cases where they might improve.  

Another point that I am thinking of that I can not do by myself is to improve the forms. Right now the forms are fairly simple. It would be nice to implement some kind of wizard, or advanced form, and be able to fill in data dynamically.  

A possible add-on is to have a mobile app. Specifically, it would be a tool used to prepare forms dynamically and to preview business projects. If you know what you need to do, you can actually do a lot with a product like that.  

From a security point of view, I think that some features can be added or enhanced. I see a lot of opportunities for interesting stuff that can be implemented like installation identity or places where token authorization can be used. More security measures can be added in order to offer options to protect the front line.  

One final feature that would be nice is the opportunity to operate an active database. I do not think that will happen soon. It is okay because we have very powerful database options right now.  

We have been using this solution for about one year.  

The stability of the product is quite good. You need to have the knowhow to work with it to optimize for best performance with the database and CPU and stuff. But it is a stable and reliable product.  

It is a scalable product. We do not have much on the cloud right now. It is less than 5 nodes. But we could expand that if we needed to.  

As I understand more of the benefits of using the product, I have more plans to increase usage. With any new customer that has a proper use case, Camunda will be my first choice. Even if it is just for the fact that we know we can deploy fast. We can start with a single instance and after that, we can scale without hesitating too much in the planning stages. It is very comfortable for the customer to see things happen quickly. From our experience, most new customers prefer to start small. Better to start fast and get them going and to build them a little at a time to more automated projects than to wait around with nothing seeming to happen.  

I have been around 10 years or more in this industry as a solution architect. With this product, we have the flexibility and speed to serve customers quickly and that is important.  

As for technical support, let's say we do not need it. We can cover any issues by ourselves with our team. We do not have any issues. If we do have an issue, we will compensate for it using Java.  

I prefer not to mention the other product by name because it seems like I would be saying it was not good enough and had to move on, but we did use a product as a solution before Camunda. Every product has its benefit in terms of what they deliver and we just decided that Camuda BPM fit our needs better than the other solution.  

For example, if we wanted to incorporate a solution in a situation where a client was using the Oracle family of products already, we might use Oracle SOA or Oracle OSB to stay within the family of products. Those choices would be a perfect fit.  

On the other hand, if your stack is Spring Boots and Java and open source, Camunda fits well. If you are stuck in an enterprise using Red Hat, there is Bonita and other Red Hat BPMs that may work best for you.  

What you use depends on a lot of things. It could change because of the recommendations of team members, it might depend on the current environment, it could be influenced by whether the company is new and needs to grow fast or if it is an established company with a predictable trajectory. At the end of the day what you use depends on the choice you make for what best fits your circumstance.  

The setup was straightforward. We need to have Java, and that is it. My team does the work on the deployments so I don't know exactly how long it takes anymore. But it is a simple concept that the more complicated the client's needs and use cases are, the longer it will take.  

We do deployments with just two people: one senior and one junior tech. But it depends on the complexity of the workflow. Sometimes we might bring an extra tech if the workflow is complex.  

Of course, we do not use an integrator, reseller, or consultant for the deployment because we are in that role. We know how to build it and we know how to run this kind of project. In the beginning, we did make a lot of mistakes, but at the end of the day, it works. Now when we have a new customer, we know what to do.  

We are using the open-source version so it is without cost.  

My advice about Camunda is I recommend this product when it fits your needs. It is that simple.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine because it fits my demands. Of course, there is always room for improvement in the interface, or performance, and stuff like that.  

I hope that people will work on Camunda and within the next releases we will have more connectors, we will have a much more powerful interface, and maybe we can have a mobile app as well.  

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.