Provider support
CrossXCloud supports Hetzner, Google Cloud, AWS and Azure. All four are live. This page is the honest support matrix.
Support matrix
Section titled “Support matrix”| Provider | Compute | Private networks | Floating IPs | Status |
|---|---|---|---|---|
| Hetzner | Live | Live | Live | Live |
| Google Cloud | Live | Live | Live | Live |
| AWS | Live | Live | Live | Live |
| Azure | Live | Live | Live | Live |
“Live” means CrossXCloud makes real API calls against that provider and you can build and apply real resources. Every provider on this page meets that bar: each one authenticates, provisions compute, and creates private networks and floating IPs through its own SDK.
Live does not mean identical. Providers differ in what they can express, and the differences are described in the app rather than hidden — see what is supported per provider below.
What is supported per provider
Section titled “What is supported per provider”All four providers support the same real capabilities today: compute, private networks, and floating IPs. The underlying resource shapes differ (for example, a Hetzner Floating IP versus a Google Cloud static external address), but CrossXCloud presents the same canvas node types for all of them.
The compute catalog (server types, images, locations) is real per provider. The dropdowns you see in the inspector come from the provider’s catalog API, so what you see is what that account can actually create.
VPC and serverless strategies are interface-only stubs. They are not documented as features.
- Node types for the fields each provider supports per node.
- Compute nodes for creating servers.
- Networking for private networks and IPs.