StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Chef vs CircleCI

Chef vs CircleCI

OverviewDecisionsComparisonAlternatives

Overview

CircleCI
CircleCI
Stacks14.5K
Followers7.1K
Votes974
Chef
Chef
Stacks1.3K
Followers1.1K
Votes345

Chef vs CircleCI: What are the differences?

Chef: Build, destroy and rebuild servers on any public or private cloud. Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others; CircleCI: Automate your development process quickly, safely, and at scale. Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Chef can be classified as a tool in the "Server Configuration and Automation" category, while CircleCI is grouped under "Continuous Integration".

Some of the features offered by Chef are:

  • Access to 800+ Reusable Cookbooks
  • Integration with Leading Cloud Providers
  • Enterprise Platform Support including Windows and Solaris

On the other hand, CircleCI provides the following key features:

  • Language-Inclusive Support
  • Custom Environments
  • Flexible Resource Allocation

"Dynamic and idempotent server configuration" is the top reason why over 104 developers like Chef, while over 218 developers mention "Github integration" as the leading cause for choosing CircleCI.

Chef is an open source tool with 5.86K GitHub stars and 2.36K GitHub forks. Here's a link to Chef's open source repository on GitHub.

According to the StackShare community, CircleCI has a broader approval, being mentioned in 943 company stacks & 388 developers stacks; compared to Chef, which is listed in 360 company stacks and 80 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on CircleCI, Chef

Dustin
Dustin

Senior Developer at Elegant Themes

Apr 18, 2019

ReviewonCircleCICircleCI

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

607k views607k
Comments
Somnath
Somnath

Engineering Leader at Altimetrik Corp.

Jun 25, 2020

Needs adviceonCircleCICircleCIDrone.ioDrone.ioGitHub ActionsGitHub Actions

I am in the process of evaluating CircleCI, Drone.io, and GitHub Actions to cover my #CI/ #CD needs. I would appreciate your advice on comparative study w.r.t. attributes like language-Inclusive support, code-base integration, performance, cost, maintenance, support, ease of use, ability to deal with big projects, etc. based on actual industry experience.

Thanks in advance!

1.82M views1.82M
Comments
Felipe
Felipe

May 24, 2020

Needs advice

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

198k views198k
Comments

Detailed Comparison

CircleCI
CircleCI
Chef
Chef

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Language-Inclusive Support;Custom Environments;Flexible Resource Allocation;SSH Or Local Builds For Easy Debugging;Improved Caching;Unmatched Security;Parallelism;Insights
Access to 800+ Reusable Cookbooks;Integration with Leading Cloud Providers;Enterprise Platform Support including Windows and Solaris;Create, Bootstrap and Manage OpenStack Clouds;Easy Installation with 'one-click' Omnibus Installer;Automatic System Discovery with Ohai;Text-Based Search Capabilities;Multiple Environment Support;"Knife" Command Line Interface;"Dry Run" Mode for Testing Potential Changes;Manage 10,000+ Nodes on a Single Chef Server;Available as a Hosted Service;Centralized Activity and Resource Reporting;"Push" Command and Control Client Runs;Multi-Tenancy;Role-Based Access Control [RBAC];High Availability Installation Support and Verification;Centralized Authentication Using LDAP or Active Directory
Statistics
Stacks
14.5K
Stacks
1.3K
Followers
7.1K
Followers
1.1K
Votes
974
Votes
345
Pros & Cons
Pros
  • 226
    Github integration
  • 177
    Easy setup
  • 153
    Fast builds
  • 94
    Competitively priced
  • 74
    Slack integration
Cons
  • 12
    Unstable
  • 6
    Scammy pricing structure
  • 0
    Aggressive Github permissions
Pros
  • 110
    Dynamic and idempotent server configuration
  • 76
    Reusable components
  • 47
    Integration testing with Vagrant
  • 43
    Repeatable
  • 30
    Mock testing with Chefspec
Integrations
dotCloud
dotCloud
GitHub
GitHub
Xcode
Xcode
Azure Container Service
Azure Container Service
Slack
Slack
Heroku
Heroku
JavaScript
JavaScript
Node.js
Node.js
Python
Python
Amazon EC2
Amazon EC2
Amazon EC2
Amazon EC2
Rackspace Cloud Servers
Rackspace Cloud Servers
Microsoft Azure
Microsoft Azure
HP Cloud Compute
HP Cloud Compute
Joyent Cloud
Joyent Cloud

What are some alternatives to CircleCI, Chef?

Jenkins

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

Ansible

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

Terraform

Terraform

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Puppet Labs

Puppet Labs

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana