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

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.
Arun S . - PeerSpot reviewer
Useful for large infrastructure, reliable, but steep learning cureve
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. The solution is good to manage multiple large infrastructures. We can have 10 to 10,000 users using this solution and it manages them well.

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 capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"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."
"I would say our headwind, or our time to market, is reduced considerably. We get more consistent results out of it, because you write one time and once it's automated you expect it to behave the same way every time. And it cut down a lot of re-work for us."
"You can design your workflows for your needs."
"The product provides efficiency, in terms time, cost, and resources."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"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 its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"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."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"The solution is easy to use and learn, and it easily automates all the code and infrastructure."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"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."
 

Cons

"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"key thing is support for cloud-based deployment. That is lacking."
"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."
"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."
"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."
"The agent on the server sometimes acts finicky."
"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."
"If they can improve their software to support Docker containers, it would be for the best."
"Since we are heading to IoT, this product should consider anything related to this."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
 

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."
"Chef is priced based on the number of nodes."
"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."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
24%
Computer Software Company
16%
Manufacturing Company
7%
University
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: February 2025.
838,713 professionals have used our research since 2012.