Free tool · Kris McCabe
Map how your systems actually depend on each other, then let a topological sort — grounded in standard graph theory, TOGAF data architecture, and NIST SP 800-34 contingency planning — tell you the one recovery order that doesn't create a hazard.
Start from a preset architecture or a blank canvas, then add systems and the dependencies between them.
Source feeds Target — Target cannot be trusted until Source is restored.
CSV, one system or dependency per line:
NODE,name,tier(0-3),interfaceType,hours
EDGE,fromName,toName
Or paste a JSON object:
{"nodes":[{"name":"","tier":0,"interfaceType":"REST API","hours":1}],"edges":[{"from":"","to":""}]}
Scroll to zoom, drag to pan, click a system for its blast radius below.
A topological sort of the dependency graph, grouped into the four standard recovery phases — the order within each phase already respects every dependency, not just the tier label. "Wave" is that calculated order: everything in Wave 1 has no prerequisites, Wave 2 depends only on Wave 1, and so on — restore in wave order and nothing gets started before what it needs.
Click any system in the map above to see what it depends on, and what depends on it.
Send the dependency-chain recovery time for the selected system straight to Redline, or take the whole map with you.