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 reduces development time in half making us more efficient."
"The tool is very flexible."
"Since implementing we have had a faster time to solution, with fewer resources needed."
"Another advantage of this tool is its reports and records. You can maintain dashboards, layouts. If you with a Java solution, it takes six months time. If you use this tool, you can finish in one or one and a half months' time."
"Appian is a very low code platform. It's very easy to learn and use."
"Appian also has very flexible local integration."
"The product has a very good mobile app."
"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."
"When our clients automate the KYC and onboarding processes, they can reduce their manual force and then deploy them in much better tasks rather than the mundane activities of selecting forms and gathering information."
"The most valuable features of the solution are case management, routing, and low-code environment."
"Powerful, full-featured business process management with excellent support"
"The initial setup is pretty straightforward."
"The most valuable features of Pega BPM are low code, no code, functionality, and easy development."
"The interface is quite simple and easy to use, even for beginners."
"It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs."
"The workflows are the most valuable features, particularly for us, because we were attempting to automate processes by utilizing workflows to provide a hands-off comparison between the bot and the human."
"What could be improved is more on the front end perspective, like the user interface and the mobile application aspect."
"Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash."
"My only request is that they decrease the license costs."
"Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian."
"The product’s pricing could be improved from the developers' perspective."
"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 solution could improve by being more responsive when dealing with large quantities of data. Additionally, they can make the decision or rules engine better. It cannot handle too many rules or too many decisions at once."
"Sometimes, clients expect us to implement ERP using Appian, which is very complicated. In such cases, I don't believe that Appian is a good tool for that."
"There are some UX shortcomings within the solution. However, it's my understanding that they have addressed them and in the next three months they will come out with a new updated version. They will be moving away from HTML5."
"The previous versions had good training documents but the updated versions need to improve the documentation."
"Pega should work on redefining their model and creating a demand for their skills."
"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."
"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."
"Its implementation in the public sector was a bit complex."
"UI needs improvement."
"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."
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.
