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.
"It's a stable product."
"The most valuable feature is business automation."
"The most valuable features are the low coding and low code data."
"Appian also has very flexible local integration."
"The initial setup is easy."
"The setup is easy."
"With low-code, we don't need a lot of coding, and then from the plumbing perspective, there is a complete CI/CD pipeline that exists within Appian that can be leveraged for open deployment."
"Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes."
"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."
"The most valuable feature of Pega BPMI would be the academy courses, specifically the Product Development Network (PDN). Additionally, our organization has a dedicated Customer Engagement Team that we work closely with to achieve our goals."
"The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform."
"The most valuable features of Pega BPM are low code, no code, functionality, and easy development."
"The solution has very helpful technical support."
"The case management functionality of this solution has been most valuable."
"The solution's most valuable feature is its quick setup. Nowhere else you can create a good-looking application this quick. It's a fairly robust system."
"The most valuable feature is the situational layer cake."
"Authoring tool is slow to use resulted in limitations on how quickly solutions can be built."
"Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash."
"It would be nice if you could create your own customized apps when the business needed them."
"My only request is that they decrease the license costs."
"There are four areas I believe Appian could improve in. The first is a seamless contact center integration. Appian does not have a contact center feature. The second is advanced features in RPA. The third would be chatbot and email bot integration—while Appian comes with chatbot and email bot, it's not as mature as it should be, compared to the competition. The fourth area would be next best action, since there is not much of this sort of feature in Appian. These are all features which competitors' products have, and in a mature manner, whereas Appian lacks on these four areas. I see customers who are moving from Appian to Pega because these features are not in Appian."
"If we could calculate the amount of data that will be realized, it would help us a lot."
"There are some restrictions with respect to using external components within Appian. So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on."
"The graphical user interface could be easier to use. It should be simplified."
"Pega should work on redefining their model and creating a demand for their skills."
"There is a scarcity of resources who have worked with this solution before."
"Its implementation in the public sector was a bit complex."
"One of the areas of this solution that could be improved would be to advance the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM."
"I believe they simplify the application development. It is still complex. The learning is not easy, it takes time compared to other products on the market."
"The pricing model needs to be improved. Right now, it's too expensive."
"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."
"It needs more integration with other platforms."
Appian is ranked 4th in Business Process Management (BPM) with 58 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 56 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.