Automic Continuous Delivery Automation [EOL] vs Chef comparison

Why PeerSpot?

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 93% 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 26 Chef reviews

5,607 Views
1,402 Comparison Views

93% 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: August 2026).

Buyer's Guide

Release Automation

August 2026

Download the complete report

Helped 913,924 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

7.8

Reviews Sentiment

6.6

Number of Reviews

Ranking in other categories

Build Automation (13th), Release Automation (6th), Configuration Management (12th)

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

G Srivastava

Senior Cloud Engineer at a tech services company with 201-500 employees

Agent setup and complexity have limited automation benefits but have reduced manual patching work

There are other automation tools, configuration management tools in the market, which offer many good functionalities compared to Chef. For Chef, we need to install those agents, the Chef client, on all those nodes. That is another heinous task to perform on those nodes. Compared with other tools, they do not require any agent; they simply push configurations to all the clients. Chef needs to improve on this agent installation on all those nodes. I would say that the agent configuration is required, and we need to manage the workstation, the Chef server, and then the Chef client. These two or three things are very difficult. It is a time-taking task compared with other configuration management tools. They need to compete with other tools, such as Ansible or Terraform. They should work on their agent part. If they can remove the agent installation on the nodes and combine both the Chef server and workstation into one server, that will provide a significant benefit in cost for the clients. They should aim for an agentless architecture rather than an agent-based architecture, which will help other customers. That is a very difficult thing because I have stopped using Chef. If you have very good developers who are skilled in Ruby language and can write codes in the Chef recipe, then those developers should start using Chef.

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

"You can design your workflows for your needs."

"Gives people insight into what's happening during the deployment."

"The agents are one of the solution's most valuable features, and I like agents for file transfers so you can transfer the files from agent to agent on the different platforms."

"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."

"It can support very complex environments and dependencies."

"You can automate everything you want."

"They have gained efficiency that they cannot achieve in any other way."

"In first pilot run, we achieved five times faster deployment without human work."

More Automic Continuous Delivery Automation [EOL] pros

"It is easy to manage on our production systems because there is an agent running on all the servers."

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

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

"Chef has impacted my organization positively by ensuring that consistent deployments across production and test environments help more effective testing and faster deployments mean that more work can be done in one release cycle."

"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."

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

"Using Chef for automating infrastructure and applications in my organization has helped us reduce manual tasks by more than forty percent, thereby saving significant revenue for the client."

"Chef benefited my organization by definitely reducing time because we were provisioning tens of thousands of servers."

More Chef pros

Cons

"The stability of the solution can be improved."

"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."

"The first time setup can be very complicated."

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

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

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

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

More Automic Continuous Delivery Automation [EOL] cons

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

"The learning curve is steep due to Chef's Ruby-based DSL and the complex components of cookbooks and recipes, which can be challenging for new users, especially those without programming backgrounds."

"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."

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

"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."

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

"If they can improve their software to support Docker containers, it would be for the best."

More Chef cons

Pricing and Cost Advice

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

"I can save time and money more quickly."

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

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

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

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

"Chef is priced based on the number of nodes."

"We are able to save in development time, deployment time, and it makes it easier to manage the environments."

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

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

913,924 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Outsourcing Company

16%

Construction Company

14%

Comms Service Provider

11%

Healthcare Company

Outsourcing Company

13%

Comms Service Provider

12%

Construction Company

Financial Services Firm

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	2
Midsize Enterprise	2
Large Enterprise	9

By reviewers
Company Size	Count
Small Business	3
Midsize Enterprise	9
Large Enterprise	20

Questions from the Community

Ask a question

Earn 20 points

What is your experience regarding pricing and costs for Chef?

The licensing cost is zero for Chef if you are using the free version. They have developed other versions, such as SaaS-based and self-managed. For the SaaS-based version, it is $59 per node per ye...

See all answers

What needs improvement with Chef?

See all answers

What is your primary use case for Chef?

We used Chef, the automation tool, as an Infrastructure as Code tool for configuration deployment, such as deploying patches on numerous servers, first on the development box, then on QA, and then ...

See all answers

Comparisons

UrbanCode Deploy vs Automic Continuous Delivery Automation [EOL]

Compared 21% of the time

Nolio Release Automation vs Automic Continuous Delivery Automation [EOL]

Compared 15% of the time

Plutora vs Automic Continuous Delivery Automation [EOL]

Compared 10% of the time

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

Compared 10% of the time

GitLab vs Automic Continuous Delivery Automation [EOL]

Compared 10% of the time

More Automic Continuous Delivery Automation [EOL] Competitors

Jenkins vs Chef

Compared 8% of the time

Red Hat Ansible Automation Platform vs Chef

Compared 7% of the time

AWS CloudFormation vs Chef

Compared 6% of the time

GitHub Actions vs Chef

Compared 6% of the time

Red Hat Satellite vs Chef

Compared 5% of the time

More Chef Competitors

Product Reports

Buyer's Guide

Automic Continuous Delivery Automation [EOL]

September 2026

Automic Continuous Delivery Automation [EOL] report

Download Automic Continuous Delivery Automation [EOL] product report

Buyer's Guide

Chef

September 2026

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 a powerful automation tool designed for efficient infrastructure management across varied environments. With its environment-as-code model, Chef provides predictability and reliability in deployments, enhancing security compliance and reducing manual intervention.

Chef focuses on automating deployments and configurations, ensuring server consistency, managing scalable environments, and orchestrating service deployments. Its versatile recipe-writing and Ruby-based flexibility cater to large-scale operational needs. Chef’s integration with services like AWS and Azure enhances its versatility, while its idempotent deployments assure reliability. Despite its prowess, Chef requires improvements in feature offerings, especially regarding container orchestration and cloud technologies.

What are Chef's Key Features?

Automation: Streamlines infrastructure management across diverse environments.
Environment-as-Code: Offers predictability and efficiency in management.
Idempotency: Ensures reliable deployments by maintaining the same outcome no matter how often applied.
Cloud Integration: Seamlessly integrates with AWS and Azure.
Security Compliance: Enhances security measures across infrastructures.
Ruby-Based Flexibility: Provides versatile recipe-writing and flexible configurations.
Scalability: Suitable for large-scale operational needs.

What Benefits Should Users Consider?

Consistency: Automated deployments reduce errors and manual efforts.
Efficiency: Decrease in manual intervention enhances team productivity.
Reliability: Idempotent deployments ensure consistent outcomes.
Scalability: Supports expanding infrastructures effectively.
Security: Maintains compliance with enhanced security features.

Chef is implemented across industries to automate application deployments, manage CI/CD pipelines, provision infrastructure, and maintain compliance. Its recipes and cookbooks streamline workflows in application deployment, system updates, and orchestration of services, reducing errors and manual intervention in a variety of sectors.

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: August 2026.

DOWNLOAD NOW

913,924 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.