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

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

"It can support very complex environments and dependencies."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"The IT process automation is the most valuable aspect of this solution."
"The product provides efficiency, in terms time, cost, and resources."
"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"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."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"The scalability of the product is quite nice."
"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."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"The most valuable feature is automation."
"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."
"Chef recipes are easy to write and move across different servers and environments."
 

Cons

"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"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."
"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."
"The stability of the solution can be improved."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"key thing is support for cloud-based deployment. That is lacking."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"The solution could improve in managing role-based access. This would be helpful."
"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."
"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."
"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."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Support and pricing for Chef could be improved."
"Since we are heading to IoT, this product should consider anything related to this."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
 

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."
"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"Customers often complain about the price."
"We are using the free, open source version of the software, which we are happy with at this time."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Pricing for Chef is high."
"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."
"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."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
23%
Computer Software Company
16%
Manufacturing Company
7%
Retailer
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: January 2025.
831,265 professionals have used our research since 2012.