Camunda Reviews

The solution is used in my company, where we deal with insurance.

In our company, we use Camunda to automate our process to reduce the need for human tasks. In short, my company uses the product to reduce the need for manual work. The tool can help automate processes like insurance claims, onboarding, and other areas that are managed manually. Various processes in our company can be converted to automated ones with the help of Camunda.

The best feature related to the product is that it offers users a zero-code or no-code platform, so people can use the product without being developers or knowing Java or other microservices.

The support offered by the product is an area of concern where improvements are required.

Though Camunda offers one of the best support services in the market, I know that Camunda Platform 8.0 is still in the development phase. The tool can have more guidelines and best practices that can be made available over the internet to help people who are researching the solution as it is a new product in the market.

I have been using Camunda for a year. My company currently uses Camunda Platform 8.0. I am just a user of the product.

It is an absolutely stable solution.

It is a scalable solution.

Camunda is a new product in our company, but once we show the abilities of the tool and showcase it by going live with the solution, our company's entire client base will open up.

There are no admins required to take care of Camunda.

My company plans to use more of the product in the future.

Camunda is the first tool that we have used in our company. I believe that Infosys was using IBM, but they also moved to Camunda recently.

The product's initial setup phase was neither an easy nor a difficult process, though my company did receive support from Camunda, considering that I work in a big company with firewall products in place. There were some hurdles during the setup phase, making it a not-so-smooth process, but my company was able to deploy the product successfully in the environment.

The solution is deployed on an on-premises and on the cloud model.

Compared to some of the major players in the market, like IBM, Camunda is a cheaply priced product, making it one of its major USPs.

My company chose Camunda since it has two parts, one of which is Camunda Rule Engine, while the other one is Camunda BPMN. When it comes to Camunda Rule Engine, Camunda passes a set of rules through the tool itself, a process that doesn't happen in the system but happens externally through validation checks called the Camunda DMN Decision Engine. After a certain period, my company realized that Camunda's main feature lies in what Camunda BPMN provides to its users. After getting a demo of Camunda, my company was impressed with the solution, and we decided to try it.

Camunda's website is filled with a lot of knowledgeable stuff, so it is important to get in touch with a person from Camunda. By just going through the website Camunda, it is possible to strengthen your understanding of the fundamentals of the product. Camunda also provides free courses to those who want to learn more about the product.

I rate the overall tool a seven and a half out of ten.

My company uses Camunda Platform as a business process optimization or business process engineering tool.

The most valuable feature of the solution is that it is flexible. I want to see if the tool is good enough for my company to continue with its use or if there are some limitations. If, at our company, we are sure that it would take us to complete your business processes engineering exercise up to the level of enterprise architecture, then we would really be able to appreciate the tool. I am unsure of the product's capabilities because I am unfamiliar. I want to get someone experienced enough to suggest to me which is the best choice for a BPM tool.

Collaborations and process documentation in Camunda Platform are areas with shortcomings that need improvement. It would be appreciated if we were more flexible in managing the processes.

I am unsure if we can get a beta version of the tool with many features, including data modeling, apart from process modeling. If we get something that can be achieved with data modeling and collaboration features for any tasks, including the ones from outside, it would be much more appreciated.

We want a common platform for taking care of customs and domestic taxes since that could be a good thing for our business process across our entire company.

I have been using Camunda Platform for about three months. I am a user of the product.

It has been a stable solution so far since it meets our needs, including data modeling, which we need to do before we embark on analyzing and optimizing the business processes.

My company has 6,000 employees, out of which around 100 people use the product.

I contacted the solution's technical support since I wanted them to give me some facts regarding the points raised by a person from GBTEC, a German company, who claims that Camunda Platform can't fulfill some expectations since its imitations in terms of capabilities, especially collaboration features. I dropped an email to Camunda Platform so that someone from the support can let me know about the product's data modeling and whether it can go up to the enterprise architecture level or if something is missing in it, because of which we might have to get a beta or higher version.

The initial setup was very easy and flexible.

The solution is deployed on-premises.

Camunda Platform is an open-source product.

We, the employees, had suggested the company authorities opt for Camunda Platform. I was looking into certain facts from Camunda's support team so that I can suggest a good way to help my company design business processes. Our company has to look after customs and domestic taxes, and BPMN in Camunda Platform has been done using the custom function.

We intend to do a few things with the product, and I am unsure if it would raise or drop the product's rating in the future.

So far, considering the modeling purposes for which we used the tool in the last month, I rate the overall solution a nine out of ten.

I worked on a project in Pakistan. For this project, I replicated processes on Camunda, including BPDs (Business Process Diagrams) and activities. Currently, I am working on the forms aspect of the implementation.

I appreciate Camunda's strong SLA agreement, my current bank client required customized forms. Camunda forms are built on Angular, and I'm currently involved in a headless reporting project with Camunda.

Camunda's front end is built in Angular, while I'm integrating the Java backend services. I'll consume the Java services and handle integration with Angular on the front end.

When deploying Camunda, I prefer a headless approach. This means Camunda acts as middleware while the front end is built using a different technology. And back end will be from the different technology. 

 I've integrated a database with Camunda's process engine. This allows me to generate emails and update the database as needed.

It is very user-friendly compared to IBM BPM. It's much simpler because it doesn't have the process admin and process inspector roles and separate pages – it's more streamlined. That means even non-technical departments can use it. 

If we don't need complex, high-level workflows but just a small form-based process, Camunda can be used by any type of client – technical or non-technical.

I don't see a lot that needs improvement in the core functionality. With the on-premises version, the task list has issues, and user creation is not as straightforward as in IBM BPM with its Process Admin role. 

Camunda also lacks some of the initial documentation that helps with onboarding. I often rely on Udemy courses for help.

So, basically, on-premises user management needs improvement.

I'd recommend a feature like the Process Inspector that IBM BPM offers. This is where you can troubleshoot and manage running processes. It would be very helpful for non-technical users, as sometimes they need insight into where a process is stuck. 

Camunda Cockpit has similar functionality, but it's a bit more complex. I'm a technical person, so I understand it, but our clients are often from non-technical backgrounds. My clients are mostly common users from commerce backgrounds. 

So it would be better for Camunda to be able to easily view their processes and troubleshoot process instances.

The Process Portal in IBM BPM is basically a dashboard view. If Camunda could offer a similar dashboard for users, it would be a big benefit for their organizations.

I have been using it for six months. I use version eight. 

I would rate the stability a seven out of ten.

I would rate the scalability a five out of ten. Scalability would be improved with better documentation and resources. IBM BPM, for instance, offers extensive documentation and support teams for various issues. Camunda's documentation feels less comprehensive in comparison.

Additionally, it would be helpful to have more readily available use cases on the internet. This is important for doing POCs [Proofs of Concept] and showcasing how Camunda can be used. IBM BPM has many example use cases for systems like currency exchange or HR management. 

Camunda lacks this, often showing only very small processes that can be difficult for clients to envision within their own needs.

So, the lack of readily available use cases affects the ability of Camunda to adapt to your customer's needs.

I have experience with both IBM developer tools and Camunda. 

Due to cost considerations, we often recommend Camunda to smaller clients where IBM solutions might be too expensive in Pakistan, especially for small companies. 

I also do POCs [Proofs of Concept]. The demands I receive from customers are varied, but they want to move forward with the technology. If Camunda fulfills their requirements, they will definitely adopt it. Before Camunda, I also worked on Appian, but it wasn't as exciting as Camunda.

I'm doing a Master's in Data Science, so I know how crucial decision-making is for customers. Once my first POC is done, I'll definitely explore decision modeling. Camunda is still in its early stages in Pakistan.

There aren't as many resources in Pakistan as there should be.

I would rate my experience with the initial setup a nine out of ten, with ten being easy. Installing Camunda on your machine is incredibly easy. It's even easier than installing MS Office. I also installed IBM BPM on a virtual machine, and that took me one or two weeks to configure fully. Camunda is much simpler in comparison – the process is similar to installing MS Office.

Most customers I have are in the banking sector, so they prefer on-premises deployment. 

It takes around three days to deploy the solution because it includes things like permissions etc. Camunda is significantly quicker to deploy in comparison to IBM BPM, which takes around ten days. 

I'm a developer, not an administrator. So, I usually work with the administration team for the actual deployment. Typically, we need a few key files: one for the setup and one for the Camunda server itself. I'm familiar with the server file since I have Camunda installed for development on my own computer.

Compared to IBM BPM or Appian, Camunda's pricing is good.

Camunda is significantly cheaper than IBM BPM, especially considering the SLA agreement. Of the three products, it offers the best price-to-value ratio.

Overall, I would rate the solution an eight out of ten. 

I'd recommend it if you're currently paying a high annual fee for a solution like IBM BPM. Camunda is much more affordable while still offering a strong SLA agreement and security. 

It's worth trying – perhaps initially with a smaller process in your organization. You could even test it on a UAT environment before going live. I often recommend this approach to clients, as it's a good solution for many use cases.

We use the product to automate our workflows. It is used for task management.

Camunda is a good product. The product has a good task management engine. Camunda has had a good impact on our operational efficiency. The integrations are getting better. It has a lot of REST APIs. We can integrate the tool via REST. It is a good feature. It's much better than what it used to be.

Camunda is Java-based. It would be better if the tool were made less reliant on Java.

I have been using the solution for four to five years.

The solution is very stable. I rate the stability a nine out of ten.

The solution is very scalable. I rate the scalability an eight and a half out of ten. We have more than 100 users. I use the product twice a week.

We have used Flowable. We also used an IBM product, but it was not very good. We chose Camunda because it is more scalable. It has a smaller footprint. It is the most effective product.

The initial setup is easy. I rate the ease of setup a nine out of ten. The solution has multiple deployment options. It has its own cloud services. The deployment takes just a few hours.

We deploy the tool in-house. We've embedded it within our application. We need only one person for the deployment.

We use the free version.

The number of people required to maintain the tool depends on the application in which it is embedded. We might not need many people for maintenance. Our in-house team resolves all our issues, so we do not have to contact support. There is a lot of documentation available. They are very good. The solution has BPMN and DMN. DMN is very powerful when modeling business decisions. The rules engine is very good. I will recommend it for the rules engine. Overall, I rate the product 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 a team that analyzes our existing processes. We discuss the manual processes currently in place within our company. We work on defining and representing these processes through block diagrams. This helps us to automate them. The processes in which we use the solution include customer order processing and quotation requests. 

Using the BPMN helps us to have a common shared communication language when discussing processes.

The tool's most valuable feature is BPMN diagrams and the possibility to automate processes.

The Camunda Modeler installation poses a challenge, requiring local installation, which doesn't help collaboration like other online tools, for instance. Camunda needs to improve its user interface.

I have been working with the product for 4 months.

The tool is very stable since we run it on-premises. 

Camunda is scalable. At present, my company has three users. By next week, four more users will be added. Over a couple of weeks, a few more users will be added. 

I have not contacted the technical support yet. 

Camunda's deployment is easy. You need to click some buttons. 

I did the tool's deployment myself. 

We use Camunda's community edition, which is free. 

I rate the overall product a seven out of ten. 

We use it in the banking sector for a specific project. The platform aids in optimizing and automating business processes, enhancing operational efficiency, and ensuring seamless workflow management

Its flexibility stands out as the most valuable feature. I am content with its courses and the support team.

When addressing a complex and extensive process, the domain it belongs to, be it banking, healthcare, or HR, requires widespread access.

We have been working with it for more than five years.

I would rate its stability capabilities ten out of ten.

It offers excellent scalability. I would rate it ten out of ten. Our clientele comprises enterprises, medium-sized businesses, and small organizations.

Technical support from Comodo is accessible exclusively with the enterprise version, and it is highly commendable. They offer two support options, including the provision of an individual technical support manager. Our customers benefit from having personal vendors in support, capable of communicating in their native languages. For instance, if operating in Ukraine, clients can expect excellent service with a personal manager fluent in Ukrainian. I would rate it ten out of ten.

Positive

The initial setup was straightforward. I would rate it ten out of ten.

When it came to deployment, there were readily available options, along with clear instructions tailored for an open environment. We have it deployed on cloud as well as on-premise. The deployment timeframe varies, measured in hours or days, contingent upon specific customer requirements. Frequently, we initiate development, reproduction, and production environments. However, delays may arise as these environments can differ slightly, necessitating additional setup time.

ROI is influenced by the quality and usage. While the pricing structure is crucial, making an error in the planning can lead to substantial expenses. However, based on the feedback from our customers, they express satisfaction with Camunda. They assert that it provides extensive coverage and is more cost-effective compared to other business process systems.

While the license isn't budget-friendly, careful consideration and calculated planning for a significant number of licenses can make it more cost-effective. The pricing structure hinges on three crucial parameters: process instances, how frequently processes are initiated, and the number of users. These latter two factors exert a considerable influence on the overall cost. However, for those looking to explore it, trying the cloud version is a viable option. The cloud variant starts at $200 per month. I would rate it six out of ten.

Overall, I would rate it ten out of ten.

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.