We performed a comparison between OutSystems and Pega BPM based on real PeerSpot user reviews.
Find out in this report how the two Rapid Application Development Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I like the mobile features the most, and there are also various features around the portal we created that I enjoy."
"We can do the validation before calling the API."
"The visual program of OutSystems is one of the major advantages of this solution."
"It is much easier to develop applications with the product’s IDE."
"It is very stable."
"Speed of delivery: We were able to reduce development time by 30%."
"OutSystems' best feature is that you can build tests with the flow, so even the tests are made in the PDD framework in a low-code way."
"The architecture of OutSystems is quite simple, and the features are similar to Mendix's. OutSystems has connectors for different enterprise apps and solid reporting capabilities. You can also integrate with any content management platform like SharePoint or Adobe Enterprise Manager, or something like that. You can also create and integrate workflows."
"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."
"Case Management, as well as Workflow Automation, are Pega's most powerful capabilities."
"Pricing is a little on the high side."
"It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs."
"The user interface and the ease of developing the workflow for an application are valuable features."
"The case management functionality of this solution has been most valuable."
"Can do a lot of things with minimum time and cost."
"The most valuable feature is the situational layer cake."
"Its ability to create and run automated tasks could be better."
"OutSystems could improve by being more like GitHub. It would be more helpful for us for division management and version control for our application."
"The dashboards in OutSystems could improve. There are a lot of tabs in the service center that can be confusing."
"One of the biggest areas for improvement is that every time an existing data element is modified, it creates a new data element. It doesn't really modify that particular data element. So, a user has to follow an extra step of removing the existing data element and bringing in the new and modified data element that is being added, which sort of goes into negative productivity."
"There is room for improvement in technical support."
"While I can't speak to the market impact, as a developer, I've seen significant reductions in development time across different versions of our applications. One area for improvement would be the UI controls in Service Studio. Sometimes, controls don't appear in the IDE, requiring us to check them in the web browser instead. Overall, our experience with OutSystems has been positive, though improvements in UI development would be welcomed."
"The tutorials for the solution should be updated."
"The documentation needs to be more robust."
"The workflow automation can be slow, so there is room for improvement there."
"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."
"Business specific functionality is needed."
"It is not fully compatible with all versions of Internet Explorer, so sometimes, it does not work."
"The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn."
"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."
"The initial setup takes time."
"The biggest thing I have seen is when going from one version to another and upgrading to the latest version, it takes a pretty long time for an organization to go through an upgrade process. I think that's an area where they can make it a little smoother."
OutSystems is ranked 3rd in Rapid Application Development Software with 46 reviews while Pega BPM is ranked 7th in Rapid Application Development Software with 55 reviews. OutSystems is rated 8.4, while Pega BPM is rated 8.2. The top reviewer of OutSystems writes "The visual program provides the advantage of only requiring one skill set for both the front and backend ". On the other hand, the top reviewer of Pega BPM writes "Low code with great APIs and good flexibility". OutSystems is most compared with Microsoft Power Apps, Appian, Mendix, ServiceNow and Salesforce Platform, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, Microsoft Power Apps and Salesforce Platform. See our OutSystems vs. Pega BPM report.
See our list of best Rapid Application Development Software vendors and best Low-Code Development Platforms vendors.
We monitor all Rapid Application Development Software 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.
