See what breaks
before you
touch it.
ZopNight draws your live cloud estate as one canvas. Pick a resource, pick an operation, and every connected resource lights up: destroyed, briefly interrupted, or safe. Classified from the resource's own type, not from a guess.
From inventory to a decision you can defend.
Four steps, none of which require opening a cloud console.
Discover, read only
ZopNight enumerates every resource across AWS, GCP and Azure without write access. Accounts, regions, networks, tags and attachments.
Assemble the fabric
Resources group by provider, account, region and VPC, VNet or network. Shared security groups on AWS, shared networks on GCP and shared subnets on Azure become hub nodes, so connectivity is drawn rather than implied.
Classify the hit
Pick a resource and an operation. Delete, stop or modify. The adjacency graph returns one-hop neighbours, each classified affected, warning or safe from its edge type and its own resource type. Safe has to be proven. Unmapped defaults to warning.
Score the risk
A 0 to 100 score folds in how much is affected, which environment it sits in, and how many teams and schedules own it. Everything safe scores zero.
The classification is not a heuristic.
Every impact verdict traces to a named rule and a detected edge.
- Edge detection
- Six edge types, each from real resource metadata.
db_accessfrom a shared security group, network or subnet.routes_tofrom load balancer targets.attached_tofrom volume attachment.triggersfrom Lambda trigger UIDs and Cloud Run event sources.member_offrom parent UID.cross_regionfrom replica pairs. - Modify behaviour
- 94 resource types update live with no interruption. 52 restart. 6 are pools, where child nodes are recreated and the cluster itself is safe. The behaviour comes from the type, so modifying a Lambda and modifying an RDS instance do not get the same warning.
- Risk score
- Impact severity ratio up to 60 points, environment up to 15, ownership spread across teams and schedules up to 20. Zeroed when nothing is impacted.
- Scope
- One hop. ZopNight does not claim multi-hop traversal, does not read VPC flow logs, and does not know how many other targets a load balancer has. Those limits are documented rather than papered over.
Stop guessing at change windows.
Connect a read-only role and the canvas draws itself. No agent, no write access, nothing to install.