Camunda Reviews

Our deployment is not live yet. We are in the process of building it.

We make basic use of this solution. It is embedded within a code module that requires workflows. Essentially, Camunda is used to keep track of workflow activity. So, we're not making massive use of it. Rather, we're making use of it as an embedded microservice.

The most valuable features are that it's lightweight, can be embedded in existing Java code, and keeps track of the workflow state and the instances that we need.

The development team had a lot of issues at the start. Guaranteeing the execution times that it will work to is difficult. It's an embedded state machine, although it doesn't give you guarantees of when it will update the state. It can be quite difficult because you can get into timing issues, which is a real pain to sort out. We were able to resolve this by writing a wrapper around it. You have to be very certain that the transactional integrity is provided to the API user.

In the future, I would like to see better transactional integrity.

We have been building the Camunda Platform for approximately two and a half years.

We use it on a daily basis and apart from the timing issues, we haven't had any problems. We have been doing a lot of heavy testing because it's a big, National system.

Scalability-wise, it's fine. It sites within the Kubernetes nodes and scales with those.

I am the technical design authority that chose the product. A whole team of developers is working on it. As it's not live yet, the users are testers and developers, and there are approximately 40 of them.

When it goes live, there will be several thousand users, but that won't be until next year. In terms of expanding usage, potentially, we might because there are a lot of workflows that we could map out of the current one. The one that we are doing now is quite complex and we needed to embed the service. Potentially, it could go across the whole of this business area, which is something that we are thinking about.

We contacted technical support when we had the initial problems with timing, and they were below average. We ended up having to resolve the problem ourselves by writing a wrapper.

We did not use another solution prior to this one. It was all greenfield development.

Camunda is easy to set up. The initial setup was fine until we had an issue with execution times not being guaranteed. That took quite a number of weeks to resolve. 

We developed this platform on-premises and we deploy through AWS.

We brought some people in to assist with our implementation. They were supposed to be experts, but they weren't that great. They wanted us to make much wider use of it, and we only wanted to use it quite in a small way. So, we paid for a bit of consultancy, but then we didn't keep them on.

They were typical London consultants. At £1,800 (approximately $2,400) per day, they were ridiculously expensive.

It is only a small team that maintains it. Right now, we only have one person for that.

We are using the open-source version, free of charge. We didn't bother with the enterprise features. We did look at the enterprise features for the MI component but we ended up writing our own.

More than two years ago, we did a lot of work evaluating Camunda and other products. The two other solutions that we looked at were Pega and Appian.

Pega and Appian were much larger than Camunda, so they didn't meet the criteria of being lightweight. They had a lot of features, which is something that we took into consideration. However, if we were going to extend it to all of the other workflows then these other products were not quite right.

My advice for anybody who is implementing Camunda is to pay attention to transaction integrity. The biggest lesson that I have learned from using it is to do a little bit more architectural spike work before committing to all of the development.

Overall, it is a pretty good product but there is room for improvement.

I would rate this solution a seven out of ten.

I use it for designing my BPMN models for my company processes, but I don't use Camunda in-depth. 

So, the Camunda Modeler is a free version of Camunda. It's just one small part of it.

It has great value in terms of automation. We can automate processes. 

Another great thing is Camunda Cockpit. The interface is great. 

It would be great to have the ability to display more than one process collaboration in the same view. 

Ideally, we could collapse and expand each process within that view, clearly visualizing two different processes collaborating through messages.

I have been using it for a couple of years. I use version eight (v8).

It is a stable product. I would rate the stability a nine out of ten. 

It is a scalable product. I would rate the scalability a ten out of ten. 

I didn't need the techincal support. I haven't needed to for Modeler. It's simple. 

But if I were to use their automation engine, I'm sure I would need support.

Camunda was my first option.

I would rate my experience with the initial setup an eight out of ten, with ten being easy. It is pretty straightforward. 

We use Camunda on the cloud. Camunda provides the cloud.

It is east to use. 

We didn't have to deploy anything. We just opened an account, signed up, and that was it.

It's costly and not accessible for small enterprises or startups. It would be great if Camunda offered a tier plan for smaller companies. I wouldn't recommend the paid version for small projects.

Camunda automation engine is quite complex and technical. It requires technical knowledge, and I don't think anyone can start by themselves. 

However, Camunda Modeler is different and doesn't require technical knowledge.

Overall, I would rate the solution a nine out of ten.

As a service company, we implement this product for different customers. It's quite useful in automating processes, particularly with its orchestration capabilities.

The visibility – the diagrams you create – and then being able to automate based on them are valuable features. It's easy to explain and comprehend, and the integration aspects are valuable.

Typically, the user integrates with the business applications by calling jobs using REST APIs and similar methods. When the user needs connectors to databases for fetching data – that's where it's useful. Also, until the previous version, the user could embed Camunda within other applications. That was a good feature.

The user interface is good from the development point of view. But it's not a no-code, low-code kind of thing. From a developer's perspective, it works well.

So, it might not be easy for non-technical people to use. Camunda themselves never positioned it as a tool primarily for business users. Business users could use it for the designing perspective and then hand it over to the developers.

In the latest version, there are certain workflow nodes that are missing. Camunda should bring those back, or rather, develop them quickly. We've seen some of this on their roadmap, so they're working on it.  

I have been familiar with this product for five years. 

Whatever issues we've faced, we were able to resolve on our own, so it's been good enough for us.

The open-source aspect was important to us. So Camunda has been a good fit.

We work with both the free version and the latest paid version, as well as version 7.4.

The pricing has been flexible. Overall, it's been good.

If a company has workflow automation requirements or needs orchestration, it's quite useful.

Overall, it's good and solid. At least up to version seven, which we're heavily using. Version eight is progressing, and Camunda will continue to add the things we need. I would rate it at least a nine out of ten.

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.