Topology and dependency mapping

Point at the blast radius. Every dependency, drawn for you.

Before anyone changes a service, see what sits in front of it and everything it relies on behind it. You see the blast radius before the change, not after the outage.

Omnitam blast-radius graph for an orders API: the upstream gateway, load balancer and CDN it would impact, and the cluster, database, queue, topic and services it depends on
Real product screen, OmniShop demo data.

Reading the graph: “3 hops” on a node means three relationship steps from the selected service.

What you get

A map built from discovery, not from memory.

MAP

Dependency mapping

Every resource’s upstream and downstream relationships, derived from discovery and always current. The map draws on 47 relationship types and is redrawn on every scan, so it is never a diagram someone drew last year.

CTR

Centered on one resource

Open any resource and the graph centers on it: what’s impacted if it fails on one side, what it depends on on the other.

CHG

Impact before change

Before anyone changes a service, see everything upstream that breaks, from the storefront down through the load balancer.

Included on every plan

See the blast radius before the change.

Size your estate first with the free count script: read-only, AWS Config optional.