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

Chef vs VMware Tanzu Platform comparison

Why PeerSpot?
 

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 (8th), Configuration Management (8th)
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 (12th), Cloud Management (33rd), Development Platforms (5th), Container Management (9th), Service Mesh (8th), Agile and DevOps Services (4th)
 

Mindshare comparison

As of November 2026, in the Build Automation category, the mindshare of Chef is 2.1%, up from 1.0% compared to the previous year. The mindshare of VMware Tanzu Platform is 2.6%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Chef2.1%
VMware Tanzu Platform2.6%
Other95.3%
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

"It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"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."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"We have seen a lot of ROI, our customers really enjoy the tool, and we are able to save in development time and deployment time, making it easier to manage the environments."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"We have had less production issues since using Chef to automate our provisioning."
"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."
"Using Chef for automating infrastructure and applications in my organization has helped us reduce manual tasks by more than forty percent, thereby saving significant revenue for the client."
"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 Day 2 operations support is the most vital feature"
"The Tanzu platform is highly available, scalable, and flexible."
"Tazu is a developer-friendly and highly mature product."
"The most important thing about the solution is its flexibility."
"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 most valuable feature of the solution is the ability to check the flow of all the different variants within our applications."
"The initial setup is easy."
 

Cons

"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"The learning curve is steep due to Chef's Ruby-based DSL and the complex components of cookbooks and recipes, which can be challenging for new users, especially those without programming backgrounds."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"Support and pricing for Chef could be improved."
"It is an old technology."
"One thing that Chef needs to improve on is making it available in as many languages as possible."
"Since we are heading to IoT, this product should consider anything related to this."
"Another area of improvement is pricing."
"The solution is currently focused on VMware infrastructure and I would like to see more options made available."
"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."
"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 implementation is not easy, it is very complex and can take a day or two to complete."
"The price is very high compared to other Kubernetes environments because Kubernetes is open source."
"LYNX is a managed cluster solution that takes care of specific details within a cluster, such as sequences or services. I haven't seen this feature in Tanzu Mission Control."
"The network control and security policies must be improved."
 

Pricing and Cost Advice

"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."
"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."
"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."
"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."
"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."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Since we were at a large data center, the price might not have been a concern for us."
"The product is not expensive, but it is not cheap."
"The license for VMware Tanzu Application Service is expensive. The license should be cheaper."
"There are different licenses available. You have to upgrade your license if you want to scale the solution more."
"I would recommend that businesses look into the full price for their requirements. The price is high, but there are some open-source add-ons that can be used for customization while keeping costs down, although these might not be suitable for everyone."
"The solution is bundled in with Cloud Foundry so the pricing is not independent."
"The licensing cost is expensive."
"VMware Tanzu Mission Control is cheaper than Red Hat OpenShift."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
13%
Comms Service Provider
11%
Manufacturing Company
8%
Financial Services Firm
8%
Financial Services Firm
16%
Outsourcing Company
9%
Computer Software Company
8%
Manufacturing Company
7%
 

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: November 2026.
920,769 professionals have used our research since 2012.