Try our new research platform with insights from 80,000+ expert users

Chef vs CircleCI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

Chef
Ranking in Build Automation
20th
Average Rating
8.0
Reviews Sentiment
7.5
Number of Reviews
19
Ranking in other categories
Release Automation (11th), Configuration Management (18th)
CircleCI
Ranking in Build Automation
14th
Average Rating
6.6
Reviews Sentiment
7.4
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Build Automation category, the mindshare of Chef is 0.5%, down from 0.7% compared to the previous year. The mindshare of CircleCI is 3.1%, down from 3.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

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.
reviewer0972521 - PeerSpot reviewer
Unhelpful support, unclear billing, and has offers ability to track usage
We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and environment. That costs us credits. Support engineers do not thoroughly read and understand issues when emailing them. They reply to me with a totally different context about the problem. Just yesterday, my web applications failed to 'yarn build' after I downgraded the resource class from extr-large to large. I contacted support and got no reply. Billing is a mess. There is duplicate information in the bill downloaded from their website and when I asked for a consolidated bill, they just answered that they didn't have it. There is no transparency on how many billed minutes and credits I spent each day both on their website and the monthly bill which makes it difficult to understand when the monthly bill contains many refill item charges. It is difficult or impossible to track usage and burndown of my subscription and to gain total outstanding refill amounts on a daily basis. Their website doesn't provide sufficient information on credits allocated/calculated for my extra-large resource class.

Quotes from Members

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

Pros

"It is a well thought out product which integrates well with what developers and customers are looking for."
"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."
"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."
"Chef recipes are easy to write and move across different servers and environments."
"The product is useful for automating processes."
"We have had less production issues since using Chef to automate our provisioning."
"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."
"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."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"It's a stable product."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The solution offers continuous integration and continuous delivery."
 

Cons

"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."
"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."
"In the future, Chef could develop a docker container or docker images."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"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."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"I would like to see more security features for Chef and more automation."
"The solution’s pricing could be better."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"There needs to be some improvement in the user interface of CircleCI."
"Billing is a mess."
 

Pricing and Cost Advice

"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."
"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 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."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Chef is priced based on the number of nodes."
"Pricing for Chef is high."
"The price of CircleCI could be less expensive."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
850,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
17%
University
6%
Healthcare Company
5%
Computer Software Company
20%
Financial Services Firm
13%
Manufacturing Company
9%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

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.
What do you like most about CircleCI?
The solution offers continuous integration and continuous delivery.
What is your experience regarding pricing and costs for CircleCI?
Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly billing statement is almost unreadable and their online dashboard doesn't provide ...
What needs improvement with CircleCI?
We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and environment. That costs us credits. Support engineers do not thoroughly read...
 

Comparisons

 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Shopify, Zenefits, Concur Technologies, CyberAgent
Find out what your peers are saying about Chef vs. CircleCI and other solutions. Updated: April 2025.
850,028 professionals have used our research since 2012.