Try our new research platform with insights from 80,000+ expert users

AWS Amplify vs OutSystems comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Amplify
Average Rating
7.4
Reviews Sentiment
7.4
Number of Reviews
7
Ranking in other categories
Release Automation (6th)
OutSystems
Average Rating
8.4
Reviews Sentiment
6.8
Number of Reviews
55
Ranking in other categories
Mobile Development Platforms (1st), Rapid Application Development Software (4th), Low-Code Development Platforms (2nd), Business Orchestration and Automation Technologies (6th)
 

Featured Reviews

Shrihari Haridas - PeerSpot reviewer
DevOps Engineer at Burns & McDonnell
Amplify CLI acts as a single source of truth
The Amplify CLI acts as a single source of truth. You install the SDK from there, and using the Amplify API, you can talk to and manage AWS services directly from your code. You don't need to go to the GUI and click through menus - everything is manageable through the Amplify API at the code level. AWS Amplify integrates seamlessly with other services through AWS CloudFormation. Amplify first connects to the cloud for me. Whenever we write down the SDK, it's managed by CloudFormation. CloudFormation still happens on our cloud for your application because everything is updated with the help of cloud automation. Anything we need to change, we just add it to Amplify, and Amplify triggers the CloudFormation templates. Then it logs permission, updates the whole thing, or whatever you need it to ask.
MA
Software Developer Advisor at NTT DATA Services
OutSystems facilitates rapid application development and effective project management
What I find valuable about OutSystems is that it has a very good learning curve for developers. Within two weeks, we can gain knowledge in OutSystems, and it is very easy to learn. With my background being .NET, OutSystems is straightforward to learn, which is beneficial. Developing applications in OutSystems is good, and the flexibility allowed by OutSystems for application development is excellent compared to my experiences with other low-code technologies, where I've faced some challenges. The clean separation of concerns in the architecture provided by OutSystems is a key benefit compared to other platforms. OutSystems integrates with our existing tech infrastructure and provides flexible integration. If we want to integrate with third-party services, OutSystems has SOAP and RESTful services that allow us to consume external services, integrate with external databases such as SQL or Oracle, and includes integration studio for writing custom .NET code. After developing a .NET component, we can reference it in service studio, creating a reference file that makes integration easy. OutSystems officially supports various integrations and also includes an API discovery tool for consuming and exposing services, providing a lot of information about incoming URLs, similar to how we use Postman.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is user management, which includes authentication and authorization."
"The link with Figma is very nice. You can create your design in Figma, and then you can import it into AWS Amplify and use it. You can link it to your data source and data bindings."
"Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as needed. They don't necessarily need to involve the cloud team for basic management."
"One of the things I like best about AWS Amplify is its ease of use and strong integration with other AWS services, which enhances efficiency."
"The most valuable feature of AWS Amplify is authentication."
"The only tricky part I experienced was during the initial installation. I followed the documentation, but it wasn't working for some reason. I had to modify some local files in the CLI-generated folder to get it to work. I had to dig deep to find the issue, and it wasn't mentioned in the docs. So, some issues could be better highlighted in the AWS CLI documentation, which would help developers integrate other services more easily. AWS needs to improve its support."
"I didn't host my application but have used their backend as a service. It was a complete package with authentication, AWS AppSync, DynamoDB, and GraphQL. AWS Amplify is great if you don't know backend development and don't want to struggle with other backend services like MongoDB. You don't have to worry about what backend language or database to use. If you're confused, enroll with AWS Amplify. I also recommend Google Firebase for similar purposes."
"It is very stable."
"We can do the validation before calling the API."
"You can go huge - so it is definitely a scalable solution."
"I really like the one-click publish feature in OutSystems. In other development tools/languages, it's not as easy. I also like how easily I can manage all my projects in one place."
"The product is mostly stable."
"There is literally a ton of stuff it can do. It's very flexible."
"We can quickly develop an application using the tool."
"The solution helps to build mobile and web applications on SOAP and REST. You can integrate it with backend systems by submitting a code."
 

Cons

"I like AWS Amplify's documentation. It's comprehensive and includes many examples, so you don't need to ask for help much - you can refer to the docs. It's easy to use. I also appreciate the cost structure. You only pay for what you use. For example, if you use 100 GB, you're charged for that, but if you don't use it, you pay the maintenance cost."
"AWS can implement multiple web applications, and cross-platform applications, like iOS."
"AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options."
"I don't think there are major issues, but there is room for improvement in the UI/UX of AWS Amplify. The UI still needs to be more polished and user-friendly. It's currently a bit like drag-and-drop initially, but there should be more options to customize the UI based on our needs."
"Its capability to handle big projects needs to be improved. If you generate a user interface in Figma and import everything where all components are in one directory, currently, it is complicated. It isn't able to cope with that. For small projects, it is not an issue, but if you have big projects and you want to use AWS Amplify, then it gets more difficult. That is the most important point for me. It should be improved to cope better with bigger projects."
"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."
"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."
"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."
"It needs improvement in the AI capability."
"It's difficult to do the component version control. I would like them to add more studying materials."
"There is room for improvement in technical support."
"I like the OutSystems platform. I am working on integrating it with another platform using APIs, however, it has proven to be difficult. The main issue I am facing is obtaining authorization tokens as well as access and refresh tokens. It may be due to my lack of knowledge of APIs as it is new to me."
"The new version could be improved."
"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 prices should be lower. It is a little bit too high for a small market."
 

Pricing and Cost Advice

"When you're just starting, it is free. You have to pay only when you reach a certain amount of usage. I'm still at the early stage. So, I don't have to pay a lot. At the moment, it is not too expensive for me. It is worth the money."
"The pricing depends on what your use case is and whether you're an existing AWS customer. It's a pay-as-you-go model, so not expensive."
"OutSystems is an expensive product. My company has to make monthly payments towards the licensing costs attached to the solution."
"It is not an expensive product, especially if you have access to more features and deal with more projects."
"I believe they have two pricing options. One is approximately $4000 USD a year and the other is approximately $10,000 USD a year."
"It's not cheap. It's pretty expensive."
"You should contact OutSystems for more details but my opinion is that it is not for small business budgets."
"The solution is expensive. The platform is not suitable for all of my clients. I work with labor unions and other smaller organizations that would not be able to afford the platform's current pricing model. It would be beneficial if there were a scaled-down version or a tiered pricing option that would allow me to build an app or a web app that is more cost-effective for my clients. Currently, the platform's pricing is too high for many of my clients, who would not be able to afford something in the $50,000 to $100,000 range."
"OutSystems is expensive, and they changed the pricing model in the last couple of years. It's changing too much and it's becoming unstable. They are constantly shifting their prices based on users, courses, and other factors."
"It is still very expensive, so small companies can’t generally afford it... Still, the time saving on development and delivery is worth the value."
report
Use our free recommendation engine to learn which Mobile Development Platforms solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Construction Company
11%
Computer Software Company
9%
Comms Service Provider
7%
Computer Software Company
13%
Financial Services Firm
12%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise1
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise7
Large Enterprise31
 

Questions from the Community

What do you like most about AWS Amplify?
Typically, whenever we make changes and need to switch environments (e.g., dev to production), it's easy for our developers to maintain the state of each environment and make customizations as need...
What is your experience regarding pricing and costs for AWS Amplify?
I find the pricing of AWS Amplify reasonable, considering the value it provides, although opinions may vary based on usage.
What needs improvement with AWS Amplify?
AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options.
Which solution is better for developing non-ITSM applications: OutSystems or Service Now?
The short answer is that OutSystems is far better for 2 main reasons. Firstly, with Service Now you are locked into that platform for good. The business model is to lock in and then keep pumping th...
What industries do you think OutSystems is most useful for?
I cannot really name an industry in which OutSystems cannot be beneficial. Who does not want to make top-notch applications that work in no time? And OutsyStems does exactly that. The low-code plat...
How did you decide which OutSystems edition was the best one for you?
We started using OutSystems fairly recently, so we are still on the free version of it. My company is still testing how we like the platform, but so far, we have been satisfied with it and will li...
 

Comparisons

 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Randstad, Warner Brothers, HP, Intel, ING, Banco Popular, Thrivent Financial, Bacardi, Kent State University, Bacardi, FICO, ING, Vodafone, AbbVie, Estafeta, Siemens, Vopak
Find out what your peers are saying about OutSystems, Mendix, Salesforce and others in Mobile Development Platforms. Updated: January 2026.
881,082 professionals have used our research since 2012.