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

Chef vs Digital.ai Release comparison

 

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 Build Automation
20th
Ranking in Release Automation
11th
Average Rating
8.0
Reviews Sentiment
7.5
Number of Reviews
19
Ranking in other categories
Configuration Management (18th)
Digital.ai Release
Ranking in Build Automation
17th
Ranking in Release Automation
12th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
4
Ranking in other categories
DevSecOps (12th)
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of Chef is 0.5%, down from 0.6% compared to the previous year. The mindshare of Digital.ai Release is 0.8%, down from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Aaron  P - PeerSpot reviewer
Easy configuration management, optimization abilities, and complete infrastructure and application automation
In terms of improvement, Chef could get better by being more widely available, adapting to different needs, and providing better documentation. There is also an issue with shared resources like cookbooks lacking context, which could lead to problems when multiple companies use them. Chef should aim for wider availability, better flexibility, clearer documentation, and improved management of shared resources to prevent conflicts. Many companies are now moving to Ansible, so I would recommend better documentation, easier customer use, and simpler integration. I have concerns about the complexity of migrating to different servers and would prefer a simpler process.
Navanath Gajare - PeerSpot reviewer
Effectively automates deployments and applies one template across applications
Our company uses the solution to handle deployments for new releases. Whenever there is a new release, the solution creates a new provision template for deployment. We also orchestrate and manage all users. We integrate with other tools like GitHub, Jenkins, or Digital.ai Deploy to manage…

Quotes from Members

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

Pros

"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."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"The most valuable feature is automation."
"Manual deployments came to a halt completely. Server provisioning became lightning fast. Chef-docker enabled us to have fewer sets of source code for different purposes. Configuration management was a breeze and all the servers were as good as immutable servers."
"Deployment has become quick and orchestration is now easy."
"We have had less production issues since using Chef to automate our provisioning."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The most valuable feature of Digital.ai Release is its ability to communicate with various deployment systems, such as XLD and batch deployments, as well as integrate with tools, such as Flyway and Bamboo. We use Bamboo as our build orchestrator, and Digital.ai Release also integrates with Jira, another Atlassian solution. These capabilities make it a powerful tool for managing workflow, test automation, and other processes."
"The time is also reduced because the manual work has tremendously decreased. We just have to click one button, and it will create everything for us."
"The solution can apply one template across multiple applications."
"The orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that."
 

Cons

"It is an old technology."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"In the future, Chef could develop a docker container or docker images."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"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."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"The agent on the server sometimes acts finicky."
"The solution could improve in managing role-based access. This would be helpful."
"Digital.ai Release could improve by having a better plugin that works with Guardian that we use for mainframe migrations. If there could be an interface or plugin for Guardian that would be beneficial."
"The solution is a little bit expensive."
"Currently, we put artifact details manually. What we could improve, in our case, is the deployment instruction base. Developers input all the information, including which artifact and where it needs to be deployed. What Digital.ai could do is automatically go to the deployment instruction page, take those artifact details, and implement them."
"The backfill could be improved, we could automate that. Right now it's subjective — it's up to the lead developer's memory to remember to backfill."
 

Pricing and Cost Advice

"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."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Pricing for Chef is high."
"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."
"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 using the free, open source version of the software, which we are happy with at this time."
"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."
"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."
"Overall, the price is just too high; especially considering we're in the middle of a pandemic."
"The solution's license includes all features."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
18%
University
7%
Healthcare Company
6%
Educational Organization
52%
Financial Services Firm
22%
Computer Software Company
9%
Healthcare Company
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

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.
What do you like most about Digital.ai Release ?
The time is also reduced because the manual work has tremendously decreased. We just have to click one button, and it will create everything for us.
What needs improvement with Digital.ai Release ?
There are many areas of improvement. Currently, we put artifact details manually. What we could improve, in our case, is the deployment instruction base. Developers input all the information, inclu...
What is your primary use case for Digital.ai Release ?
It helps with creating documentation, release processes, deploying to lower environments, scheduling meetings, and sending emails to stakeholders. The goal is to reduce manual work and save time.
 

Comparisons

 

Also Known As

No data available
XL Release, XebiaLabs XL Release
 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
3M, GE, John Deere, Deutsche Telekom, Cable & Wireless, Xerox, and Société Générale, Liberty Mutual, EA, Rabobank
Find out what your peers are saying about Chef vs. Digital.ai Release and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.