Plan before you apply, on a canvas
How CrossXCloud brings the diff-before-apply discipline of Terraform to a visual editor, without the wall of HCL.
Direct-manipulation tools have a reputation problem in infrastructure, and it is a fair one. Click a button in a console, something changes immediately, and there is no record of what you intended versus what actually happened. That is how you end up afraid of your own dashboard.
Terraform solved the intent problem with a plan. You describe the desired state, it computes a diff against reality, and nothing changes until you approve. The discipline is excellent. The authoring experience, a thousand lines of HCL spread across modules, is not something everyone wants to live in.
Keeping the plan, dropping the wall
CrossXCloud keeps the plan and moves the authoring to the canvas. When you rearrange nodes, add a network, or delete a machine, you are editing desired state. Nothing is applied yet.
When you are ready, CrossXCloud computes the diff between the board and the live infrastructure and shows you exactly what will change:
- Resources that will be created
- Resources that will be updated, and which fields
- Resources that will be destroyed
You read it, you approve it, and only then does anything happen. The visual edit is convenient. The plan is what keeps it safe.
Reconciliation, not fire-and-forget
The other half is what happens after apply. The canvas does not assume success and walk away. It reconciles: it watches the real state, compares it to what you asked for, and surfaces drift when the two disagree.
That means the board stays honest over time. If something changes out from under you, you see it on the canvas instead of discovering it during an incident.
We will write more about how reconciliation works, including how we handle partial failures and resources that take a while to settle.
