Upbound Spaces are hosting environments for Upbound’s managed Crossplane control planes.
Upbound offers a Global Console, with complementary API and CLI, that users use to manage operations for MCPs. MCPs are deployed in hosting environments called Spaces. Upbound supports two types of Spaces: Cloud Spaces and Connected Spaces. Users have the freedom to choose whether to run MCPs in Cloud Spaces, Connected Spaces, or both.
Cloud Spaces
Cloud Spaces are multi-tenant deployments of Upbound, operated by Upbound inside our cloud environments. With Cloud Spaces, you get a fully managed SaaS experience, MCPs, hosting infrastructure management, persistent storage management, and backup and restore management.
Choosing to run in Upbound’s multi-tenant Cloud Spaces offers the most turnkey managed Crossplane experience. Upbound hosts Cloud Spaces in multiple Cloud Service Providers and regions. This gives you the flexibility to have a fully managed SaaS experience wherever you need to run Crossplane.
Self-hosted Spaces
A self-hosted Space is a single-tenant deployment of Upbound within your infrastructure. Upbound offers self-hosted Spaces as a Disconnected Space or Connected Space.
Connected Spaces
Connected Spaces allows you to use Upbound’s Console, CLI, and API to manage your control planes.
We’ve packaged the best parts of Upbound into a Helm chart and can deploy and operate them on your own infrastructure. You get the best of SaaS with the benefit of additional security guarantees and a deployment free of noisy neighbors.
With Connected Spaces, it’s more than just an on-premises deployment of your MCPs; the Crossplane experts at Upbound are operating your control planes alongside your team for a truly fully managed Crossplane solution. The Upbound team is on-call for your control planes.
Disconnected Spaces
Like a Connected Space, a Disconnected Space is a single-tenant deployment of Upbound within your infrastructure, such as your Amazon Web Services (AWS) cloud account or Microsoft Azure subscription. However, there’s no connectivity to the rest of the Upbound product and you’re limited to a command-line interface to interact within a single Space context.
