INSPECTOR / PRO

Desktop topology design / Inspector-Pro

Design the topology.
Inspect the record.

Put devices, links and their properties on one canvas. Build a topology you can read, edit and check before the next step.

01 / Edit the design record

Your topology, made explicit.

Arrange devices, inspect properties and connect interfaces. Download the applied preview data to see the underlying record.

Topology editor bench

Browser sample / no network launched

Edit local preview data. Checks cover native topology structure only; no IP, routing, reachability, image existence or deployment check is made. No app backend is contacted.

Select a device to edit. Drag to arrange, or use arrow keys on a focused device.

3 devices / 2 linksLocal sample data

Device record

Select a device

Selected device properties

Structure findings

Sample ready. Select Check structure to inspect the record.

    Preview data downloads

    Browser-generated files only. Export uses applied edits. These files do not launch a network or prove a native app save/export journey.

    02 / Explain the policy

    Same attempt. Different boundary.

    Simulated browser sample

    This deterministic illustration shows an attacker attempting to reach a service through a router/firewall boundary. Apply a deny rule, then replay the same attempt to inspect the changed result. All events are local sample data; no network action occurs.

    Current policy: allow untrusted access
    FLOW / ILLUSTRATIONAwaiting playback
    Simulated browser sample: attacker, boundary and serviceNo attempt played yet. The topology connects an attacker to a router/firewall boundary and then a service.ATTACKERUntrusted sampleROUTER / FIREWALLPolicy boundarySERVICEProtected sampleATTEMPT → POLICY DECISION → RESULT

    Amber = attempted / allowed · Mint + stop marker = blocked. Scroll the diagram on narrow screens.

    Before / weak policy

    Untrusted access is allowed at the boundary. In this sample, the attempt reaches the service.

    After / deny rule

    Apply the deny rule and replay to collect the changed result.

    Evidence / ordered events

    Playback record

    Ready. Play the weak-policy sample, then apply the deny rule and replay.

      This scenario explains a fixed policy outcome. It does not validate the editor topology, execute commands, contact a service or prove native lab behaviour. The editor and scenario have independent local state.

      Next / desktop application

      Platform installers
      are in preparation.

      Planned platforms: macOS, Windows, and Linux. Installers are in preparation; no installer download is available here.

      The browser editor exports preview data files only. A structural pass does not establish reachability, deployment readiness or runtime safety.

      Return to the Inspector hub →