Kumo.io

Product

Change the View, Not the Truth Underneath It.

Group by region, network, service, tag or your own hierarchy. Filter, annotate and switch templates to answer the question in front of you—without redrawing anything or losing the link to discovered state.

One revision. Many views. Nothing redrawn.

kumo.io / multi-view-demo
awsMicrosoft Azure
  1. One Revision
  2. Your Question
  3. View Template
  4. Saved View

How It Works

One Set of Infrastructure, Shaped to the Question in Front of You

A view is a recipe applied to a revision, not a drawing. Changing the view never changes what was discovered.

Phase One · Anchor

Every View Starts from a Chosen Revision

A view is generated from one fixed revision. That is what lets you reproduce it tomorrow and compare it against a later sync.

  • Tied to a named revision, not a moving 'now'
  • Same recipe and revision, same result

Phase Two · Shape

Choose the Question, Then Shape the Answer

Start from an environment, query, scope or saved template. Then group, filter, arrange and annotate until the view answers the question you actually have.

  • Group by region, network boundary, service, tag or your own hierarchy
  • Filter, arrange and annotate
  • Manual nodes, edges and notes stay separate from discovered relationships

Phase Three · Reuse

Save the Recipe, Not the Picture

Save the logic behind a view so it re-runs against later revisions and others on the team can reuse it—instead of becoming another diagram that quietly ages.

  • Re-run saved views against any later revision
  • Share as a template the whole team can use
kumo.io / views / newPlaceholder
Choosing the revision a view is built from.
kumo.io / views / payments-networkPlaceholder
The same revision as a network view and an application-ownership view.
kumo.io / templatesPlaceholder
One saved template applied to two revisions, each output dated.

Proof

The Same Infrastructure, Three Different Questions

Flexibility only counts if the underlying state stays the same. Each view names the revision it came from.

kumo.io / views / comparePlaceholder
Network, application-ownership and security-scope views of one revision.
  1. 1

    One Revision Underneath

    Each view names its revision. Different presentation, identical discovered state.

  2. 2

    Recipe, Not Redraw

    The view keeps the logic that produced it, so you reapply it instead of recreating it.

  3. 3

    Origin Still Visible

    Anything you add stays marked as user-authored in every view it appears in.

Product screenshots are coming soon. The quickest way to see this for yourself is on your own cloud: start a free trial, or request a walkthrough.

What You Get

What Flexible Views Are For

One Diagram Stops Being a Compromise

Stop negotiating one picture that half-serves four audiences. Give each audience its own view of the same infrastructure.

Discovery and Documentation

Reviews Get Their Own View

Build a scope-specific view for a review instead of annotating a general architecture diagram in the meeting.

The Team Inherits the Logic

A saved view outlives the person who built it, and keeps working as the environment changes.

Team Standardisation

Bring Clarity to Your Cloud

See Your Own Infrastructure from More Than One Angle.

See your own cloud in Kumo.io. Read-only access. Nothing in your account changes.

Free Trial