Product
Know What You Are Looking at—And Where It Came From.
Understand what Kumo.io observed, what it derived and what a user added.
Freshness. Origin. Coverage. Read-only.
- Latest Successful Sync
- Origin
- Relationship
- Coverage
The Mechanism
Four Things Kumo.io Will Always Tell You
Trust here is a set of product mechanisms, each of which you can check on screen. None of them require taking our word for it.
Phase One · Freshness
When the Source Was Last Successfully Observed
Kumo.io displays the latest successful sync, the state of the source and the revision on screen — so a view that looks current can be confirmed as current, and a stale one is visibly stale.
- Latest successful sync shown, not implied
- Failed syncs surface as failures, never as quiet staleness
Phase Two · Origin
Discovered, Derived, Imported or User-Authored
Every element is classified by where it came from, and the classification is visible in the view rather than buried in a detail panel. Human context stays clearly human.
- Four origin classes, stated per element
- User-authored content never blends into discovered content
Phase Three · Explanation
Why That Relationship Is on the Diagram
Select a relationship and Kumo.io states which source, rule or action produced it. A line between two resources is always attributable to something.
- Source, rule or action named per relationship
- No unexplained edges
Phase Four · Boundaries
What Is Supported, and What Is Not, with a Date on It
Provider and workflow coverage is described with dated limitations rather than a logo wall, and Kumo.io observes cloud configuration read-only — it does not deploy or change customer infrastructure.
- Coverage stated by scope, with dated limitations
- Read-only observation; Kumo.io never changes your infrastructure
Source list showing last successful sync per source, including one source in a failed or degraded state.
A view containing discovered, derived and user-authored elements, with the origin legend visible and one user-authored node selected.
A relationship selected in a view with its explanation panel open, naming the source and rule that produced it.
Coverage detail for one provider showing supported resource types, known limitations and the date the scope was last validated.
Proof
Select Anything and Ask Where It Came From
This is the mechanism the rest of the product rests on, and it is the easiest one to verify for yourself in a demo.
A generated view with one resource selected and the provenance inspector open, showing origin, source, revision ID and last successful sync together.
- 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
What Visible Provenance Changes
Diagrams Stop Needing a Caveat
Share a view without the verbal footnote about which parts are current and which were drawn by hand last quarter.
Discovery and DocumentationReviewers Can Check Your Work
Give a reviewer an artifact whose claims they can verify themselves, instead of asking them to trust the author.
Investigations Start from Fact
Distinguish what was observed from what someone assumed, at the moment it matters most.
Bring Clarity to Your Cloud