Sold by
Chef SaaS
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.
Reviews (91)
Bongisiwe S.
Streamlined DevOps with Quick Deployment and Security
Reviewed on Jul 11, 2026
Review provided by G2
What do you like best about the product?
I like that Progress Chef simplifies a DevOps engineer's work by deploying VMs seamlessly and quickly, which helps application teams not worry about deployments. It saves a lot of time since deployment can be done with API calls and agents installed, and you just need to run the pipeline. The process is also secure.
What do you dislike about the product?
We need more features that include AI as the world and business is moving to AIOps.
What problems is the product solving and how is that benefiting you?
I use Progress Chef to deploy and maintain infrastructure quicker and easier. It simplifies a DevOps engineer's work by making deployments seamless and secure. It saves time by allowing deployment with API calls and pipelines.
Information Technology and Services
Streamlines Task Management with Ease
Reviewed on Jul 08, 2026
Review provided by G2
What do you like best about the product?
I use Progress Chef to manage and streamline workflows, and I really like the task tracking and the dashboard view. It makes it easy to see progress at a glance and quickly check what's done or still pending. These features help me stay organized and focused by allowing me to see what needs attention and track progress efficiently, saving me time. Additionally, the initial setup of Progress Chef was quite straightforward, and it didn't take long to get familiar with the platform and start using it effectively.
What do you dislike about the product?
It works well overall but when there are many tasks, it can take a bit more time to go through everything. A slightly quicker way to filter or find specific items would make it even better.
What problems is the product solving and how is that benefiting you?
I use Progress Chef to streamline workflows, track tasks, and ensure projects stay on schedule. It keeps me organized, prevents missing tasks, and saves time with a dashboard view to quickly check progress.
Anonymous
Powerful Automation with a Steep Learning Curve
Reviewed on Jul 08, 2026
Review provided by G2
What do you like best about the product?
I like Progress Chef's ability to automate infrastructure management while ensuring consistency across all servers. Instead of configuring systems manually, I define the desired state in code, and Chef applies it automatically, reducing downtime and improving consistency. Once it's properly implemented, it becomes a powerful and reliable tool for automating infrastructure at scale. After migrating from Puppet, we have found Chef to offer a more flexible and maintainable automation platform.
What do you dislike about the product?
One area where Progress Chef could be improved is its learning curve, it takes more time to understand concepts. Debugging issues are challenging, setting up and managing Chef servers are complex for smaller environments.
What problems is the product solving and how is that benefiting you?
I use Progress Chef to manage servers, reducing downtime and improving consistency. It automates infrastructure management, allowing me to define desired states in code while ensuring consistency across servers.
Anonymous
User-Friendly UI with Detailed Error Tracking
Reviewed on Jul 08, 2026
Review provided by G2
What do you like best about the product?
I find the UI of Progress Chef to be user-friendly, which really helps in displaying all the servers it supports. It shows the errors in detail for servers that are failing, and you can track back to when the failure started, which is incredibly useful. Every morning, I conduct check-ins to see which servers need attention or have been decommissioned, and this tool assists in alerting the VM owners effectively.
What do you dislike about the product?
None so far as we only use it for observability nothing much
What problems is the product solving and how is that benefiting you?
I use Progress Chef for observability, checking health status, identifying server issues, and alerting VM owners about failures. Its user-friendly UI shows supported servers and detailed errors, helping me track problems back to their start.
Nomzamo X.
Efficient Automation Tool with a Learning Curve
Reviewed on Jul 06, 2026
Review provided by G2
What do you like best about the product?
I like Progress Chef's ability to automate infrastructure management and maintain consistent server configuration across environments. It reduces manual work, it's reliable, and saves time.
What do you dislike about the product?
Learning can be a challenge. Improved documentation would make it easier. I think a more step-by-step guide for beginners and clear troubleshooting documentation for common errors would help.
What problems is the product solving and how is that benefiting you?
I use Progress Chef to automate and configure servers, eliminating manual setup errors and maintaining consistent configurations. It's reliable, reduces manual work, and saves time.
Judith Mologadi M.
Simplifies Automation and Boosts Consistency Across Environments
Reviewed on Jul 06, 2026
Review provided by G2
What do you like best about the product?
It simplifies automation,improves consistency and reduce manual effort in managing our environments
What do you dislike about the product?
The initial setup and troubleshooting can be complex for new users
What problems is the product solving and how is that benefiting you?
Progress chef helps automate infrastructure and configuration management,reducing manual effort,improving consistency and enabling faster,more reliable deployment
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?
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?
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