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

Chef vs VMware Tanzu Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

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
14th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
Release Automation (5th), Configuration Management (12th)
VMware Tanzu Platform
Ranking in Build Automation
17th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
23
Ranking in other categories
PaaS Clouds (13th), Cloud Management (33rd), Development Platforms (5th), Container Management (9th), Service Mesh (8th), Agile and DevOps Services (4th)
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of Chef is 2.2%, up from 0.6% compared to the previous year. The mindshare of VMware Tanzu Platform is 2.7%, up from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Chef2.2%
VMware Tanzu Platform2.7%
Other95.1%
Build Automation
 

Featured Reviews

G Srivastava - PeerSpot reviewer
Senior Cloud Engineer at a tech services company with 201-500 employees
Agent setup and complexity have limited automation benefits but have reduced manual patching work
There are other automation tools, configuration management tools in the market, which offer many good functionalities compared to Chef. For Chef, we need to install those agents, the Chef client, on all those nodes. That is another heinous task to perform on those nodes. Compared with other tools, they do not require any agent; they simply push configurations to all the clients. Chef needs to improve on this agent installation on all those nodes. I would say that the agent configuration is required, and we need to manage the workstation, the Chef server, and then the Chef client. These two or three things are very difficult. It is a time-taking task compared with other configuration management tools. They need to compete with other tools, such as Ansible or Terraform. They should work on their agent part. If they can remove the agent installation on the nodes and combine both the Chef server and workstation into one server, that will provide a significant benefit in cost for the clients. They should aim for an agentless architecture rather than an agent-based architecture, which will help other customers. That is a very difficult thing because I have stopped using Chef. If you have very good developers who are skilled in Ruby language and can write codes in the Chef recipe, then those developers should start using Chef.
ErmiasGirma - PeerSpot reviewer
Cloud Infrastructure Engineer at Safaricom Ethiopia plc
Has supported container-based deployments and improved infrastructure visibility through monitoring tools
Aria Operations, formerly known as VMware vRealize Operations, has been renamed to vROps. We are currently using this for monitoring purposes. For orchestration, we are using VCD to automate Telco Cloud. VCD is an automation tool, and we are also using VMware Tanzu Platform for the Kubernetes environment, alongside TKG, Tanzu Kubernetes Grid. These are also other solutions for the Tanzu Kubernetes environment. For Telco Cloud, we are using it to automate our company's operations, which is for a telecom company. We are familiar with these products, especially vCenter, ESXi, VCD, vCF, and vROps. It is very easy to integrate applications when we deploy vCenter and ESXi since we can enable vSphere with Tanzu feature. We can build namespaces and provide application developers the platform to deploy their applications on pods within containerization. We can easily manage, pull results, and create containers efficiently, making it a simple way to handle applications. We provide namespace labels for application developers, and we can manage their resources along with other aspects easily. Regarding security, we use many tools such as CDX and LDAP, AD for integrating our Kubernetes cluster with the developer teams. We can manage roles and permissions simply. It is very straightforward to integrate with EDX and other third-party tools, Active Directory, to the Kubernetes cluster, allowing easy access and management.

Quotes from Members

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

Pros

"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"Part of the reason why we have stuck with it is that it managed to effectively scale with us and stay stable at the same time."
"The scalability of the product is quite nice; we have deployed it across six to seven organizations."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"Chef has created much faster procedures for system setup and rollout of infrastructure in my organization, as well as for scaling and ensuring that all servers are configured identically."
"Chef has impacted my organization positively by ensuring that consistent deployments across production and test environments help more effective testing and faster deployments mean that more work can be done in one release cycle."
"We feel very good about these features."
"The most valuable feature of the solution is the ability to check the flow of all the different variants within our applications."
"It has provided us with one central point where we can easily track our product QA, and our project resources, across multiple projects and multiple business units."
"Tanzu is easy to upgrade and scale, whether we're talking about horizontal or vertical scaling. It is as smooth as possible without any downtime. The platform maintenance, upgrading, and operations part is very smooth."
"The valuable feature I have found to be the management of Kubernetes clusters in a private cloud or public clouds, such as Azure or Google Cloud Platform."
"The multi-tenancy with the VCD is great."
"The most popular feature of VMware Tanzu Mission Control is its graphical user interface for describing network policies on the Service Mesh, which is highly integrable with other tools commonly used in supply chains such as security."
"The most valuable feature of VMware Tanzu Mission Control is the management functionality of the cluster life cycle. Additionally, the solution integrates well with other vendors, such as Velero for backups and Sonobuoy for compliance. Additionally, it works well in multi-cluster environments."
 

Cons

"In the future, Chef could develop a docker container or docker images."
"The solution could improve in managing role-based access. This would be helpful."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"I think it can be costly considering the advantages and disadvantages of Chef."
"The agent on the server sometimes acts finicky."
"I chose a rating of seven because Chef is a great tool, but sometimes resource consumption is quite large, and it requires server-side setup, which is not required but should be considered if you are using server-client plus server."
"Support and pricing for Chef could be improved."
"It is an old technology."
"The biggest gap for me was just that the solution is relatively tied to Cloud Foundry. If you have anything you need to deploy outside of that, it becomes burdensome."
"The solution's initial setup process was complex...The solution could benefit from improved customization and visibility for its users."
"Tanzu could provide more granular control over whatever networking is being done on the containers."
"Another area of improvement is pricing."
"It is not easy to build a solution with containers. It has a graphical user interface, but you need to have a lot of knowledge of Linux and how to work in the command mode. Its support can also be improved. Currently, its biggest disadvantage is that it is a new product, and the clients prefer to go for a solution that has been in the market for a long time. There are not that many people who know this product."
"Cost is always a concern. Smaller companies might find the price a bigger issue."
"The price is very high compared to other Kubernetes environments because Kubernetes is open source."
"Tanzu provides better manageability as compared to OCP, but when it comes to tagging it with other products, it's a bit rigid. If I have to bring in any new product or something out of the box from a different vendor, working with Tanzu becomes a little difficult. For example, if I want to use the F5 services, I have to add one more layer of Avi, but I don't want to do that. If I have a list of the products that I want to use, such as for firewall services, with Tanzu, I will have to go through another layer, which creates complexity."
 

Pricing and Cost Advice

"Chef is priced based on the number of nodes."
"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."
"Pricing for Chef is high."
"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 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."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
"We are using the free, open source version of the software, which we are happy with at this time."
"The price of VMware Tanzu Mission Control is greater than that of Red Hat's competitor solution"
"It is not the most expensive option, and I believe the capabilities align well with the value it provides."
"Its pricing is very competitive. We get around 70% or 75%, sometimes even 80%, discount on the product. I would rate it a four out of five in terms of pricing."
"The license for VMware Tanzu Application Service is expensive. The license should be cheaper."
"The least expensive licensing cost for VMware is around $350 per core."
"The solution is only for large or medium size enterprises because it is expensive."
"The solution is bundled in with Cloud Foundry so the pricing is not independent."
"There are different licenses available. You have to upgrade your license if you want to scale the solution more."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise9
Large Enterprise20
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise3
Large Enterprise11
 

Questions from the Community

What is your experience regarding pricing and costs for Chef?
The licensing cost is zero for Chef if you are using the free version. They have developed other versions, such as SaaS-based and self-managed. For the SaaS-based version, it is $59 per node per ye...
What needs improvement with Chef?
There are other automation tools, configuration management tools in the market, which offer many good functionalities compared to Chef. For Chef, we need to install those agents, the Chef client, o...
What is your primary use case for Chef?
We used Chef, the automation tool, as an Infrastructure as Code tool for configuration deployment, such as deploying patches on numerous servers, first on the development box, then on QA, and then ...
Which is better - OpenShift Container Platform or VMware Tanzu Mission Control?
Red Hat Openshift is ideal for organizations using microservices and cloud environments. I like that the platform is auto-scalable, which saves overhead time for developers. I think Openshift can b...
What is your experience regarding pricing and costs for Concourse for VMware Tanzu?
The least expensive licensing cost for VMware is around $350 per core. Pricing varies based on commitment and volumetric, with discounts provided for long-term commitments. VMware sells directly or...
What needs improvement with Concourse for VMware Tanzu?
The price is very high compared to other Kubernetes environments because Kubernetes is open source. We can easily work with Docker, and when we compare it with OpenShift, the price is very high. We...
 

Also Known As

No data available
Tanzu Application Catalog, Application Platform, Application Service, Hub, Mission Control, Service Mesh, Build Service, Concourse for VMware Tanzu
 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Verizon, Cerner, Zipcar, Avarteq
Find out what your peers are saying about Chef vs. VMware Tanzu Platform and other solutions. Updated: August 2026.
908,800 professionals have used our research since 2012.