NacTrack
FRGet the demo
For network teams

See every command we run on your devices

Read only SSH, no agent, no configuration change. Here is the command list, the access it needs, and where each platform falls short.

The vendor matrixOpen the demo
On your devices

What this does on your devices

One read only SSH session, with the credentials you provide. No configuration command is pushed.

The commands run are the platform's: what one command shows on IOS is read differently on VRP, and differently again on Junos or AOS-CX. Raw output is kept as it came, alongside the parsed fields.

No agent, no probe, no traffic mirror, no reboot, no change window. The data plane is untouched.

  • Read only, your credentials
  • Raw output kept, not only the parsed fields
  • Nothing installed on the devices
  • Works on old hardware
  • Scheduled or on demand collection
Check for yourself

Four ways to catch us out

The coverage matrix

The empty cells are published like the rest. Find your platform and look at what is marked no.

›

The demonstration account

A one minute form, a read only account by email, on a fictional estate of fifty eight devices. Then you click everywhere.

›

The how to guides

Every question handled screen by screen, with screenshots and video. Including the limits of each view.

›

What the product cannot do

Between two collections, nothing is observed. NacTrack says what the network is, not whether a device is answering right now or how loaded it is. Real time monitoring stays necessary, and the trade off is written down here rather than left to be discovered.

›
What changes

What you get, ticket by ticket

  • The port behind a MAC address: one search, instead of a tour of sessions.
  • The path of a VLAN between two sites: one query against the collected topology.
  • The devices running a given software version: one sortable column.
  • What changed in a configuration since the last collection: a dated diff.
  • A defensible replacement plan, rather than an estimate, when management asks for a budget.
  • The devices missing from every list, surfaced by the discovery crawl. Rarely the newest ones.
  • The raw output of every command stays readable, so you can check what the parser made of it.
On the screen

The same questions, screen by screen

All seven lines above, taken in the application on a fictional estate of fifty eight devices.

app.nactrack.com/troubleshooting/macfinder
MAC address search: the ports and the devices that see it
A MAC address. One address entered, fourteen occurrences. The port, the VLAN, the VRF and the age on every device that sees it, MAC table and ARP table told apart. What this screen replaces is a tour of SSH sessions.
app.nactrack.com/neighbors/topology/multi
The topology canvas: the estate's CDP and LLDP adjacencies
The collected topology. The adjacencies the devices declare themselves, not a hand drawn diagram. The path of a VLAN between two sites is read off these links: the VLAN layer is one of the filters on the left, and path analysis works on the same data.
app.nactrack.com/devices
The device list, with the software version column
A software version. Fifty eight devices, several vendors mixed together, one Software column that sorts and filters. Knowing which devices run a given version is a sort, and the EOL column beside it already says which ones will get no more fixes.
app.nactrack.com/diff/config
Two collections compared: the configurations that changed
What changed. Two successive collections compared, on 31 July 2026: four switches whose configuration moved, with the severity of the change and the count of lines added, removed and modified.
app.nactrack.com/discovery/runs/demo-discovery-20260801-210507
The result of a discovery sweep, grouped by subnet
What the lists are missing. A sweep of 10.250.0.0/16 in fourteen seconds, fifty eight nodes grouped by subnet. The legend separates reachable, unreachable, auth failed, unrecognised and no address, and three nodes carry only an IP with failed or timed_out beside it: those are the ones no list names.
app.nactrack.com/eol
Hardware lifecycle: the models past end of sale and end of support
The replacement plan. Twenty seven models, sixteen devices already past support, each one named and attached to its model with the end date and the announced successor. This table is what a budget request puts up against an estimate.
The raw output of one command, opened beside the matching lines
The raw output. One search crosses the configurations of all fifty eight devices, and the command output opens exactly as it was collected, matches highlighted. That is what lets you check what the parser made of a line instead of taking its word for it.

Take the demo for yourself

Read only, on a fictional estate. The account is requested through a form and arrives by email. Look for your platforms in the matrix, then go and see whether the product holds up to it.

Request the accountThe coverage matrix