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 (18th), Release Automation (11th), Configuration Management (18th)
 

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 most valuable feature is the ability to see which problems have been resolved from deployment."
"It gives us good feedback on visualizations and on how our processes have progressed."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"The main benefit is you can deploy everything with it."
"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"It provides a wonderful user interface which is easy to use."
"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."
"We have saved on our time costs and have seen more quality."
"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."
"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."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"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."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"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."
"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."
"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."
 

Cons

"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."
"The dashboard should allow you to see the current state of packages in each environment, not only on an individual application basis, but across the entire application platform."
"The stability of the solution can be improved."
"One of the biggest features I've been asked by my team to put in there is opening more scripting languages to be part of the platform. There is a little bit of a learning curve in learning how to code some of the workflows in Automic at this time. If widely used languages like Perl and Python were integrated, on top of what's already there, the proprietary language, it would make it easier to on-board new resources."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"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."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"There needs to be better error handling and error descriptions. It should be more clear what the errors are and what we can do to fix them."
"One thing that Chef needs to improve on is making it available in as many languages as possible."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Chef has a very steep learning curve, especially for beginners."
"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."
"Support and pricing for Chef could be improved."
"The agent on the server sometimes acts finicky."
 

Pricing and Cost Advice

"I can save time and money more quickly."
"Customers often complain about the price."
"We increased our quality and reduced our time costs."
"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."
"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."
"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."
"Pricing for Chef is high."
"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 able to save in development time, deployment time, and it makes it easier to manage the environments."
"Chef is priced based on the number of nodes."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
879,310 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Computer Software Company
14%
Financial Services Firm
13%
Retailer
9%
Manufacturing Company
6%
 

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: December 2025.
879,310 professionals have used our research since 2012.