LOGINventory vs Open Network Diagram

LOGINventory discovers and documents hardware, software, configurations, and permissions across IT networks. Its core discovery is agentless, using WMI/RPC, SNMP, or SSH; an Offline Agent can cover Windows, Linux, and macOS devices outside the local network. Coverage includes Windows, Linux/Unix, macOS, SNMP devices, hypervisors, Microsoft cloud services, AWS virtual machines, and Exchange. The maker says the product can capture up to 1,117 individual values per Windows device by default. The Inventory Edition covers network inventory; the SAM Edition adds license management, software usage measurement, target-versus-actual comparisons, and compliance reports. It runs on the customer's infrastructure and stores inventory data in a local SQL database; the maker says inventory data is not transmitted to it. The optional LIA assistant sends requests through Azure OpenAI with automatic anonymization and can be disabled. The server requires Windows 10/11 or Windows Server 2016–2025 (x64) and SQL Server 2012 SP4 or later. Pricing includes a free plan, Inventory360 at €6.50 per year, and a 30-day trial; listed prices exclude VAT.

Open Network Diagram is a free, self-hosted tool for visualizing and managing home lab and network architecture. It provides network, Hosts & VMs, and rack views for mapping topology and inventory, including subnets, VLANs, virtual machines and rack positions. Connections can record cable type, colour and length. Its IPAM panel reports subnet utilization, detects duplicate addresses and suggests the next free IP. The application keeps JSON as its source of truth; self-hosted changes autosave, writes are persisted atomically, and rolling backups retain the last five files. Deployment is Docker-first, with writable data volumes and Docker Compose support. The runtime exposes GET and PUT operations at /api/network-data, and published Docker images support AMD64 and 64-bit ARM, including Raspberry Pi systems. The project is licensed under GNU GPL v3 and has no runtime dependency on external APIs. It does not include authentication or TLS. The project warns that topology details may expose sensitive infrastructure information and advises restricting access or using an authenticated TLS-terminating reverse proxy.