ITFlow vs Open Network Diagram

ITFlow is a free, open-source platform for client IT documentation, ticketing, and billing, aimed at small managed service providers. It stores client details such as contacts, locations, vendors, computer assets, software licences, domains, and documents. Teams can create, prioritize, and track support tickets. Billing tools include recurring invoices, quotes, automated reminders, and client payments through Stripe. Other listed modules cover accounting, bulk email, calendars, lead management, a client portal, and a password manager. The version 1 API includes modules such as assets, clients, contacts, credentials, documents, invoices, and tickets, although some operations are partial or unavailable. Documentation lists Ollama, OpenAI, and LocalAI integrations for ticket rewording and summaries. Login passwords are encrypted at rest using AES 128-bit encryption, and the documentation advises backing up the master key. ITFlow is self-hosted: Debian is the recommended installation method, with manual Debian, HestiaCP, and community-supported Docker options also documented. Windows installation is unsupported. Hosting and sponsor support are paid services.

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.