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

GoCD vs Tekton comparison

Why PeerSpot?
 

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 (18th), Release Automation (14th)
Tekton
Ranking in Build Automation
4th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the Build Automation category, the mindshare of GoCD is 2.9%, up from 1.7% compared to the previous year. The mindshare of Tekton is 4.0%, down from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Tekton4.0%
GoCD2.9%
Other93.1%
Build Automation
 

Featured Reviews

RajeshReddy - PeerSpot reviewer
Dev Ops Engineer at Infosys
The UI is colorful, but the user experience must be improved
We can see all the pipelines with a simple search. The UI is colorful. The user experience is very rich. The product is very easy to learn if we know a bit of the basics. If we have someone to show us how to use it, it is very easy.
reviewer2741265 - PeerSpot reviewer
Software engineer at a manufacturing company with 10,001+ employees
Benefit from a smooth learning curve and efficient adaptability
After seeing Jenkins and Tekton, I think Tekton is quite built on top of Kubernetes, so the learning curve is minimal. If you are working with Kubernetes, then OpenShift created Tekton on top of that, making it easily adaptable. Tekton is highly customizable. With Kubernetes, we can customize on our own and create custom builders. If teams have time and want to make enhancements, they can do it themselves. Whatever OpenShift is providing regarding Tekton is sufficient. It is easy to use because we don't need to write every pod step every time. A proper DevOps engineer can help once or twice, and development teams can easily adapt to that, make small shell script changes in the steps, understand the process, and work with it.

Quotes from Members

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

Pros

"The UI is colorful."
"After we switched to GO, each team can set-up their own delivery pipeline and run it themselves."
"It has a user-friendly interface, which for free and open-source tools, the UI is really amazing and simple."
"Permission separations mean that we can grant limited permissions for each team or team member."
"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."
"In terms of value added it has more than achieved everything we wanted from it and more."
"GoCD's open-source nature is valuable."
"Tekton is highly customizable, with Kubernetes, we can customize on our own and create custom builders."
"The ability to scale is valuable."
"You can isolate most Tekton assets in the Kubernetes namespace for your feature branch. This allows you to freely change Tekton assets and objects to adapt to your feature branch and requirements."
"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."
"Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments."
"The installation process is seamless, requiring fewer resources compared to Jenkins."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines."
 

Cons

"The tool must be more user-friendly."
"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."
"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 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."
"The documentation really should be improved by including real examples and more setup cases."
"User management, Documentation, Advanced GUI functionality."
"Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline."
"Tekton should include many features to integrate event-driven pipelines."
"The tool should improve in terms of output flexibility. It runs on a specific Kubernetes machine, and the persistent memory storage is on a single partition. Improving this aspect could make analyzing logs and toolchain outputs from external tools easier."
"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."
"Tekton could use better documentation."
"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."
"Improvement is needed in the build step."
"If you are a beginner, then accessing the flexibility part can be overwhelming. We think the learning curve of the tool is steep, especially for those who are not already familiar with Kubernetes."
 

Pricing and Cost Advice

"It's an open-source and free tool."
"This is an open-source solution and it is inexpensive."
"Tekton is an open-source tool."
"The tool is open-source and free to use."
"The product is free of cost."
"It is entirely open source and free of charge."
"The solution is open-source."
"The product is free and open-source."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
914,262 professionals have used our research since 2012.
 

Top Industries

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

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 Business11
Midsize Enterprise4
Large Enterprise23
 

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...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What needs improvement with Tekton?
I didn't get the intention of scalability. Scalability means based on the load, it will automatically gain resources and run. The question of pipeline scalability remains unclear. It's quite easy t...
What is your primary use case for Tekton?
We use Tekton for build and deployments. For LMP testing, we use the Tekton pipeline. We also use GitHub CI/CD. For infrastructure pipelines and Infrastructure as Code (IaC), we use Tekton. Previou...
 

Comparisons

 

Also Known As

Adaptive ALM, Thoughtworks Go
No data available
 

Overview

 

Sample Customers

Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about GoCD vs. Tekton and other solutions. Updated: September 2026.
914,262 professionals have used our research since 2012.