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
7.5
Number of Reviews
19
Ranking in other categories
Build Automation (20th), Release Automation (11th), Configuration Management (18th)
 

Featured Reviews

MJ
The main benefit is you can deploy everything with it, but everybody has to need to use this tool in the organization
The main benefit is you can deploy everything with it, but everybody has to need to use this tool in the organization. If some organizations have their own tool, it is hard to make it clear that ARA would be better if everyone used it, because it provides a benefit when you can monitor all the users.
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.

Quotes from Members

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

Pros

"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 IT process automation is the most valuable aspect of this solution."
"You can design your workflows for your needs."
"The product provides efficiency, in terms time, cost, and resources."
"Deployment workflow (WF) can be designed this way, so that it is not necessary to provide all applications (systems) artifacts of which an application consists."
"It provides a wonderful user interface which is easy to use."
"We have saved on our time costs and have seen more quality."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"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."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"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 streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"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."
 

Cons

"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."
"key thing is support for cloud-based deployment. That is lacking."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"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."
"I would like to see more support for WebSphere."
"The stability of the solution can be improved."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"The agent on the server sometimes acts finicky."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"It is an old technology."
"If they can improve their software to support Docker containers, it would be for the best."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Since we are heading to IoT, this product should consider anything related to this."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"I can save time and money more quickly."
"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."
"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."
"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."
"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 using the free, open source version of the software, which we are happy with at this time."
"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."
"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."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
24%
Computer Software Company
18%
University
7%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
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.
 

Comparisons

No data available
 

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: March 2025.
845,040 professionals have used our research since 2012.