We performed a comparison between IBM BPM and Pega BPM based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: Pega BPM finishes slightly ahead of IBM BPM. Pega BPM is low-code and very user-friendly. It provides next-generation processes that will convert problem statements into different diagrams and then implement the process, saving time and keeping organizations running efficiently. IBM BPM has a big learning curve and lacks many basic features that other BPM solutions provide.
"We are receiving good assistance from the technical support."
"IBM BPM should become cloud-native. It should also add a cloud deployment feature."
"The system integration layer is valuable because this enables an organization to create a single point where all the key organizational master data is held in different IT applications across different functions, that can be accessed and updated."
"Everything is coupled together and comes as one solution."
"We are implementing the tool to triple our monthly transaction volume."
"The most valuable features are the integration capabilities - BPM can connect with almost any legacy or advanced system."
"This is one of the best tools to support the business and the way we work, and the numerous processes we need to implement."
"With the Process Center, I can go to one place and view what all the environments are doing."
"The most valuable feature is the situational layer cake."
"The most valuable feature of Pega BPM is step-by-step voice guidance that converts your problem statement into different diagrams and then implements the process."
"The case management is great."
"Case Management, as well as Workflow Automation, are Pega's most powerful capabilities."
"Fast prototyping."
"The workflow designing and integration are the most valuable features. Also, the UI design was pretty easy."
"The solution is operating well overall."
"There are a lot of frameworks in the product. I use Pega PRPC the most."
"User Interface components could be further refined to enhance and extend customizations dictated by end clients."
"I have an interest around the robotic piece, and integrating that with the processes. I think that is certainly a good direction to be going."
"All our clients are changing to microservice and cloud service. However, BPM does not have a solution for microservice and cloud service."
"If you want to use IBM BPM, you will have to invest a lot of money for licenses and you need to learn that there are limitations in developing applications. You cannot create anything you want."
"It is a really powerful tool, but its entry price is so high, which makes it a very exclusive club for who gets to use it. The thing that seemed to be the most intolerable was that you could put lots and lots of users on it, and it worked fine, but if you put lots and lots of developers on it, it sure seemed to have challenges. The biggest challenge was the development because of the Eclipse tool. It just seemed like irrespective of the development team that you put together, whether it had 10 or 50 people, you would end up having to reboot the development server throughout the day when you concurrently had lots of people hammering on the system. The development server just got sluggish. This was true for every project I was on. Once you got more than about five people working on the system at the same time, it would just get slower and slower during development work, and the only way to fix it was to reboot the server. It became just like a routine. Sometimes, we would reboot at lunch or dinner time, which is silly. After the cloud instances started rolling out, I never saw that again. That was probably the one big advantage of the cloud version. Instead of using an independent Eclipse-based process development tool, we moved to web-based process and design. The web-based tool definitely had greater performance than the Eclipse-based tool. I never got onto another project after that with 50 people, so I don't know how the performance is when you get a large team on it, but it definitely seems that the cloud design tool was a massive improvement."
"We still have a couple of issues that we are working on right now with stability. Mostly on the configuration side of the tool, and it has been about a month that we have been working to stabilize the platform."
"I would like to see the solution be able to interact with other customer software solutions."
"The tool's workflow function is very strong."
"Pega currently is trying to add chatbots to their systems, and it's still quite immature. This part definitely needs to be improved."
"First-time customers will find its licensing tricky. The technical support team for this solution could be faster in resolving tickets."
"Compared to other BPM products, the interface is somewhat complex, so the usability could be improved."
"The workflow automation can be slow, so there is room for improvement there."
"It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there."
"The licensing cost is very high."
"Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now."
"If it could also be integrated with robotics, it could help with a lot of things, even if we don't have APIs, we could still talk to other applications. If it could invoke a bot, for example."
IBM BPM is ranked 5th in Business Process Management (BPM) with 105 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 58 reviews. IBM BPM is rated 7.8, while Pega BPM is rated 8.2. The top reviewer of IBM BPM writes "Offers good case management and its integration with process design but there's a learning curve". On the other hand, the top reviewer of Pega BPM writes "Provides built-in frameworks that can be reused and reduces time and cost". IBM BPM is most compared with Camunda, Appian, IBM Business Automation Workflow, Apache Airflow and ServiceNow Orchestration, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, Microsoft Power Apps and OutSystems. See our IBM BPM 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.