No more typing reviews! Try our Samantha, our new voice AI agent.

Chef SaaS vs Upbound Crossplane comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Chef SaaS
Ranking in AWS Marketplace
59th
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Upbound Crossplane
Ranking in AWS Marketplace
6th
Average Rating
8.4
Number of Reviews
9
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the AWS Marketplace category, the mindshare of Chef SaaS is 0.2%, up from 0.1% compared to the previous year. The mindshare of Upbound Crossplane is 0.3%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AWS Marketplace Mindshare Distribution
ProductMindshare (%)
Upbound Crossplane0.3%
Chef SaaS0.2%
Other99.5%
AWS Marketplace
 

Featured Reviews

Aaron Prashanth - PeerSpot reviewer
DevOps Engineer at Siemens Industry
Consistent releases have improved collaboration while configuration procedures still need simplification
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.
Diego Paradeda - PeerSpot reviewer
Senior Software Engineer at Philips
Automated infrastructure deployment has reduced our backend release time from days to hours
I found an issue with features that was difficult for me when we needed to retrieve some tags or IDs of a resource that we deployed using Upbound Crossplane, for example, the RDS. We encountered a problem where we needed to use the ID of the RDS in another document that we have, making it difficult to return this information using Upbound Crossplane deployment. I believe Upbound Crossplane could be improved by possibly having a feature that can return tags, IDs, or resources that were deployed inside AWS, such as needing to return the ID of the VPC that we create when using Upbound Crossplane. I think the current state of Upbound Crossplane is already good enough.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Chef SaaS is stable and we have never faced any issues with it, as it is quite reliable and, since it is mature and established, it is capable enough to manage large infrastructures."
"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."
"The best features Upbound Crossplane offers are infrastructure as Kubernetes APIs and self-service infrastructure, where developers can provision resources without cloud credentials, and its strong multi-cloud support that makes it useful in managing AWS, Azure, and GCP from a single control plane with valuable GitOps integration."
"Upbound Crossplane has impacted our organization positively as it has been a transformative experience because the main thing about transformation is how we were able to make our lives easier as engineers."
"When I provisioned PostgreSQL and S3 buckets through Crossplane, I noticed improvements in deployment speed, reliability, and team collaboration."
"Before choosing Upbound Crossplane, I evaluated various options, but I only found Upbound Crossplane to be the best choice."
"The time required to complete an environment setup was reduced from about one or two weeks to forty to fifty minutes."
"Upbound Crossplane has positively impacted our organization by reducing the pipeline time, saving time, and decreasing cost spending."
"We went from having a 28-member troubleshooting team down to four to five members of the platform engineering team."
"Upbound Crossplane has positively impacted our organization by allowing us to reduce our deployment time from three days to three hours for the entire back-end and entire infrastructure."
 

Cons

"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."
"One area where Upbound Crossplane can be improved is with API rate limiting."
"Regarding Upbound Crossplane's capabilities, I feel the governance and security is something which is lacking."
"Regarding Upbound Crossplane, I see room for enhancement in synchronizing the state file of Crossplane with Terraform, as 90% of organizations have generally implemented Terraform and have their own specific, environment-specific Terraform state files."
"Upbound Crossplane can be improved if they can add more AI agentic workflows."
"Upbound Crossplane was not stable in my experience."
"This was the only thing that we took as a disadvantage at the time of implementing, since we did not have any way to see what the Upbound Crossplane composition or what the Upbound Crossplane resource will do to the actual infrastructure."
"However, one area of improvement is the learning curve, as Upbound Crossplane concepts such as providers, compositions, and claims can be difficult for beginners."
"The documentation needs to be updated regarding the needed improvements for Upbound Crossplane. There is very little documentation online, and there are no tutorials for Upbound Crossplane."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,383 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
43%
Comms Service Provider
12%
Media Company
9%
Manufacturing Company
7%
Construction Company
26%
Outsourcing Company
11%
Manufacturing Company
11%
Comms Service Provider
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise4
 

Questions from the Community

What needs improvement with Chef SaaS?
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 se...
What is your primary use case for Chef SaaS?
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 your experience regarding pricing and costs for Upbound Crossplane?
I find the pricing, setup cost, and licensing of Upbound Crossplane very suitable for research and development.
What needs improvement with Upbound Crossplane?
One thing I have noticed about improving Upbound Crossplane is that, in Terraform, we can do a validation stage where people can say Terraform plan and see what changes it will do. It would be bett...
What is your primary use case for Upbound Crossplane?
Our main use case for Upbound Crossplane is that we are using Kubernetes as our main platform, and we have multiple clients who will be using this Kubernetes platform for deploying their container ...
 

Overview

Find out what your peers are saying about Chef SaaS vs. Upbound Crossplane and other solutions. Updated: September 2026.
915,383 professionals have used our research since 2012.