One canvas for every cloud
Why we stopped tab-hopping between five provider consoles and built a single visual surface for multi-cloud infrastructure.
Running one real system usually means living in five different places at once. A tab for the AWS console, a tab for GCP, a portal for Azure, a dashboard for Hetzner, and a terminal with a wall of Terraform and half-remembered SSH aliases. None of them agree on where anything is.
CrossXCloud started from that frustration. We wanted the infrastructure to look the way we already think about it: a set of things that are connected, on one surface, that we can see all at once.
What the canvas is
The canvas is a single visual space where every resource is a node. Compute, networks, storage, and the IPs between them all sit on the same board, regardless of which provider they actually run on. You drag a node out, wire it to another, and the connection means something concrete.
It is not a diagram that drifts out of date. The board is the source of truth, and the real infrastructure is reconciled to match it.
Why one surface matters
Context switching is not free. Every time you move from one console to another you reload a different mental model: different names for the same thing, different defaults, different ways of showing state. The cost is quiet but constant.
The moment you can see the whole system in one place, most of the guesswork disappears.
One surface does not make the clouds identical. AWS is still AWS. What it does is put them next to each other, in the same language, so the shape of your system is finally legible.
This is the first of a series where we will get into how the canvas works underneath, what we chose to ship first, and what we deliberately left out. More soon.
