Chef capabilities are available as cloud-based services, providing customers with the same powerful automation capabilities with the added benefit of reduced infrastructure overhead and faster time to value.

    Ratings and reviews

    4.2
    85 ratings
    55%
    34%
    9%
    0%
    1%
    1 AWS reviews
    |
    84 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (85)
    Kwazikonke M.

    Exceptional Monitoring and Compliance Tool

    Reviewed on Jul 01, 2026
    Review provided by G2
    What do you like best about the product?
    I like Progress Chef for its visibility and monitoring capabilities. It allows us to easily track Chef-managed VMs, verify they are checking in successfully, and quickly identify systems that require attention. It helps us see which VMs are healthy, failing, missing, or checking in as expected, and when a system stops reporting, we can identify and investigate it immediately.
    What do you dislike about the product?
    Nothing
    What problems is the product solving and how is that benefiting you?
    I use Progress Chef to monitor and track VMs, ensuring regular check-ins and compliance. It solves the challenge of monitoring managed VMs and provides visibility to quickly identify systems needing attention, helping maintain our infrastructure standards.
    Chathura Nuwan

    Cloud automation has saved time by managing VM patching and security without a control node

    Reviewed on Jul 01, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for Chef SaaS is cloud infrastructure management. I use Chef SaaS for cloud VMs patch updates, service installation, and security state checks.

    What is most valuable?

    The best feature Chef SaaS offers in my experience is that we do not need to manually install a Chef control node. In a traditional way, we have to install and manage the Chef control node, and we need to patch it, but here, we do not need to maintain a Chef control node, which is actually the main feature.

    This has made my daily work easier and saved me time because we do not need to maintain Chef server. We only need to write the cookbook for managing Chef client, and we can save time because we do not need to worry about the Chef control node. We only have to write a cookbook and apply those changes to Chef client through Chef worker node, which is how we save time.

    Chef SaaS has positively impacted my organization by saving more time. We do not need to control Chef control node and we can apply the required changes for VMs quickly, which is a big advantage for our organization. We are saving time because we only spend time building the Chef cookbook and can easily apply those changes quickly after writing it. After writing the Chef cookbook, it only takes a few seconds to apply those changes for Chef client.

    For how long have I used the solution?

    I have been using Chef SaaS for one year.

    What do I think about the stability of the solution?

    Chef SaaS has already improved the reliability of the control node. I mainly consider reliability, and I believe they have already built the reliability of the control node from their architecture, making Chef SaaS the best product for automation environments. When considering the reliability of Chef SaaS's AI capabilities, it only needs to be connected between control node and client. If connectivity exists, we can ensure 100% reliability and output of this product.

    What other advice do I have?

    Regarding Chef SaaS's AI capabilities, I believe it satisfies governance and security requirements. I recommend this product for large scale businesses that manage large VM infrastructures because it is effective for cloud or hybrid environments. They can save time and efficiently apply changes for the required environment. I suggest this product since they can save time and apply changes quickly without needing to manage their own Chef controller node, which is a big advantage. I rate this product a 9.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Aaron Prashanth

    Consistent releases have improved collaboration while configuration procedures still need simplification

    Reviewed on Jun 30, 2026
    Review provided by PeerSpot

    What is our primary use case?

    We are using Chef SaaS for the release process of all product items and for configuring all our products. Chef SaaS helps us maintain consistent application behavior by aiding with consistency and automating our configuration processes.

    What is most valuable?

    What stands out for me in Chef SaaS is that the procedure is straightforward and the release goes smoothly because we can create different versions according to our own requirements.

    Chef SaaS helps with collaboration between our development and operations team. A benefit I can see is that configuring is easier because developers commit new code and new versions, and using Chef SaaS, we can create different cookbooks. Cookbooks contain different recipes, and different cookbooks represent different versions. Using these versions, we can consolidate and create a new package that will help us with the release.

    Since this is a product-based company and our product is wind turbines, every time we have a product release or patch release, Chef SaaS helps us tremendously. We release different patch cycles such as LTS patch cycles, Windows patches, or any kind of patch feature and built features. To maintain the cycle, the process is quite smooth.

    What needs improvement?

    An area of improvement is that if you compare Chef SaaS to Ansible, Ansible is much faster and the process is easier and faster, but Chef SaaS is more complicated. It has different kinds of file sets, so to make it straightforward, I feel they should improve the procedure and the entire process. The server setup could also be faster and easier.

    Chef SaaS is more complicated than Ansible, but Ansible is faster and generally easier.

    For how long have I used the solution?

    I have been working with the product for almost four years, close to five years, but I do not directly use this product myself. My colleagues do use this.

    What do I think about the stability of the solution?

    Chef SaaS is stable and we have never faced any issues with it. It is quite reliable in that regard, and since it is mature and established, it is capable enough to manage large infrastructures.

    What do I think about the scalability of the solution?

    Chef SaaS is scalable, but we are not scaling it in our infrastructure. We could scale it in better ways by creating different management systems and from management you could create parallel or centralized management, but we are not trying to scale it up. We are doing it in a consistent way for consistency purposes, and we do not want anything to have issues.

    How are customer service and support?

    I am not certain about this because I have never reached out for technical support for Chef SaaS. Probably other colleagues who use it exclusively on a day-to-day basis might have, but my team has not reached out for any kind of support so far.

    How was the initial setup?

    The installation part is moderate, somewhere in between.

    The biggest challenge when installing Chef SaaS is typically setting up the server and workstation. You need to maintain node certificates, install the certificates, create different environments, and create cookbooks and policy files. There are significantly more components to manage.

    What was our ROI?

    As for the return on investment, I would say that maybe a bit of time can be observed with Chef SaaS. I would probably not say it is time-saving. It does consume some time, but the impact is neutral.

    What's my experience with pricing, setup cost, and licensing?

    Chef SaaS is a bit expensive, but not very much so.

    Which other solutions did I evaluate?

    I do work with Ansible, vSphere, Azure, and others. We do use GitLab and Black Duck. We do use Ansible, but not very exclusively for any specific purpose. We are using it for our own internal work.

    What other advice do I have?

    We do not use the InSpec feature. I would rate this product seven point five out of ten.

    Anshul S.

    Configure automation with Chef

    Reviewed on May 24, 2024
    Review provided by G2
    What do you like best about the product?
    This works on pull mechanism also configured bulk servers in a single go
    What do you dislike about the product?
    As there are some clouds like terraform, it do not support server of it.
    What problems is the product solving and how is that benefiting you?
    Automating the large numbers of servers in single go that reduces the manual work
    Apparel & Fashion

    Automate Configuration Management

    Reviewed on May 24, 2024
    Review provided by G2
    What do you like best about the product?
    The product is super easy when it comes to usage
    What do you dislike about the product?
    Implementation could have been made less complex
    What problems is the product solving and how is that benefiting you?
    Configuration of remote servers
    Suvom D.

    Best tool to automate Infrastructure

    Reviewed on May 24, 2024
    Review provided by G2
    What do you like best about the product?
    The best part of using Progress Chef is that it doesn't depend on a single cloud infrastructure. We offer SaaS as well as Product as a Service. Given this, we provide infrastructure code and Docker images for applications to our customers. Therefore, we required a service that can manage both infrastructure code and application deployment, including the pipeline for future releases. In these terms, Progress Chef is the go-to solution for us, whether our customer is in AWS, Azure, or GCP.
    What do you dislike about the product?
    I would like it even more if I can get a managed service for using Progress Chef. The Infrastructure requirement for Progress Chef is a bit complex.
    What problems is the product solving and how is that benefiting you?
    The problems that are solved by Progress Chef are as follows:
    1. It doesn't depend on cloud infrastructure. It can be used for AWS, Azure, GCP or On-Prem deployment as well.
    2. Single software can be used for configuration management, CI/CD, IaC.
    3. To deploy an entire application with infrastructure in a customer environment irrespective of the cloud provider they use, Progress Chef is the best solution available in the market.
    Banking

    Automate your configuration management

    Reviewed on May 23, 2024
    Review provided by G2
    What do you like best about the product?
    It is super easy to use, You can create groups that are helpful
    What do you dislike about the product?
    Maintainence is difficult since it has many parts
    What problems is the product solving and how is that benefiting you?
    It helped me in configuration of my cloud servers
    Shivendra S.

    Application modernization with Progress Chef

    Reviewed on May 22, 2024
    Review provided by G2
    What do you like best about the product?
    Securities and compliance integration and application packaging
    What do you dislike about the product?
    Support and problem solving with the prod is concerning
    What problems is the product solving and how is that benefiting you?
    Automating the workflow and applicationmodernization
    Firoj S.

    Chef Recipes

    Reviewed on May 21, 2024
    Review provided by G2
    What do you like best about the product?
    There are multiple reasons why i love chef, like being open source, auotmate the configuration, accuracy.
    What do you dislike about the product?
    For the general audience (college students) not hear about chef easily. They could have better marketing around it.
    What problems is the product solving and how is that benefiting you?
    By using chef we are taking L3 backup from one cloud provder to another. It saves us incase there is any breakdown/outage in cloud provider services.
    Naveenkumar M.

    Chef software devops automation product

    Reviewed on May 21, 2024
    Review provided by G2
    What do you like best about the product?
    Broad user community
    ChefConf is an excellent conference
    What do you dislike about the product?
    It remains to be seen how Chef evolves after being acquired by Progress
    The Chef technology itself for cookbook development has a not-insignificant learning curve due to how powerful it is
    What problems is the product solving and how is that benefiting you?
    Using Chef to automate configuration management allows DevOps teams to define policies that are repeatable, consistent and reusable. The result is increased business agility and security because all systems and resources are continuously and automatically evaluated, corrected, and modified.