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

AWS Amplify vs GitLab comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

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
Ranking in Release Automation
5th
Average Rating
7.4
Reviews Sentiment
7.4
Number of Reviews
7
Ranking in other categories
No ranking in other categories
GitLab
Ranking in Release Automation
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
82
Ranking in other categories
Application Security Tools (9th), Build Automation (1st), Static Application Security Testing (SAST) (7th), Rapid Application Development Software (12th), Software Composition Analysis (SCA) (5th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (3rd)
 

Mindshare comparison

As of May 2025, in the Release Automation category, the mindshare of AWS Amplify is 2.4%, down from 2.8% compared to the previous year. The mindshare of GitLab is 32.1%, down from 34.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation
 

Featured Reviews

Shrihari Haridas - PeerSpot reviewer
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.
Gaurav Chandel - PeerSpot reviewer
Boosted productivity with automated pipelines and seamless collaboration
There are some challenges with repository file management as GitLab may struggle to manage larger files. Improvements could be made regarding size management and file partitioning. Also, the UI has remained the same for a couple of years and could benefit from an update with AI features and better customization.

Quotes from Members

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

Pros

"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."
"The most valuable feature of AWS Amplify is authentication."
"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."
"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."
"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."
"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."
"As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
"The initial setup of GitLab is pretty simple, with no complications."
"We use GitLab in the new project for CI/CD, integration, and deployment."
"It is very flexible and easy because you can store data on cloud."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."
"The SaaS setup is impressive, and it has DAST solutioning."
 

Cons

"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."
"AWS Amplify can be improved in some areas, particularly in providing more robust documentation and easier customization options."
"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 could improve in the deployment. It would be beneficial to have more methods, such as automation."
"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."
"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."
"When deploying the solution on cloud and the CI/CD pipeline, we have to define the steps and it becomes confusing."
"The user interface could be more user-friendly. We do most of our operations through the website interface but it could be better."
"Technologies are always changing. Nowadays, new things like serverless computing and workload management have emerged. We have noticed a few gap items for faster service delivery. For example, we do user interface testing in the latest team and automate it using some tools. Recently, we integrated a tool with user interface testing, which can simulate a multi-user environment. So, we would like to see more integration with different platforms."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"GitLab could improve by having more plugins and better user-friendliness."
"The price of GitLab could improve, it is high."
"The pricing has been substantially increased, which is a major concern."
"I would like to see AI support in GitLab."
 

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."
"GitLab is cheap."
"In total, I believe we have more than 300 licenses spread over about 100 users, though I can't comment on the costs involved."
"The solution is based on a subscription model and is reasonably priced."
"It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."
"Regarding pricing, I would rate GitLab as moderately priced, maybe around a seven or eight out of ten. It could be more flexible for clients but generally offers good value."
"The solution's standard license is paid annually. They have changed the pricing model and it used to be better. There is a free version available."
"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."
"GitLab is highly priced for smaller teams, but it's okay if considering a user base of thousands."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
9%
Comms Service Provider
9%
Manufacturing Company
7%
Educational Organization
24%
Financial Services Firm
12%
Computer Software Company
12%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How to estimate whether using the AWS services is worthwhile for saving time and money for manufacturing at a retailer company?
Estimating the cost-effectiveness of using AWS services for manufacturing at a retailer company involves a comprehensive analysis. To make an informed decision, you should consider factors like the...
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 do you like most about GitLab?
I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently.
What is your experience regarding pricing and costs for GitLab?
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
What needs improvement with GitLab?
Certain features in Jira are not available in GitLab, such as the functionality to have weights at the milestone and epic levels. Hopefully, these features will be resolved with work items in GitLa...
 

Comparisons

 

Also Known As

No data available
Fuzzit
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
Find out what your peers are saying about AWS Amplify vs. GitLab and other solutions. Updated: April 2025.
849,686 professionals have used our research since 2012.