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

GoCD vs Harness comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 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

GoCD
Ranking in Build Automation
18th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (17th), Release Automation (13th)
Harness
Ranking in Build Automation
8th
Average Rating
8.0
Reviews Sentiment
7.3
Number of Reviews
12
Ranking in other categories
Static Application Security Testing (SAST) (12th), Cloud Cost Management (8th), Feature Management (2nd)
 

Mindshare comparison

As of June 2026, in the Build Automation category, the mindshare of GoCD is 2.8%, up from 1.5% compared to the previous year. The mindshare of Harness is 4.8%, down from 7.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Harness4.8%
GoCD2.8%
Other92.4%
Build Automation
 

Featured Reviews

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.
MK
Technical Associate at ZS
Templatized pipelines have improved efficiency while limitations in code-based development remain
Harness UI can do a lot of good things. Harness's UI should not feel very complicated. At the current stage, it feels very commercialized and compared to other platforms such as Argo CD or Jenkins, which feel much more lively and much more simple. Infrastructure as code or pipeline as code is something that Harness severely lacks. There is not a lot of good support for pipeline as code, and I often find myself not using pipeline as code the way other platforms such as GitHub Actions or Jenkins integrate pipeline as code. Pipeline as code is definitely one of the disadvantages when it comes to Harness. Additionally, the entire platform feels very commercialized, which is something that a lot of developers, especially open-source enthusiasts, might not appreciate even within the organization. One of the very important key factors I observed was that there is no way to execute nested pipelines, which means that we cannot execute child pipelines within child pipelines and child pipelines even within those child pipelines. There is no way to execute nested pipeline execution, which may or may not be required based on the use case, but it is definitely one of those features that I wish the platform had.

Quotes from Members

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

Pros

"After we switched to GO, each team can set-up their own delivery pipeline and run it themselves."
"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."
"Permission separations mean that we can grant limited permissions for each team or team member."
"In terms of value added it has more than achieved everything we wanted from it and more."
"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."
"Everything in Harness is configured and runs smoothly."
"Harness positively impacts our organization by reducing deployment time, improving release confidence, and lowering operational overhead during deployment."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time and also reduced risks of failures or error rates by upwards of 70%."
"The time to resolve issues has been cut by about thirty to thirty-five percent, while the time to deploy has actually been cut in half."
"Approximately seventy-five percent time was reduced in case of deployment and around sixty to sixty-five percent time was reduced while troubleshooting it."
"Harness has positively impacted my organization as several teams have already migrated to it, and some are in the process of moving, reducing the dependency on one specific platform and making it faster with shortened build times and much faster deployments."
"Harness has impacted my organization positively; we use Harness in most of all deployments, so it is uniform."
 

Cons

"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."
"There are some UI components that can be improved."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"The initial setup can be complex and time-consuming, and the advanced features may require some learning time due to a steep learning curve."
"Harness can be improved by providing more clarity on the credits it issues for Harness Cloud, as it has a tiered pricing structure involving license and credit costs, which can get confusing."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"One improvement I see for Harness is simplifying the configuration process for smaller teams or startups, as the platform offers powerful features that new users may require some time to understand."
"Infrastructure as code or pipeline as code is something that Harness severely lacks."
 

Pricing and Cost Advice

"It's an open-source and free tool."
"This is an open-source solution and it is inexpensive."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
10%
Construction Company
8%
Computer Software Company
7%
Financial Services Firm
26%
Manufacturing Company
8%
Computer Software Company
7%
Outsourcing Company
5%
 

Company Size

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

Questions from the Community

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...
What needs improvement with Harness?
There are some UI components that can be improved. The needed UI improvements include more graphs, more history, the ability to create pipelines through the UI, and more interactions, with UI compo...
What is your primary use case for Harness?
My main use case for Harness is to create pipelines, deploy applications, and manage security pipelines. I use Harness to deploy applications to EC2 instances and Kubernetes instances, and I create...
What advice do you have for others considering Harness?
My advice for others looking into using Harness is to use AI capabilities, create pipelines, and then use it to deploy. Harness is a good tool. I would rate this review a nine out of ten.
 

Comparisons

 

Also Known As

Adaptive ALM, Thoughtworks Go
Armory
 

Overview

 

Sample Customers

Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about GoCD vs. Harness and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.