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

Chef vs Tekton comparison

 

Comparison Buyer's Guide

Executive Summary

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

Chef
Ranking in Build Automation
17th
Average Rating
8.0
Reviews Sentiment
7.5
Number of Reviews
19
Ranking in other categories
Release Automation (6th), Configuration Management (17th)
Tekton
Ranking in Build Automation
2nd
Average Rating
7.6
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Build Automation category, the mindshare of Chef is 0.4%, down from 0.6% compared to the previous year. The mindshare of Tekton is 12.1%, up from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Arun S . - PeerSpot reviewer
Useful for large infrastructure, reliable, but steep learning cureve
Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed. The solution is good to manage multiple large infrastructures. We can have 10 to 10,000 users using this solution and it manages them well.
AjayKrishna - PeerSpot reviewer
If you're dealing with many applications and need a reliable, scalable, and efficient system, I'd recommend this solution
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. Another important aspect is the level of customization offered by Tekton. Each task in the CI pipeline can be customized independently, allowing developers to write code in various languages like shell scripting, Java, or Python and incorporate them into the pipeline as needed. This level of abstraction and customization greatly benefits developers in creating efficient CI pipelines. Also, it can be challenging to understand the logs and troubleshoot issues without clear guidance. It's not always easy to reach technical support and get immediate answers. In my opinion, improvement in this area would be beneficial.

Quotes from Members

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

Pros

"The most valuable feature is the language that it uses: Ruby."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most valuable feature is automation."
"Deployment has become quick and orchestration is now easy."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"The scalability of the product is quite nice."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"I like the branching and visualization tools for the pipeline."
"Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed."
"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."
"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."
"One of the best things I appreciate is that Tekton runs on the Kubernetes platform. This is very useful when working on a project with other team members. For instance, suppose we have a very big project that requires building a large amount of source code or running many unit tests. During the build and unit test phases, Tekton on Kubernetes allows us to have a scalable machine to handle these tasks. This scalability is the most useful aspect for me."
"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."
"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."
"The tool offers flexibility and compatibility."
 

Cons

"Since we are heading to IoT, this product should consider anything related to this."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"The agent on the server sometimes acts finicky."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Support and pricing for Chef could be improved."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"It is an old technology."
"If they can improve their software to support Docker containers, it would be for the best."
"RBAC is really needed for Tekton."
"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."
"Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline."
"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Chef is priced based on the number of nodes."
"I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
"The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
"We are using the free, open source version of the software, which we are happy with at this time."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"When we're rolling out a new server, we're not using the AWS Marketplace AMI, we're using our own AMI, but we are paying them a licensing fee."
"The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it."
"Pricing for Chef is high."
"The product is free and open-source."
"Tekton is an open-source tool."
"The product is free of cost."
"It is entirely open source and free of charge."
"The solution is open-source."
"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.
831,071 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
16%
Manufacturing Company
7%
Retailer
6%
Financial Services Firm
23%
Manufacturing Company
15%
Computer Software Company
13%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Chef?
Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
What needs improvement with Chef?
Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
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 do you like most about Tekton?
Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively.
What needs improvement with Tekton?
Regarding areas for improvement in Tekton, I have not encountered significant issues. It works well for our use case. However, incorporating AI could be a potential enhancement in the future.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about Chef vs. Tekton and other solutions. Updated: January 2025.
831,071 professionals have used our research since 2012.