A guided path from "what can Zaryn do for my network?" to safe, automatically checked changes: a read-only collector, config backups and drift, the live map, why A can't reach B, a digital twin that tests a change first, rollouts that undo themselves, and device access without shared passwords. Pictures first, every step explained.
See your routers and switches live. Every config backed up and checked against the approved one, a map of how devices connect, and an address plan with its conflicts. Cisco, Huawei, MikroTik, FRRouting and VyOS.
Why can't A reach B? Zaryn follows the traffic hop by hop through your devices' routes, ACLs and firewalls, names the device and the rule that stops it, and gives the fix in that device's commands. Probes check what matters every minute.
See what a config change would do to your network before anyone types it. Which traffic stops, starts or takes another way and why, every routing table entry that changes, and the single points of failure it creates. On the site page, from the command line, and on every pull request.
Make a config change on the devices themselves, checked on the live network and taken back by itself when the network doesn't hold. The exact commands both ways, the twin's verdict, approval with four eyes, waves with a canary, MikroTik safe mode and a dead man's switch on the device, every command and answer kept.
Give an engineer a terminal on a router or switch for a limited time, through the site's collector. They never see the device's password, every session is approved, ends by itself and is recorded keystroke by keystroke, and an admin can end it at any moment.
NetFlow, IPFIX and sFlow from your routers and switches, IPv4 and IPv6, turned into dependencies between named VMs, devices and hosts: which services each one uses, and what moves or fails together.