Product
The Source-to-View Workflow
From connected source to revisioned, reusable cloud views — with the origin of every element still on screen.
Connect. Compose. Use.
- Connected Source
- Accepted Revision
- Generated View
- Provenance Inspector
The Mechanism
Three Phases, One Explainable Pipeline
Each phase changes what Kumo.io knows and what you can see. Nothing is inferred that the source did not report.
Phase One · Connect
Point Kumo.io at a Scope You Control
Configure a supported cloud source with read-only access and an explicit scope, then run a sync. Kumo.io records the run and accepts observations into a source snapshot.
- Read-only credentials, scoped by you
- Every sync run recorded with its outcome
- Failures surface as failures, never as stale success
Phase Two · Compose
Observations Become an Immutable Revision
Resources and relationships from the accepted snapshot form a workspace graph revision. Revisions are immutable, so any view built on one can be reproduced exactly — and two revisions can be compared.
- Immutable graph revision per accepted sync
- Relationships derived from reported configuration
- Revision-to-revision comparison for change
Phase Three · Use
Generate the View the Question Needs
Focus a revision with an environment or query, apply a reusable view recipe, then save, share or export the result. The same revision supports many valid views without redrawing anything.
- Reusable view recipes, not one-off diagrams
- Save, share, embed or export
- User-authored context stays marked as user-authored
Source configuration screen: scope selector, read-only credential status, and the result of the most recent sync run.
Revision timeline with two revisions selected and the diff panel open, showing added, removed and changed resources.
One revision rendered as two different saved views side by side — for example a network view and an application-ownership view.
Provenance
Every Element Can Answer Where It Came From
This is the part that is hard to fake and easy to verify. Select anything in a view and Kumo.io states its origin, the revision it belongs to, and when that revision was accepted.
A generated view with one resource selected and the provenance inspector open, showing origin, source, revision ID and last successful sync.
- 1
Origin
Discovered, derived, imported or user-authored — stated per element, never blended into one undifferentiated picture.
- 2
Source and Scope
Which connected source reported the element, and the scope that source was configured to observe.
- 3
Revision
The immutable revision this view was generated from, so the same view can be regenerated or compared later.
- 4
Last Successful Sync
When Kumo.io last successfully observed the source — shown on screen rather than implied by the diagram looking current.
Starter placeholders must be replaced with real, approved captures before this page is published.
What You Get
Documentation That Survives the Next Change
The mechanism matters because of what it lets a team stop doing.
Architecture That Documents Itself
Stop rebuilding the same diagram every quarter. Generate the view from the current revision and reuse it as documentation.
Discovery and DocumentationContext When Something Breaks
Inspect current relationships and compare revisions to see what changed, instead of reconstructing the environment from memory.
Artifacts a Reviewer Accepts
Produce explainable, dated views with visible origin — the kind of artifact a security or compliance review can actually use.
Bring Clarity to Your Cloud