Connecting your first provider

Getting a cloud account onto the canvas takes a few minutes. Here is the shape of it, from an empty board to your real resources showing up as nodes.

Add the account

Open the command palette and choose to connect a provider. CrossXCloud will ask for credentials scoped to what it needs. Credentials go into the vault, encrypted at rest, and are never rendered back into the interface once saved.

You can connect more than one account per provider, which is useful if you separate staging and production, or run different regions as different accounts.

Let it read your infrastructure

Once the account is connected, CrossXCloud reads the existing resources and places them on the canvas as nodes. Nothing is changed during this step. It is a read, so you can connect an account to an established system without any risk of it touching live resources.

You will see your compute, networks, and storage laid out and wired according to how they actually relate. This first view is often the first time people see their whole account in one picture.

Make a change

From here the normal loop applies. Edit the board to describe what you want, review the plan, and apply. A good first change is something small and reversible, so you can watch the full cycle end to end:

1. Move or add a node on the canvas
2. Open the plan and read the diff
3. Approve, and watch the apply run
4. Confirm the board and the live state agree

That loop is the whole product in miniature. Once it feels natural on one account, adding the rest of your clouds is more of the same, on the same surface.

For the full reference, see the docs.