The Graph — node versioning
The Graph is node versioning for a 360 project: see every committed change, compare a draft, and choose where the next edit begins.
Every committed edit has a place in the story
Tool previews can sit as drafts while you compare them. Commit the result you want, branch from an earlier image when you want to try a different direction, and see which operation produced each version.
- draft
- Tool work you are still considering. Drafts are held so you can compare them, and they do not move the project on their own.
- commit
- The take you selected becomes a project step and the graph head moves to it.
- branch
- Carry on from an earlier result without erasing the direction you already took.
Node versioning is the derivation graph. Every change that writes pixels becomes a node. The durable pointer is head — the step the next edit will build on. Clicking an older node is a look, not a rewrite, until you make it head.
That is how you roll back without undo-stack theatre. Take a branch from an earlier result and keep the line you already liked. Prune if you only want one lineage. The graph lives on disk with the project.
-
1 · Do the work
Tile, Spot, Layers, post, upsample. Each commit adds a node and moves head forward.
-
2 · Open the graph
The Graph panel shows the tree. Click a node to view that state. The look is ephemeral until you write.
-
3 · Make Head
When that older take should be the new starting point, Make Head. The next edit parents from there.
-
4 · Branch or prune
Carry on from an earlier result without erasing the other direction. Prune keeps only the lineage you name.
How to think about it
head
The durable work pointer. Next ops parent from here.
view
Clicking a node inspects it. It does not rewrite head.
branch
A second line from an earlier node. Both stays exist.
Operations become typed nodes
The graph records the operation that made a step: source, pass, spot, offset, depinch, or upscale. That keeps the lineage legible while the image changes.
Fork lanes
A fork keeps a second lane from an earlier node, so a new direction does not erase the first.
Scrub a view
Scrub through a lineage to inspect its states. Looking at a node does not make it the durable head.
Prune a lineage
Prune when one named lineage is the only direction you want to keep.
- Batch import
- Point at a folder or a saved project and bring it in with its history intact, rather than opening one file at a time.
- Local files on disk
- Projects and their derivation graphs live as ordinary files on your own disk. Nothing is parked in a cloud project store you have to sign in to reach.
Undo goes all the way back.
Facts
| What is versioned | Each committed edit as a graph node |
| Durable pointer | head — advanced by creative ops |
| Rollback | View any node, then Make Head |
| Where it lives | On disk with the project |
Work on your own GPU
One-time licence from $360. No subscription, no per-render cloud charge.
30-day money-back guarantee on every purchase.