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

AWS CodeBuild vs Tekton 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

AWS CodeBuild
Ranking in Build Automation
9th
Average Rating
8.2
Reviews Sentiment
6.4
Number of Reviews
13
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
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 March 2026, in the Build Automation category, the mindshare of AWS CodeBuild is 2.4%, up from 1.2% compared to the previous year. The mindshare of Tekton is 6.6%, down from 12.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Tekton6.6%
AWS CodeBuild2.4%
Other91.0%
Build Automation
 

Featured Reviews

SomdipRoy - PeerSpot reviewer
Solution Architect at Skillnetinc
Has enabled automated deployments through continuous integration and supports multi-environment delivery
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as GitHub Actions, but it provides a very competitive price compared to GitHub Actions. GitHub Actions, if you want to use the YML CI/CD pipeline, gives a free tier of around three thousand hours per month. AWS CodeBuild is a little more expensive than that. However, if it supports the repository function as well along with it, then it will be a complete package. Everything would be in AWS, including the code versioning, code commit to the code infrastructure, to the code database, to the networking, and how the applications are accessed. Everything would be in one place, which would be very helpful. I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well. At the enterprise level, it charges maybe around nineteen dollars per user, though I do not remember exactly. In terms of AWS CodeBuild, I believe it is a bit expensive because it is providing only the deployment features. It is not providing the repository. In that comparison, I would say it is a little bit expensive.
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 integration is a good feature."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"AWS CodeBuild reduces wait time and optimizes workflows."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"AWS CodeBuild's support for a wide range of programming languages and build environments benefits development teams significantly in terms of productivity and ease of use."
"The initial setup of CodeBuild is easy."
"The integration with other AWS services has streamlined our workflow."
"The most important thing is that it's self-contained in an AWS account, and it's all linked to the customer's AWS account."
"Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins."
"Tekton is highly customizable, with Kubernetes, we can customize on our own and create custom builders."
"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."
"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."
"Tekton is an orchestrator. It provides seamless integration for our pipelines. It offers robust support for executing tasks within the pipeline, allowing us to set up and run pipelines quickly."
"Tekton provides a feature where you can schedule the job."
"It is an open-source tool, which makes it highly adaptable."
"Tekton is a cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."
 

Cons

"There is no persistent storage or preservation of workspace between the builds."
"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."
"They can further improve the integration of the Bitbucket for CodeBuild."
"For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"Multiple clients have faced issues with pricing. After migrating from Azure to EC2, they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible."
"I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"Tekton lacks integration capabilities compared to other CI/CD tools like Jenkins and Travis."
"The product's version update management process needs improvement."
"The product's UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement."
"Initially, working with YAML configuration can be challenging using the solution."
"Tekton lacks sufficient documentation"
"Some of the tool's cons include its minimalistic dashboard, which lacks detailed information and control compared to other tools like Jenkins or GitLab. Additionally, it's primarily used by Japanese companies."
"The product's documentation is an area of concern, making it an area where improvements are required."
"Tekton could improve by adding better documentation."
 

Pricing and Cost Advice

"We pay a monthly licensing fee."
"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."
"Despite the cost, it is worth the investment."
"The product is free of cost."
"The solution is open-source."
"The product is free and open-source."
"It is entirely open source and free of charge."
"Tekton is an open-source tool."
"The tool is open-source and free to use."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
884,797 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Computer Software Company
11%
Media Company
11%
Financial Services Firm
11%
Financial Services Firm
20%
Manufacturing Company
11%
Computer Software Company
8%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise5
Large Enterprise2
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise22
 

Questions from the Community

What do you like most about AWS CodeBuild?
It works seamlessly with AWS Elastic Container Registry (ECR).
What is your experience regarding pricing and costs for AWS CodeBuild?
The cost structure is affordable for most builds except macOS servers. Standard builds can utilize AWS EC2 servers for background operations. However, macOS or iOS builds require physical servers m...
What needs improvement with AWS CodeBuild?
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as G...
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

CodeBuild
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about AWS CodeBuild vs. Tekton and other solutions. Updated: March 2026.
884,797 professionals have used our research since 2012.