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

"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"We have saved on our time costs and have seen more quality."
"Gives people insight into what's happening during the 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."
"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."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"The most valuable feature is automation."
"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."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"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 important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
 

Cons

"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 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."
"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."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"It would be very beneficial for us to see integrations into cloud environments, especially into the Google Cloud environment because we are heading towards cloud."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"The agent on the server sometimes acts finicky."
"If they can improve their software to support Docker containers, it would be for the best."
"It is an old technology."
"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."
"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."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
24%
Computer Software Company
17%
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.
844,944 professionals have used our research since 2012.