Upbound

Crossplane with a support contract

Upbound is the company behind Crossplane's original development and sells a commercial distribution of it, called Upbound Crossplane (UXP), along with a hosted environment called Spaces. If you already run upstream Crossplane and the question is who patches the AWS or Azure provider when a CVE lands, this is the paid answer. If you have not used Crossplane, the first thing to settle is whether you want a Kubernetes-based control plane for cloud resources at all; Upbound does not make that concept easier, it makes it operable.

What the licence actually unlocks

UXP runs without a licence and provides the core Crossplane control plane. The docs list five features that need a Standard plan or above:

• Backup and Restore for control planes
• Function Scale-to-Zero
• Official Package Patch Releases, meaning security and bug-fix patches for Official Providers
• Provider Pod Autoscaling
• Secrets Proxy, which reads and writes provider secrets to HashiCorp Vault

Patch releases are the real argument for paying. Provider packages for large clouds contain hundreds of CRDs, and keeping them current is what most self-run Crossplane installs struggle with.

Hosted or self-managed

Upbound will host UXP for you in Spaces, its control-plane-as-a-service environment, or you can self-manage UXP on your own Kubernetes cluster. Self-hosted Spaces, Console and Hub are listed only on the Business Critical tier, so a regulated team that must keep everything in its own network is pushed to the most expensive plan.

Pricing, as published

Standard starts at $1,000/month, consumption-based, for up to 5 control planes and 10 team members. Enterprise (unlimited control planes and members, SSO/SAML, fleet management) and Business Critical are custom quotes.

On top of the plan, managed resources are metered on a declining scale: roughly $1.095 per resource for the next 10,000, falling to $0.73 for the next 200,000, with 400,000+ by quote. The page says plan tiers have consumption minimums but does not state them. It also describes the resource rate as per hour in prose and per month in the table, so work out which one applies before modelling a bill. The FAQ separately mentions a month-to-month Team Plan with a $150/month usage credit whose licence fee is not stated.

The awkward part

You are paying for operations on a tool whose learning curve is the main barrier. Writing compositions, functions and claims is real platform-engineering work, and Upbound's pricing assumes you are already committed to it. The unpublished minimums mean you cannot confirm cost without talking to sales.

Where it fits

Platform teams building an internal developer platform on Kubernetes, with enough cloud resources that a per-resource metered bill is reasonable, get the most from it. A team managing 40 S3 buckets and a VPC would be better served by OpenTofu.