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

Chef SaaS vs Upbound Crossplane comparison

Sponsored
 

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

Arctera Insight Platform
Sponsored
Average Rating
0
Number of Reviews
0
Ranking in other categories
Data Governance (61st), Compliance Management (31st)
Chef SaaS
Average Rating
8.0
Number of Reviews
2
Ranking in other categories
AWS Marketplace (119th)
Upbound Crossplane
Average Rating
8.4
Number of Reviews
6
Ranking in other categories
AWS Marketplace (9th)
 

Featured Reviews

Use Arctera Insight Platform?
Leave a review
Aaron Prashanth - PeerSpot reviewer
Dev Ops 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.
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
902,894 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Construction Company
53%
Media Company
11%
Comms Service Provider
7%
Healthcare Company
5%
Construction Company
32%
Manufacturing Company
11%
Comms Service Provider
10%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
No data available
 

Questions from the Community

Ask a question
Earn 20 points
Ask a question
Earn 20 points
What is your experience regarding pricing and costs for Upbound Crossplane?
The documentation and learning curve for Upbound Crossplane were really smooth initially to set up. However, our use ...
What needs improvement with Upbound Crossplane?
Upbound Crossplane can be improved if they can add more AI agentic workflows. In the open source Upbound Crossplane, ...
What is your primary use case for Upbound Crossplane?
My main use case for Upbound Crossplane is that initially we were frustrated with using Terraform, and right now all ...
 

Overview

Find out what your peers are saying about Dice, HailBytes, PeerSpot and others in AWS Marketplace. Updated: June 2026.
902,894 professionals have used our research since 2012.