We performed a comparison between Appian 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: Appian comes out ahead in this comparison. Pega BPM users say it is not robust enough. In contrast, Appian is a high-performing, reliable product.
"In terms of interface, it's very good. In terms of infrastructure, it's amazing and already using multiple tools behind the scenes. It's a low-code platform, so it's very easy to implement."
"Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes."
"The initial setup was seamless. We didn't run into any hardships at all."
"There is no need to worry about vulnerabilities in the system, because Appian built a secure system."
"We appreciate the drag and drop functionality and the easy to access plug and play features."
"Even with an on-premise implementation, the scalability is still high, so it is easy to scale up."
"Recently, we added Appian Process Mining, Appian Portals, and now Appian RPA."
"Technical support is quite responsive."
"The initial setup is pretty straightforward."
"The solution is able to support the size and scale required."
"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."
"Overall, the ability to integrate with multiple applications and effective case management is the most valuable."
"The solution's case management is its most valuable aspect."
"While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega."
"Allowed us to develop and quickly release with confidence using cloud technologies."
"The most valuable features of Pega BPM are low code, no code, functionality, and easy development."
"Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian."
"The solution needs more features. For example, a way to connect to our viewing database, to record, and more interface and component design."
"Appian could be improved by making it a strict, no-code platform with free-built process packs."
"We'd like improved functionality for testing new devices."
"There could be a scope of enhancement for capturing the variety of use cases."
"Even though the company has made great improvements in online documentation, featuring rich material which includes case studies of real-life use cases, the material could definitely be better in quality and coverage of use cases."
"A point of improvement would be the SAIL forms. The built-in tool used to generate forms does not have debugging support (to view local variables as they change on live preview, and step-by-step valuation) which is a big drawback for form development. Moreover, the script language used to build SAIL forms does not support inheritance or lambda expressions (functions as arguments of other functions), which makes the code base more verbose."
"We have clients that want to use Office 365, Microsoft Analytics, and Power Apps. Appian just isn't the same as using something specifically designed to cater to the Microsoft Suite."
"The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn."
"The pricing model needs to be improved. Right now, it's too expensive."
"UI needs improvement."
"Currently, there isn't any feature I want to be added in the next release of Pega BPM because Pega always adds new features that my team welcomes and looks forward to learning. One area for improvement in the solution is the long learning curve, but after that, you'll find Pega BPM easy to use."
"This is a quite expensive product."
"Pega's technical support could be better."
"It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge."
"The previous versions had good training documents but the updated versions need to improve the documentation."
Appian is ranked 4th in Business Process Management (BPM) with 58 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 57 reviews. Appian is rated 8.4, while Pega BPM is rated 8.2. The top reviewer of Appian writes "Low resource consumption, easy setup, and stable". On the other hand, the top reviewer of Pega BPM writes "Low code with great APIs and good flexibility". Appian is most compared with Microsoft Power Apps, OutSystems, Camunda, ServiceNow and Mendix, whereas Pega BPM is most compared with ServiceNow, Camunda, Microsoft Power Apps, IBM BPM and OutSystems. See our Appian vs. Pega BPM report.
See our list of best Business Process Management (BPM) vendors, best Process Automation vendors, and best Rapid Application Development Software 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.