How does Resource Graph help before deployment?

It helps teams see upstream and downstream dependencies before a change is applied, reducing surprise impact in production.

Does Resource Graph help with drift?

Yes. Resource Graph can connect drift findings to affected resources and dependencies so teams understand operational impact.

Is the Resource Graph built from live state or hand-drawn?

It is built from live state, not a hand-drawn diagram. ops0 reads dependency topology directly from your running infrastructure, so upstream and downstream relationships stay accurate as the estate changes.

Can Resource Graph show the blast radius of a change?

Yes. Before a change, Resource Graph shows its blast radius and traces how a variable propagates through dependent resources, so you can see what a change touches before approving it.

Can I query the resource graph directly?

Yes. ops0 keeps queryable, database-backed state you can ask SQL-style questions of, so you can answer questions like which resources depend on a given subnet instead of clicking through a diagram.

Resource graph

Understand what the risk can break.

Name: ops0
Author: ops0

ops0 maps dependencies and blast radius from live state, so you know what a fix or a failure touches before it happens.

Live-state topology

Blast radius before a change

Drift-aware graph

Queryable infrastructure

ops0.ai/features/resource-graph

ops0 resource graph query console: a natural-language query returns production resources with active security findings and monthly spend, and the blast radius panel shows that changing aws_db_instance.main affects 6 downstream resources across 1 level

Live

State

not a diagram

Both

Directions

upstream + downstream

Blast radius

Before a change

not just a diff

Drift-aware

Graph

stays current

Queryable

With SQL-style queries

database-backed

Dependency graphLive from state

Nodes

Edges

Owners

Topology

See the real dependencies.

Upstream providers and downstream consumers.

Built from live state, not a hand-drawn diagram.

Linked to the IaC that owns each resource.

Blast radius preview7 affected

private_subnet_count change in network-core

ECS Servicecheckout-service

VPCpayments-vpc

Lambdafraud-worker

Kinesis Streamanalytics-pipeline

Severity

High

Change type

Shared subnet variable

Consumers

4 downstream projects

Drift linked

2 resources

Impact

Blast radius before a change.

See what a change touches before it is approved.

Trace variable impact across the graph.

Know the blast radius, not just the diff.

Graph queryDrift-aware

Query

“What depends on payments-platform, and is any of it drifted?”

Result

checkout, fraud, analytics3 consumers

fraud-workerdrifted 3 hours ago

Cost

per node

Exposure

per edge

Ownership

per project

Queryable

Ask your infrastructure directly.

Query dependencies, cost, and exposure in one place.

The graph is drift-aware, not a stale snapshot.

Answers come from live state, database-backed and queryable.

Under the hood

A graph you can query, not just look at.

Built from live state

The graph is generated from what is actually running, not a hand-maintained diagram.

Upstream and downstream

See what a resource depends on, and everything that depends on it, in both directions.

Linked to IaC ownership

Every node traces back to the Terraform, OpenTofu, or Oxid that owns it.

Blast-radius analysis

Know what a proposed change touches before it is approved, not after it ships.

Variable impact tracing

Follow a shared variable or module across every resource it reaches.

Queryable, database-backed state

Ask SQL-style questions over your infrastructure and get an answer from live state.

Common questions

Resource Graph is a view of infrastructure relationships, dependencies, state files, drift, and blast radius across cloud and Kubernetes resources.

See the topology
before you touch the system.

Resource Graph shows what a fix or a failure touches. Workflows is where the reviewed change ships.

Explore Workflows