Product
Every Accepted State Becomes a Point You Can Revisit.
Compare immutable graph revisions to understand infrastructure change.
Immutable revisions. Explainable change.
- Accepted Revision
- Second Revision
- Comparison
- Change View
The Mechanism
Change You Can Point at, Not Change You Remember
Every accepted sync leaves a durable revision behind. Two of them are all you need to answer what changed.
Phase One · Anchor
Each Accepted Sync Becomes a Durable Point
A revision is an immutable record of what Kumo.io observed and accepted at a defined time. It does not drift, and it does not get overwritten by the next sync.
- Immutable once accepted
- Carries its own acceptance timestamp
Phase Two · Compare
Compare Two Revisions Instead of Two Memories
Select any two revisions and Kumo.io separates the difference into added, removed and changed. The comparison is structural, not a visual diff of two images.
- Added, removed and changed, as explainable categories
- Pairwise — no reliance on recollection or stale diagrams
Phase Three · Explain
Apply the Same View Logic to a Different Point in Time
Run a saved view recipe against an earlier revision to see the same question answered before the change, and carry revision and freshness metadata onto whatever you export.
- Same recipe, different revision
- Revision and freshness metadata preserved on outputs
Revision timeline for one workspace, showing several accepted revisions with their timestamps.
Two revisions selected with the comparison panel open, showing added, removed and changed resources grouped by category.
One saved view rendered against two different revisions, with each output labelled by revision and date.
Proof
What Changed, Stated as a Record
The claim is narrow and checkable: two accepted revisions, one structural comparison, categories you can explain to someone else.
Full comparison view with the change summary expanded and one changed resource selected, showing its before and after configuration.
- 1
Two Named Revisions
Both sides of the comparison are identified, with the time each was accepted.
- 2
Structural Categories
Added, removed and changed are separated rather than merged into one highlighted picture.
- 3
Per-Resource Detail
A change can be opened to see which attributes differed, not just that something differed.
- 4
Carried onto Exports
Revision and freshness context travels with the artifact, so a shared output stays interpretable.
Starter placeholders must be replaced with real, approved captures before this page is published.
What You Get
Why a Durable Record Matters
Incidents Start with What Moved
Open the comparison instead of reconstructing the environment from memory under time pressure.
Reviews Get a Dated Baseline
Point at the revision a review was performed against, and show what has changed since.
Documentation Stops Silently Rotting
Regenerate a view from the current revision rather than trusting a diagram nobody has checked.
Discovery and DocumentationBring Clarity to Your Cloud