No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Amplify vs GoCD 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
11th
Average Rating
7.6
Reviews Sentiment
7.2
Number of Reviews
8
Ranking in other categories
Mobile Development Platforms (17th)
GoCD
Ranking in Release Automation
14th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (18th), Build Automation (18th)
 

Mindshare comparison

As of August 2026, in the Release Automation category, the mindshare of AWS Amplify is 2.1%, down from 2.4% compared to the previous year. The mindshare of GoCD is 2.8%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation Mindshare Distribution
ProductMindshare (%)
AWS Amplify2.1%
GoCD2.8%
Other95.1%
Release Automation
 

Featured Reviews

YP
Adjunct Lecturer at a university with 10,001+ employees
Building full-stack apps has been streamlined and supports efficient authentication workflows
The best features AWS Amplify offers include AppSync, which is very good for authentication and the deployment version. It also allows me to easily use DynamoDB tables from AWS. The authentication and deployment features of AWS Amplify help me by ensuring that the authentication flow runs smoothly, as they are integrated and interconnected with GraphQL. I can delete or add users, create groups, reset passwords, and customize the login experience using the sign-in and sign-out features that come with GraphQL. AWS Amplify also has IO components, allowing me to configure files for AWS export to check if there are any builds or configurations missing. The ease of using AppSync and GraphQL is what I appreciate most about AWS Amplify. AWS Amplify is a strong tool for quickly building full-stack applications, which do require a solid understanding of how the underlying AWS services interact. AWS Amplify has positively impacted my work by making things easier, faster, and more efficient, particularly with its continuous integration feature and user management while monitoring app builds. The usage of AWS Amplify is part of my freelance work for different clients rather than directly within a single organization.
Nishant Narayan Singh - PeerSpot reviewer
DevOps Architect at a consultancy with 10,001+ employees
Simplifies the pipeline process, but the access control system needs enhancement
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified. The folder structure is another aspect that could be enhanced, as all jobs are displayed on a single page without the clear organization seen in Jenkins. Implementing a more structured approach to organizing jobs would improve user experience. AI could simplify job creation. For example, instead of manually editing pipelines as code, an AI tool could allow users to input variables and automatically generate the required jobs. It would help reduce human errors, such as issues that arise from incorrect edits in large code files.

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 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."
"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 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."
"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."
"Together with Ionic and Amplify, a nice use case is when you want to generate the backend very fast, and you want to have a desktop application and mobile application."
"The most valuable feature of AWS Amplify is authentication."
"Permission separations mean that we can grant limited permissions for each team or team member."
"After we switched to GO, each team can set-up their own delivery pipeline and run it themselves."
"GoCD's open-source nature is valuable."
"The UI is colorful."
"It has a user-friendly interface, which for free and open-source tools, the UI is really amazing and simple."
"In terms of value added it has more than achieved everything we wanted from it and more."
"The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."
 

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."
"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 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."
"There are certain things about AWS Amplify that keep changing."
"AWS can implement multiple web applications, and cross-platform applications, like iOS."
"The documentation needs improvement, as it is not user-friendly and can be challenging for novices."
"AWS Amplify could improve in the deployment. It would be beneficial to have more methods, such as automation."
"The tool must be more user-friendly."
"GO doesn't come with a lot of out of the box features like other tools, don't expect that you can get it to work by clicking the NEXT button."
"The documentation really should be improved by including real examples and more setup cases."
"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."
"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us."
"User management, Documentation, Advanced GUI functionality."
 

Pricing and Cost Advice

"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."
"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."
"This is an open-source solution and it is inexpensive."
"It's an open-source and free tool."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Construction Company
12%
Comms Service Provider
10%
Outsourcing Company
8%
Financial Services Firm
15%
Manufacturing Company
9%
Construction Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise1
Large Enterprise2
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise3
 

Questions from the Community

What is your experience regarding pricing and costs for AWS Amplify?
My experience with pricing for AWS Amplify has been generally positive, especially for small to mid-sized applications. Most of our clients required small to mid-sized applications. The pricing mod...
What needs improvement with AWS Amplify?
Currently, I do not believe that AWS Amplify is lacking in features, but one of the main limitations I feel is a lack of flexibility in CI/CD pipelines. The built-in pipeline works well for simple ...
What is your primary use case for AWS Amplify?
My primary use case for AWS Amplify is to build and host full-stack web applications where it handles front-end deployment, authentication via Cognito, and basic back-end integration.
What needs improvement with GoCD?
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be sim...
What is your primary use case for GoCD?
The solution helps us deploy microservices across multiple environments.
What advice do you have for others considering GoCD?
We integrate the solution with Git, where we store our code. We use Maven to build the code and tools like SonarQube and Checkmarx for code quality checks. We deploy our services in a Kubernetes-ba...
 

Comparisons

 

Also Known As

No data available
Adaptive ALM, Thoughtworks Go
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
Find out what your peers are saying about AWS Amplify vs. GoCD and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.