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 can scale by increasing the infrastructure which is currently running."
"It has an elaborated way to explore the IBM BPM processes."
"I rate the technical support a ten out of ten...The product's installation was easy."
"We like that it does not require a lot of hours to train our people."
"The installation was straightforward."
"We made the transformation to agile. Altogether with BPM, it is the total package."
"Technical support is good. They are very responsive. It is usually me who takes more time to get back to them than they take to get back to me, which is good."
"The most valuable features come in the bundle, the design process, creating services, creating BPDs, creating coaches, and UI/UX."
"It is a stable solution...It is a scalable solution."
"While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega."
"Decreased time for plane departures and landing, supported analytical insight for planning of three to six month forecasting, and helped with operational decision planning and support."
"Pega BPM's most valuable features are case management, integration, the convenience of using REST APIs, and the ease of changing things at the UI level."
"Fast prototyping."
"The most valuable feature is flexibility, as we can configure it to best suit our requirements."
"Case Management, as well as Workflow Automation, are Pega's most powerful capabilities."
"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."
"There are a few areas, like triggering mechanisms, externally exposed variables, and changing its values."
"It can definitely be improved in terms of performance and stability."
"The debugging needs improvement. There is some confusion surrounding the debugging."
"This is technology, and there's always room for improvement. It would be better to have a single solution. Trying to have an overview in terms of this solution brings together the concepts of BPM processes, customer journeys, and an automation part for KPIs. All of this working together and coming up with a single solution with privacy is more commercial than anything else."
"The front end is not customised for a good user experience."
"It might not be suitable for entry level clients because it comes with a huge number of modules for processing that at times might not be necessary for upcoming clients."
"Could increase vulnerability and security patches to make it more robust."
"The initial setup was complex."
"The licensing cost is very high."
"They need to support the solution better, at this time the company does not have enough support."
"It should have integration with non-relational databases. A lot of databases are non-relational, and as a company, we are planning to move to NoSQL or open-source databases. It would be good if we are able to install and use Pega on a NoSQL database. They can also try to tailor or organize the company a bit differently and go more towards the microservice concept. I would like Pega to develop machine learning and intelligent AI algorithms. They have a good foundation in terms of the model and the stuff that we are using for some customers, and it will be good to onboard as many machine learning algorithms as possible."
"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."
"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."
"This is an expensive solution."
"I believe that Pega's strategy when it comes to the UX part is not that great currently as compared to the other emerging BPM tools in the market."
"Pega's technical support could be better."
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 57 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.