Automic Continuous Delivery Automation [EOL] vs Chef comparison

Broadcom and Progress Software are both solutions in the Release Automation category. Additionally, 86% of Broadcom users are willing to recommend the solution, compared to 95% of Progress Software users who would recommend it.

Automic Continuous Delivery...

Read 13 Automic Continuous Delivery Automation [EOL] reviews

86% willing to recommend

Chef

Read 19 Chef reviews

1,238 Views
272 Comparison Views

95% willing to recommend

Automic Continuous Delivery...

Chef

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Automic Continuous Delivery Automation [EOL] and Chef based on real PeerSpot user reviews.

Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation.

To learn more, read our detailed Release Automation Report (Updated: July 2025).

Buyer's Guide

Release Automation

July 2025

Download the complete report

Helped 865,384 peers since 2012

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

Ranking in other categories

No ranking in other categories

Chef

Average Rating

8.0

Reviews Sentiment

7.5

Number of Reviews

Ranking in other categories

Build Automation (20th), Release Automation (11th), Configuration Management (18th)

Featured Reviews

reviewer895359

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.

Read full review

Aaron P

DevOps Engineer at a manufacturing company with 1,001-5,000 employees

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.

Read full review

Quotes from Members

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

Pros

"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."

"You can design your workflows for your needs."

"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."

"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."

"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."

More Automic Continuous Delivery Automation [EOL] pros

"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."

"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."

"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."

"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."

"Deployment has become quick and orchestration is now easy."

"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."

"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."

More Chef pros

Cons

"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."

"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."

"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."

"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."

"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."

"GUI for mobile phones: Availability to approve and start deployment through mobile phones."

"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."

"key thing is support for cloud-based deployment. That is lacking."

More Automic Continuous Delivery Automation [EOL] cons

"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."

"Third-party innovations need improvement, and I would like to see more integration with other platforms."

"I would like to see more security features for Chef and more automation."

"The solution could improve in managing role-based access. This would be helpful."

"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."

"Support and pricing for Chef could be improved."

"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."

"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."

More Chef cons

Pricing and Cost Advice

"We increased our quality and reduced our time costs."

"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 can save time and money more quickly."

"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."

"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."

"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."

"We are using the free, open source version of the software, which we are happy with at this time."

"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 able to save in development time, deployment time, and it makes it easier to manage the environments."

More Chef pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Release Automation solutions are best for your needs.

See recommendations

865,384 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

No data available

Financial Services Firm

18%

Computer Software Company

15%

Retailer

University

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.

See all answers

What is your experience regarding pricing and costs for Chef?

Chef is priced based on the number of nodes.

See all answers

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.

See all answers

Comparisons

Red Hat Ansible Automation Platform vs Automic Continuous Delivery Automation [EOL]

Compared 34% of the time

AWS CodeStar vs Automic Continuous Delivery Automation [EOL]

Compared 26% of the time

More Automic Continuous Delivery Automation [EOL] Competitors

BigFix vs Chef

Compared 39% of the time

AWS CloudFormation vs Chef

Compared 10% of the time

AWS Systems Manager vs Chef

Compared 10% of the time

VMware Aria Automation vs Chef

Compared 8% of the time

Red Hat Ansible Automation Platform vs Chef

Compared 7% of the time

More Chef Competitors

Product Reports

Buyer's Guide

Automic Continuous Delivery Automation [EOL]

August 2025

Automic Continuous Delivery Automation [EOL] report

Download Automic Continuous Delivery Automation [EOL] product report

Buyer's Guide

Chef

August 2025

Download Chef product report

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform

No data available

Overview

Deliver apps at pace with agile development and let customer satisfaction soar.

Today, the pressure is on to transform how you deliver applications to market. Get release agility and speed without compromising quality and stability with CA Continuous Delivery Automation. Deliver apps reliably on demand from development through production—mobile to mainframe. Agilely scale as the cadence, volume and complexity of your apps grow. It’s DevOps-ready release management and automation for your dynamic enterprise.

Broadcom

Chef, is the leader in DevOps, driving collaboration through code to automate infrastructure, security, compliance and applications. Chef provides a single path to production making it faster and safer to add value to applications and meet the demands of the customer. Deployed broadly in production by the Global 5000 and used by more than half of the Fortune 500, Chef develops 100 percent of its software as open source under the Apache 2.0 license with no restrictions on its use. Chef Enterprise Automation Stack™, a commercial distribution, is developed solely from that open source code and unifies security, compliance, infrastructure and application automation with observability. Chef provides an unequaled developer experience for the Coded Enterprise by enabling users to express infrastructure, security policies and the application lifecycle as code, modernizing development, packaging and delivery of any application to any platform. For more information, visit http://chef.io and follow @chef.

Progress Software

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: July 2025.

DOWNLOAD NOW

865,384 professionals have used our research since 2012.

See our list of best Release Automation vendors.

We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.