Chef vs GitHub Actions comparison

Cancel
You must select at least 2 products to compare!
Chef Logo
Read 18 Chef reviews
373 views|251 comparisons
95% willing to recommend
GitHub Logo
1,044 views|963 comparisons
100% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between Chef and GitHub Actions based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed Chef vs. GitHub Actions Report (Updated: May 2024).
770,924 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The most valuable feature is the language that it uses: Ruby.""It is a well thought out product which integrates well with what developers and customers are looking for.""I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles.""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 scalability of the product is quite nice.""The product is useful for automating processes.""Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.""It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."

More Chef Pros →

"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform.""The most valuable feature of the solution is that it is a good product that offers stability and performance.""I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations.""The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency.""The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs.""It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."

More GitHub Actions Pros →

Cons
"The agent on the server sometimes acts finicky.""The AWS monitoring, AWS X-Ray, and some other features could be improved.""I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great.""Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that.""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.""Since we are heading to IoT, this product should consider anything related to this.""I would like to see more security features for Chef and more automation.""In the future, Chef could develop a docker container or docker images."

More Chef Cons →

"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex.""The reporting capabilities are somewhat limited.""The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly.""We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter.""The UI could be better.""There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."

More GitHub Actions Cons →

Pricing and Cost Advice
  • "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 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."
  • "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."
  • "We are able to save in development time, deployment time, and it makes it easier to manage the environments."
  • "We are using the free, open source version of the software, which we are happy with at this time."
  • "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."
  • "Pricing for Chef is high."
  • More Chef Pricing and Cost Advice →

  • "It is free and open platform, so I would rate it 1 out of 10."
  • "Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."
  • "For our basic usage, we didn't have to pay."
  • "It's low-priced. Not high, but definitely low."
  • More GitHub Actions Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    770,924 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
    Top Answer:Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
    Top Answer:I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just… more »
    Top Answer:The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these… more »
    Ranking
    15th
    out of 41 in Build Automation
    Views
    373
    Comparisons
    251
    Reviews
    4
    Average Words per Review
    304
    Rating
    6.8
    7th
    out of 41 in Build Automation
    Views
    1,044
    Comparisons
    963
    Reviews
    6
    Average Words per Review
    533
    Rating
    8.3
    Comparisons
    Jenkins logo
    Compared 20% of the time.
    AWS Systems Manager logo
    Compared 13% of the time.
    Microsoft Azure DevOps logo
    Compared 10% of the time.
    SaltStack logo
    Compared 8% of the time.
    Tekton logo
    Compared 39% of the time.
    Bamboo logo
    Compared 12% of the time.
    AWS CodePipeline logo
    Compared 9% of the time.
    GitLab logo
    Compared 8% of the time.
    Harness logo
    Compared 7% of the time.
    Learn More
    Overview

    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.

    GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.

    Sample Customers
    Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
    Information Not Available
    Top Industries
    REVIEWERS
    Computer Software Company30%
    Comms Service Provider20%
    Non Tech Company10%
    Legal Firm10%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company13%
    Government8%
    Manufacturing Company8%
    VISITORS READING REVIEWS
    Computer Software Company15%
    Financial Services Firm14%
    Manufacturing Company10%
    Healthcare Company8%
    Company Size
    REVIEWERS
    Small Business5%
    Midsize Enterprise35%
    Large Enterprise60%
    VISITORS READING REVIEWS
    Small Business19%
    Midsize Enterprise11%
    Large Enterprise69%
    REVIEWERS
    Small Business14%
    Midsize Enterprise29%
    Large Enterprise57%
    VISITORS READING REVIEWS
    Small Business29%
    Midsize Enterprise14%
    Large Enterprise57%
    Buyer's Guide
    Chef vs. GitHub Actions
    May 2024
    Find out what your peers are saying about Chef vs. GitHub Actions and other solutions. Updated: May 2024.
    770,924 professionals have used our research since 2012.

    Chef is ranked 15th in Build Automation with 18 reviews while GitHub Actions is ranked 7th in Build Automation with 6 reviews. Chef is rated 8.0, while GitHub Actions is rated 8.4. The top reviewer of Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". On the other hand, the top reviewer of GitHub Actions writes "Facilitates connectivity for developers and allows us to easily collaborate with other developers, regardless of location". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack, whereas GitHub Actions is most compared with Tekton, Bamboo, AWS CodePipeline, GitLab and Harness. See our Chef vs. GitHub Actions report.

    See our list of best Build Automation vendors.

    We monitor all Build 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.