See the critical path, not the task list.
Below is a real project — the roadmap of Cubons itself — unfolded into a 3D structure by the live engine. Not a screenshot, not a video: grab it. This page walks you from this one concrete map to building your own in about a minute.
One project, laid out in space.
Every sphere is a task; the golden rings are goals. Position isn't decorative — left to right runs time, and the vertical lanes are work tracks: core, UI, data, cloud. The edges are dependencies: this task needs that one. A flat task list stores these links as a column nobody reads. Here they are the skeleton you're looking at.
A goal — the thing several chains of work converge into.
A blocked task: something upstream isn't done. The ring pulses until the blocker falls.
After you click a node — everything that holds it back, however deep the chain goes.
Everything that unlocks once the clicked node is done. The payoff, made visible.
Try these three moves — right in the panel above.
Take it in your hands
Drag to spin the structure, scroll or pinch to zoom. Notice how clusters and empty gaps read instantly from shape alone — no report can do that.
⟨ DRAG · SCROLL ⟩Click any node
The camera flies in and its whole dependency chain lights up: red is what holds it back, green is what it unlocks. Click empty space to let go.
⟨ CLICK A SPHERE ⟩Find the bottleneck
Spot a pulsing ⛔ ring and click it. Follow the red chain up — that's the real reason the launch is stuck, three tasks away from the obvious one.
⟨ FOLLOW THE RED ⟩The full app adds the rest of the toolkit: eight layouts on the same data, filters by track and status, an analysis mode with the critical path, a two-way data table, and editing with undo. Open this map in the app →
Structure is a spatial property.
"What blocks what" is a graph, and a graph has a shape. Flatten it into a list and the shape is gone — you re-derive it in your head every time you plan. A static cubon keeps the shape: bottlenecks look like knots, risky areas look like long thin chains, orphan work floats disconnected at the edge.
And because the whole scene — data, layout, camera, filters — serializes into one link (Cubonize), the shape travels. Your teammate opens the link and holds the same structure, no account required.
From your tracker to a map — about 60 seconds.
Drop what you already have
Open the app and drop a Trello board (JSON), a Jira or Linear CSV, an Asana export, an XLSX — or just paste a table straight from Excel or Google Sheets. The importer recognizes the source and keeps the links: Jira's "blocks", Trello's lists, epic-to-task nesting.
No dependency columns? Connect by column.
One click links rows through any shared column — assignee, category, sprint. Or draw the edges by hand: ⤳ Connect on a node, click the target, pick the type. The data table under the scene edits everything with undo.
Cubonize and hand it over
Hit ⚡ Cubonize — the entire living scene packs into one URL. Save it to your free cloud library to get a short link with access control: anyone-with-the-link or invited emails only.
🔒 Privacy: imports are parsed by the engine inside your browser. Your files aren't uploaded anywhere — a public test suite enforces that promise on every build.