Solo Inventory
The entry point: active discovery, and the OT asset catalog it builds — running entirely on one technician’s laptop. No server, no site infrastructure, no vulnerability correlation yet.
Finding what’s actually there
Active discovery, limited to the address range the technician gives it — one cell, one subnet — never the customer’s whole network by accident.
Coverage already reaches well beyond Siemens: Rockwell/Allen-Bradley (EtherNet/IP), Schneider Electric and any other Modbus- or OPC UA-speaking PLC are picked up by the same scan.
No admin rights needed
Runs as a normal user account — the technician is rarely a local admin on a customer-owned laptop.
No extra drivers
No special network drivers to install on the scanning machine.
Controlled pace
A quick liveness check runs before any port or protocol probing, one attempt per device, no aggressive retries — and every protocol probe stays strictly read-only. A per-scan device exclusion list lets a technician rule out specific equipment before a scan even starts.
Curated before it counts
Every device found is reviewed and confirmed by hand before it joins the inventory — nothing is added automatically.
The catalog builds itself
Discover
Active scanning finds every device on the network — PLCs, HMIs, switches, gateways — including the ones nobody remembered were still plugged in.
Characterize
Vendor, model, firmware version, protocols and open ports are filled in automatically from what the scan actually sees — not a guess based on a MAC prefix.
Confirm & Catalog
A technician adds only what a scan can’t know — Machine ID, location, criticality, who’s responsible — and saves it to the catalog. Minutes per device, not a spreadsheet afternoon.
A catalog that accumulates, not resets
Recognized across visits
A device already inventoried is matched on a later visit, even if its IP address changed, and compared against what was already known.
“Identical” vs. “changed since last scan”
When something changes — open ports, identification data — the exact fields that changed are listed, instead of the device looking simply “new” again.
Editable & managed
Every asset can be classified — location, criticality, responsible party, device type — and kept current directly in the inventory.
Exposure as its own risk factor
Beyond location and criticality, every device is classified by its network exposure — in plain language, answered by the technician on site, no formal network-architecture knowledge required.
No connection to other networks.
Separated from the IT network by defined controls.
Communicates directly with the corporate network.
Reachable from the public internet.
Every declaration is stamped with author and date, and can never be edited retroactively without leaving a trace — it’s an audit fact, not just a label. It travels with the device if the account later upgrades to Solo Analytics or Site Analytics.
One workstation, several people
Local PIN gate
Name and PIN required before any data or feature becomes accessible — protects a laptop that goes home in a bag every night.
Correct attribution
Every network-exposure declaration and every catalog edit is tied to whoever was actually signed in — never a freely-typed name.
No persistent session
Always asks for credentials on launch — protects a lost or unattended laptop.
Team management
Add a colleague, reset a forgotten PIN, or remove access, all inside the app itself.
Try it, then keep it
Activation is local, tied to the machine the app runs on — no central accounts, no permanent connection to a licensing server required.
Evaluation license
Fully functional, with a cap on inventory size — built to prove the value before committing.
Full license
Removes the device cap, for continued use on a single workstation.
Works with no internet at all
Solo Inventory builds the catalog — it doesn’t yet tell you which of those devices are actually exploitable. That correlation against NVD and CISA KEV, plus a full vulnerability review workflow, is exactly what Solo Analytics adds, on the same workstation.
Questions about getting started? Get in touch.