Packetman saysPacketman here. The usual way to inventory a fleet is to stand up a server and have it interrogate every device over the network, again and again. We turn it around. Each machine already knows exactly what it is: the CPU and its security features, every memory module, every drive, the graphics adapter and its driver, the network cards, the firmware, the installed software. It reports that once a day, and only if something changed. The center just rolls it up.Large organizations run inventory servers that reach out and interrogate every device on the network, over and over. DataStun does the reverse. Each enrolled machine already knows exactly what it is and inventories itself — hardware, firmware, drivers, software, security posture — then reports up once a day, and only when something changed. The center rolls it up so a question about a component becomes a query, not a project.
The same agent that watches the network reads the machine it lives on. No inventory agent, no scanning server, no credentials for a central box to hold.
Manufacturer, model, SKU, serial number, system UUID, chassis type, and the firmware vendor, version, and date — the keys asset systems actually match on.
Model and core count, current and rated frequency, power governor, side-channel mitigation status, and the instruction-set features that matter for security and performance — hardware encryption, virtualization, vector extensions.
Each slot: size, type, manufacturer, part number, and the speed it is actually running at against the speed it is rated for.
Every drive: class (NVMe, SATA SSD, hard disk, virtual, removable), capacity, model, serial, firmware revision, and the link speed and width it trained at.
Each graphics adapter with vendor, model, driver version and date, and memory; each network card with addresses and its link state — so a 10 Gb card trained at a fraction of its lanes shows up as a finding, not a mystery.
Installed software, attached USB devices, and the security posture: disk encryption, host firewall, TPM, Secure Boot, antivirus real-time state, local administrators, pending updates, reboot pending.
Illustrative excerpt. The real snapshot lives on each device’s Host tab and in the fleet rollup.
The center does what only the center can: put every self-inventory side by side.
Agents reporting, operating-system split, the security-posture rollup (encryption, firewall, Secure Boot, TPM), machines needing a reboot or updates, the most common processor models and memory sizes, and a per-machine table with snapshot age — stale snapshots flag themselves.
The whole rollup is also available as a JSON export, so a bad memory part number, a graphics driver version with a known problem, or a network card trained at the wrong width becomes a query across the fleet instead of a week of desk visits.
The fleet software bill of materials lists every distinct program observed, with version, signer, and what share of the fleet runs it; the patch-lag view shows which machines are still on an old version of a common product. Business tier and above.
Distributed collection, central reporting: the same shape as everything else DataStun does. How it works →
Sign up free, enroll one agent, and its Host tab fills in on the first heartbeat; the full inventory snapshot follows within 24 hours. Every tier.