
Overview

Product video
Chef SaaS is a cloud-based solution for infrastructure, compliance, and cloud security automation to manage entire IT estates. Enterprises can automate infrastructure configurations, view compliance and security postures of all devices, and detect and remediate configuration drift and security vulnerabilities.
If you need a customized private offer, we can create one tailored to your needs. Please contact us at marketplaces@progress.com
Highlights
- Configuration Management for All Platforms and Operating Systems
- Continuous Compliance Audits and Automated Remediation
- Cloud Security Posture Management (CSPM)
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months | Overage cost |
|---|---|---|---|
Node | 50 nodes of Chef SaaS | $7,000.00 | |
Nodes beyond 50 | Any nodes above 50 are priced per node | $150.00 | - |
Vendor refund policy
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Exceptional Monitoring and Compliance Tool
Cloud automation has saved time by managing VM patching and security without a control node
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?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Consistent releases have improved collaboration while configuration procedures still need simplification
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.