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

Automic Continuous Delivery Automation [EOL] vs Chef 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

Automic Continuous Delivery...
Average Rating
8.0
Number of Reviews
13
Ranking in other categories
No ranking in other categories
Chef
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
25
Ranking in other categories
Build Automation (12th), Release Automation (5th), Configuration Management (12th)
 

Featured Reviews

reviewer895359 - PeerSpot reviewer
Principal Project Engineer at a computer software company with 501-1,000 employees
Automatic installation for complex deployments and environments, with good workflow support
I like that really complex deployments are possible with it. It's very good. You have everything you need. You can design your workflows for your needs. You can do so much more, it's not just an automatic installation tool. It's a real deployment tool. I can do the complete deployment with everything that is possible.
Walter Ochieng Odhiambo - PeerSpot reviewer
Software Engineer and Tester at Safaricom
Automation has transformed daily infrastructure work and now frees teams to focus on new challenges
One thing that Chef needs to improve on is making it available in as many languages as possible. There should be a focus on how to make it understandable, not just to infrastructure people, but also to those working in monitoring. How can we ensure that it is part of their daily input? That is something that still has a small missing link. We are almost there, but it can help us achieve outcomes in the future in terms of objectives, not just workflows and visibility. How can we make real-time interactive dashboards more available? Look at what kind of tools can be integrated with them, not just working with the ones like Chef Kitchen and Habitat, but trying to make it even more flexible than what we have right now. On support, I think there should be more focus on how we can achieve AI automations in answering questions for beginners and addressing deep concerns without general manual management.

Quotes from Members

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

Pros

"The IT process automation is the most valuable aspect of this solution."
"The event monitor is very good. You can monitor when the file is created so you can pick up the file once it's done."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"Gives people insight into what's happening during the deployment."
"The main benefit is you can deploy everything with it."
"The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"I think on a day-to-day basis, it has increased the capacity to deploy. We don't have to wait for someone to do something."
"The product provides efficiency, in terms time, cost, and resources."
"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."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"Chef benefited my organization by definitely reducing time because we were provisioning tens of thousands of servers."
"The most valuable feature is automation."
"Chef offers valuable features in infrastructure as code, where it uses cookbooks and recipes written in Ruby language for detailed and flexible configuration of systems and applications."
"The scalability of the product is quite nice."
"All the use cases—configurations, deployment, compliance, and other common situations—demonstrate how helpful Chef is, and we found it very beneficial, which is why both my past organization and my current organization are using it."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
 

Cons

"There is an issue with the stability in the tool. The process of agent will stop, then the monitoring agent can't be recognized because the process is running, but you can talk with the system."
"The stability of the solution can be improved."
"I would like to see more support for WebSphere."
"At the moment, the version that we are using (version 12.0), the environment is complex with multiple installations. Therefore, the monitoring is not scalable, but this should be improved in 12.1 and 12.2."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"If you have a technical problem and need development of the tool, the support team is terrible, because they cannot help with the technical details."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"Since we are heading to IoT, this product should consider anything related to this."
"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."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"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."
"The agent on the server sometimes acts finicky."
"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."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
 

Pricing and Cost Advice

"Customers often complain about the price."
"If you have a fixed contract, it has limits to spreading out. If you have a flexible enterprise license contract, then you have a lot of scalability for this tool."
"We increased our quality and reduced our time costs."
"I can save time and money more quickly."
"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."
"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."
"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."
"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."
"Pricing for Chef is high."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
881,733 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
11%
Financial Services Firm
11%
Comms Service Provider
11%
Retailer
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise9
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise7
Large Enterprise19
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Chef?
My experience with pricing, setup cost, and licensing is that we sidestepped it by using Cinc because none of the functionality that is exclusive to the paid version was actually in use in the orga...
What needs improvement with Chef?
I would add that Ruby is a domain-specific language in the Chef dialect, which is a learning curve, but so is Terraform and so is Ansible. The only feedback would be if they could come up with an i...
What is your primary use case for Chef?
My main use case for Chef is configuration and deployments. We receive blank servers and use Chef to build predefined application or appliance servers. A quick specific example of how I use Chef to...
 

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform
No data available
 

Overview

 

Sample Customers

BET365, Charter Communications, TASC
Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation. Updated: January 2026.
881,733 professionals have used our research since 2012.