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

Chef vs Digital.ai Agility comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 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

Chef
Ranking in Release Automation
8th
Average Rating
7.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
Build Automation (13th), Configuration Management (11th)
Digital.ai Agility
Ranking in Release Automation
12th
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
8
Ranking in other categories
Application Lifecycle Management (ALM) Suites (14th), Enterprise Agile Planning Tools (6th), Value Stream Management Software (5th)
 

Mindshare comparison

As of October 2026, in the Release Automation category, the mindshare of Chef is 3.0%, up from 1.5% compared to the previous year. The mindshare of Digital.ai Agility is 2.3%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Release Automation Mindshare Distribution
ProductMindshare (%)
Chef3.0%
Digital.ai Agility2.3%
Other94.7%
Release 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.
JaiBharath Boithi - PeerSpot reviewer
Data Scientist at a tech vendor with 51-200 employees
Agile planning has improved daily coordination but reporting and dashboards still need more flexibility
I would like to see more advanced reporting and analytics customization. The existing dashboards are useful for tracking velocity, backlog, and delivery, but deeper real-time insights would improve decision-making. I would also like simpler integrations and more flexibility, especially across large teams and complex projects. Another improvement I would like is more flexible reporting and dashboard customization, especially for creating organization-specific metrics. More intuitive visualizations would also help. Digital.ai Agility can be improved mainly by making reporting and dashboard customization more flexible and intuitive. I would also like simpler integrations with third-party tools and easier configurations of automated workflows. Better dependency visualizations and real-time alerts for delivery risk would help large teams identify blockers earlier. The user interface could also be simplified to make it easier for new users. Overall, these improvements would make day-to-day planning, reporting, and cross-team coordination more efficient. There are a few areas where improvements are needed. I would like to see further improvements in user experience and navigation, especially making commonly used features easier to access for new users. More intuitive dashboard customization, better dependency visualization, and simpler third-party integrations would also help.

Quotes from Members

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

Pros

"The features are good in Chef, especially its compliance feature; it's very good and it's what I found most valuable in the tool."
"Chef recipes are easy to write and move across different servers and environments."
"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."
"The manual work has been reduced with the help of this automation, we only need two or three people to write those recipes and upload them on the Chef server, and once the configuration tool pulls those changes from the Chef server, it automatically deploys all those changes and has reduced our manpower and our costs."
"It has decreased a lot of man-hours that we were previously spending doing stuff which we now manage with Chef, decreased the time to fix production issues, and reduced the number of production issues since using Chef to automate our provisioning."
"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."
"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 valuable feature is the language that it uses: Ruby."
"The solution is excellent for collaboration; from the agility point of view, they have very good sprint functionality, allowing you to set up sprints effectively."
"For visualization capabilities, the automation capabilities make it possible to support the different personas. The features and capabilities are excellent and come with excellent support."
"The most valuable thing is kind of the whole package together."
"It can generate reports showing a burndown chart, burnup chart, and the planned vs actual velocity."
"I prefer Agility out of the three applications we work with because it has the most flexibility and can work at a higher level."
"Agility is highly flexible. It can do much more than what our client is doing with it. They use it in a defined way. Some at that company have a much broader knowledge of agile and SAFe, but they're given applications and a mandated way to work. We had to work within their parameters and provide an accurate transition so the data would be mapped and pushed through."
"You can use Digital.ai Agility for automating your tasks and creating your dashboard."
"VersionOne delivers a total ALM solution for whether you are operating a single team, like Scrum and Kanban for IT operations, or implementing an agile enterprise approach, like SAFe."
 

Cons

"However, if you are on-premise, it may not be the best solution."
"Since we are heading to IoT, this product should consider anything related to this."
"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."
"Other things would be the need to use Cinc if you want to use the open-source version because Progress Software's policy on copyright is confusing for new users and it puts a barrier in the way to adoption because many small, medium enterprises, startups, and non-profits who might want to use Chef would find the whole Cinc versus Chef situation confusing and the fact that there is not an easy path to install Chef and then go to a paid version without having to change from Cinc to Chef or Chef to Cinc."
"I would like to see more security features for Chef and more automation."
"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."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"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."
"The user interface could also be simplified to make it easier for new users."
"The machine learning features are a new capability but could be improved. This is being worked by Digital.ai currently. Multicolor simulation, specifically, could be improved."
"There is room for improvement in getting the analytics portion of the solution more integrated with the rest of it."
"In my work as a contractor, it's always frustrating when a client has multiple software applications that don't talk to each other and they all perform the same function. That presents a huge challenge between their IT groups."
"The response from Digital.ai Agility is a little bit slow and could be faster."
"It was not supporting some plugins. We wanted to migrate data that we were already using."
"The user interface can be improved by adding Save, Edit, Add, Cancel, and Return buttons to the popup windows that are displayed when you click on a child item."
"Improve how to create and track releases. Currently, I have to create child projects."
 

Pricing and Cost Advice

"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"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."
"We are using the free, open source version of the software, which we are happy with at this time."
"Chef is priced based on the number of nodes."
"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."
"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."
"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."
"You get what you pay for. Don't let your development teams dictate what the portfolio management team should use as the main tool."
"Comparing the pricing to other products, I think this solution is in the middle."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
13%
Comms Service Provider
11%
Manufacturing Company
8%
Construction Company
7%
Manufacturing Company
13%
Insurance Company
10%
Construction Company
9%
Outsourcing Company
9%
 

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 Business3
Large Enterprise5
 

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 ...
What needs improvement with Digital.ai Agility?
I would like to see more advanced reporting and analytics customization. The existing dashboards are useful for tracking velocity, backlog, and delivery, but deeper real-time insights would improve...
What is your primary use case for Digital.ai Agility?
I primarily use Digital.ai Agility for Agile project management, sprint planning, backlog management, and tracking team progress and deliveries. We use Digital.ai Agility for Agile project and port...
What advice do you have for others considering Digital.ai Agility?
I can advise others to use Digital.ai Agility for organizations. It is good for enterprise-level Agile planning across multiple teams and portfolios. Before implementing it, I would suggest startin...
 

Also Known As

No data available
VersionOne Lifecycle, VersionOne, CollabNet VersionOne, Digital.ai Continuum
 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Siemens Health Services (HS), Cerner Corporation, Aaron's, Federal Home Loan Bank of Atlanta, Kelley Blue Book, AOL, Axway, Tideworks, bwin Interactive Entertainment, AG, Intergraph, Eos Group, PeopleCube, Liquid Machines
Find out what your peers are saying about Chef vs. Digital.ai Agility and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.