Camunda Reviews

We have implemented it for an existing production application called Click End Connect, which is used for Orange Shops. Click End Connect allows users to view available mobile devices, select the shop that best suits their needs, and collect the chosen device within two hours without having to wait in the shop. The application handles stock verification and ticket collection processes seamlessly.

We have the Camunda Platform's cockpit, which is a key component of the Camunda Platform. By utilizing the Camunda cockpit, we can define stages and collect valuable data, including key performance indicators (KPIs). This allows us to identify areas of weakness that can be improved upon. 

The BPM (Business Process Management) cycle follows a pattern of collecting data, making improvements, executing processes, and then continuously refining them with the input of the entire team. The Camunda cockpit serves as a powerful tool provided within Camunda Platform. It acts as a dashboard, offering all the necessary information and key performance indicators required for effective monitoring and decision-making.

The most important thing about Camunda is that it's open source. It's a tool that is tuned to our pro profile concept, which suits our preferences and project needs. It's been really beneficial for us. 

The connectors available on Camunda Platform have responded to all our requirements, such as sending emails, and SMS, making web service calls, API integration, and handling show requests. 

Additionally, we were able to connect it with the Docker platform, allowing us to use containers that meet our performance needs. 

There is something that could be improved, particularly the availability of a drag-and-drop front-end tool for the workflow designer. When building interfaces, there are limited tools to work with, especially when dealing with different types of tasks, such as user tasks and system tasks. It would be beneficial to have something like the latest version of Ondula, which offers more flexibility and ease of use.

I've been using Camunda for five years now. We collaborated with a company called Schema in Paris, which provided us with support when needed and integrated closely with us. Camunda was the first product we put into production, and it has been quite successful.

We are currently using the seventh version of Camunda. We haven't upgraded to the eighth version yet. However, we are studying the possibility of migrating to the new version, especially the cloud-based variant with DB platform integration, among other features.

It is a stable solution if you have a properly configured server, regardless of the server type you are using (e.g., Apache, Nginx, or others), Camunda remains stable. 

As long as you have a good configuration, you shouldn't face any significant problems.

It is a scalable solution. We use four containers for our production environment. It is scalable and easy to maintain. 

We haven't encountered any problems with scalability during both the testing and deployment phases.

It is not overly complex to set up and implement if you are already a Java developer. For Java developers, it is quite straightforward and manageable. 

However, if you are, for example, a PHP developer or someone working with a different technology stack without Java skills, it may be a bit challenging to get started with Camunda. In such cases, I would recommend seeking assistance or guidance.

Camunda is a highly documented platform. I really appreciate that aspect. When I started working with Camunda, I made sure to read all the documentation for the APIs and other related information. It's a well-documented tool.

The deployment process utilizes DevOps practices. We make use of tools like Docker, which are suitable for various platforms and easy to use.

The deployment usually takes around five minutes. This includes steps such as packaging, configuring the environment, installing the application, and allowing the server to start. The entire procedure is completed within five minutes.

Moreover, it can be managed by a single engineer or developer who has experience with CI/CD, DevOps platforms, Docker, and related technologies. 

Although not a junior developer, one knowledgeable person can handle the deployment process. In our case, we had one individual who handled the deployment for us, and for subsequent applications, each of us was responsible for maintaining our own application.

There were some features that were only available in the paid version, not in the community version we used. For instance, we implemented an interface ourselves to view the history of our process instances because the historical data functionality was not accessible.

It is available, but it is part of the enterprise edition, which requires a paid license. We didn't have the option to purchase licenses as we migrated to open-source tools. 

So we had to customize our interfaces and tools using the Camunda API to replace the functionality found in the enterprise edition. That's how we managed it.

We have compared Camunda with the Bonita platform, and Camunda came out as the preferred choice in terms of features and functionality.

I recommend developing their expertise and skills with BPM. They should have a deep understanding of architecture. Starting with good releases is important because it allows users to become familiar with powerful tools and solutions. 

If you encounter a real problem, it is crucial to have a well-configured environment, whether it's a web server or any other production platform. Implementing BPM with good practices and optimization is key. 

Overall, Camunda can be a powerful tool to work with when used in an optimized and well-implemented manner.

Overall, I would rate Camunda Platform an eight 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.

We use Camunda to automate business processes.

The most valuable features are the workflow, the task list, and the modeler where we use VPN.

An improvement would be to support Angular 2 instead of AngularJS, which is quite old. I would also like Camunda to provide support for migrating to the new version so that my processes migrate without any problems.

I've been using Camunda for almost six months.

Stability-wise, Camunda is good, but sometimes task queries get very slow when we have a large number of tasks.

The scalability is quite good, we've had no challenges with it.

The initial setup is quite easy - I set it up in 30-35 hours.

The license is quite expensive, which is why we went with the community version.

We chose to use Camunda because it's open-source, easy to develop, and scalable, plus we were able to develop some of the enterprise features offered with the license in-house only. I would definitely recommend anyone thinking of implementing Camunda to try it out, just bear in mind that when the number of tasks increases, you need to write your own queries and that you need to keep the number of form variables low because performance decreases when it gets higher. I would rate Camunda Platform eight out of ten.

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. 

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

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.

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.