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.
"Appian's most valuable features are the quick time it takes to develop for the market. It's easy and faster than other BPM solutions."
"Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes."
"Appian is easy to install and set up, and it does not come out with your audit. It has accessible process orchestration and process management. With Appian, the time to market is much faster."
"Appian also has very flexible local integration."
"The most valuable feature is business automation."
"Rapid development with low-code makes it easier to quickly get apps implemented and the time to break-even and ROI is much faster."
"Since implementing we have had a faster time to solution, with fewer resources needed."
"The product's most valuable feature is the low code aspect of development. We can develop an end-to-end VPN solution using a single platform."
"I have a lot of experience in this kind of industry, and Pega is one of the best solutions in terms of performance, capabilities, and the way we develop."
"The solution's case management is its most valuable aspect."
"The case management is great."
"The stability has been good. We haven't had any issues."
"It is a stable product."
"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."
"There are a lot of frameworks in the product. I use Pega PRPC the most."
"The solution offers excellent workflows."
"We'd like improved functionality for testing new devices."
"Native mobile capabilities or hybrid mobile app capabilities are very limited. Things like offline sync, offline storage, access to smartphone device features, etc. are not supported by the Appian platform yet."
"Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian."
"It would be useful if they could create an academy or forum in the future to help active users answer questions they have about the solution."
"There should be more flexibility for the developers to choose the look and feel of the UI. They should have a better ability to design their widgets and customize them with different colors, shapes, and sizes. That is a limitation that could be improved upon."
"One room for improvement is the ease of UI UX development, like in OutSystems and Mendix."
"The UI of Appian is more internal. Recently, there has been an addition of an external user portal for the customer-facing stuff. It's still coming out."
"Offline capabilities and responsive capabilities could be better. The mobility features of Appian platform are still evolving."
"To learn Pega, you need to be a partner. If someone just wants to learn Pega for the sake of learning, they won't be able to do so as they don't give access to that."
"The previous versions had good training documents but the updated versions need to improve the documentation."
"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."
"Reporting is not so clear and not so great. We really struggle to get the right reporting. When we need reporting based on the content of the tickets, we are not able to get it. The MIS reporting is not great. That's one of the reasons why we are switching to ServiceNow. Its compatibility with the higher versions of Internet Explorer should be improved. It really works well in Mozilla Firefox or any other browser, but when it comes to Microsoft Edge or Internet Explorer, sometimes, the layout gets disturbed. The positioning of the buttons changes, and there is some distortion in the layout. I am not sure whether it is our configuration problem or Pega's, but when it is working in Mozilla Firefox, it should also work in Microsoft Edge or Internet Explorer."
"The UI part needs improvement."
"They need to support the solution better, at this time the company does not have enough support."
"Business specific functionality is needed."
"In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals."
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.
