We performed a comparison between Camunda Platform and Pega BPM, based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Users show a greater preference for Camunda Platform, as Pega BPM is less stable, intuitive, and might have a less effective support team.
"It is simple to use. The user experience is very good."
"It has an open BPM"
"It allows me to present or to demonstrate the business process flow, visually, without having to resort to PowerPoint, Visio, or other products."
"The product has a good task management engine."
"The flexibility characteristic in a BPMS, through BPMN and DMN, is undoubtedly the most interesting feature for our business."
"I like everything about the entire BPM that comes with the BPM suite."
"For an internal project, this is a solution that you can install and have up and running quite quickly."
", Camunda can be a powerful tool to work with when used in an optimized and well-implemented manner."
"Scalable and stable BPM software with a powerful case management feature. It also has good workflow."
"The solution is operating well overall."
"While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega."
"The solution provides us with a very good dashboard."
"Application development is very rapid. A lot of code gets reused while building the applications, which is something we highly appreciate."
"There are a lot of frameworks in the product. I use Pega PRPC the most."
"In general, we use web services to integrate this solution with our other tools. It is the main approach we use with this solution and it integrates with all tools that we need. If you want to integrate with other solutions such ThreatFire or similar, it is possible as well."
"It is easy to use, easy to understand, easy to implement and easy to enhance and we can do it as a Cloud. Also it is very user friendly."
"If there were some industry templates it would have helped significantly, because it is similar to a process map for a domain. That is what we are currently creating, a domain-relevant process map."
"The only drawback is the time that it takes to have a complete set of workflows implemented on the Camunda platform."
"We're trying to put the people from the business to do it. We are using APIs, and we have open APIs to define our APIs and the request-response that each call requires and sends. So, to base the mapping on that, there was nothing to help. I know that with some tools, such as Oracle tools, you can see the input and expected output. With drag and drop, you can take one property from the left and drag it to the right, and it does all the mapping itself, but that's not the case with Camunda. So, for me, this is something that can be improved."
"The support definitely can be improved. Apart from that, the language should be extendable to other platforms. If I want to write, I'll run a different platform, like Python code on top of it, or COBOL code on top of it, and it should support those languages."
"The initial setup can be complex for business users."
"We have faced problems with the performance."
"Customization and tech stack could be up-to-date."
"The business model could be easier to understand."
"Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services."
"What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works."
"We have experienced a few technical challenges, particularly triggering the workflow through file drops and accessing files."
"The licensing cost is very high."
"The pricing model needs to be improved. Right now, it's too expensive."
"An area for improvement in Pega BPM is security. It's secure, but it still has a lot of vulnerabilities. Pega BPM is robust, but it still needs some improvement performance-wise."
"It is not fully compatible with all versions of Internet Explorer, so sometimes, it does not work."
"The way the IDE works with the chatbox and the taxonomy imports could be a little smoother."
Camunda is ranked 1st in Business Process Management (BPM) with 71 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 57 reviews. Camunda is rated 8.2, while Pega BPM is rated 8.2. The top reviewer of Camunda writes "Open-source, easy to define new processes, and easy to transition to new business process definitions". On the other hand, the top reviewer of Pega BPM writes "Provides built-in frameworks that can be reused and reduces time and cost". Camunda is most compared with Apache Airflow, Bizagi, IBM BPM, Appian and Bonita, whereas Pega BPM is most compared with ServiceNow, Appian, IBM BPM, Microsoft Power Apps and OutSystems. See our Camunda vs. Pega BPM report.
See our list of best Business Process Management (BPM) vendors and best Process Automation vendors.
We monitor all Business Process Management (BPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.