Open Network Diagram
github.com
- Free plan
- Web
- API
- Self-hosted
What Open Network Diagram is
Open Network Diagram is a free, self-hosted tool for mapping home lab and network infrastructure. Its network, Hosts & VMs, and rack views help organize devices, virtual machines, services, and rack placement. Users can declare subnets and VLANs, track cable type, colour, and length, and expand VM lists by machine. The IPAM panel shows subnet utilisation, detects duplicate IP addresses, and suggests the next available address. Infrastructure information is represented in JSON, which can be backed up, reused, and optionally versioned after reviewing it for sensitive information. Self-hosted deployments autosave changes, persist writes atomically, and keep the five latest rolling backups. Deployment is Docker-first, with writable volumes and Docker Compose support; the runtime exposes GET and PUT operations at /api/network-data. Published Docker images support AMD64 and 64-bit ARM, including Raspberry Pi systems. Licensed under GNU GPL v3, it has no runtime dependency on external APIs. It does not include authentication or TLS, and topology details may expose sensitive infrastructure information.
Who it suits
Open Network Diagram suits home lab users who need to map machines, virtual machines, devices, and rack placement. It is a better fit for environments where access can be restricted or protected by an authenticated TLS-terminating reverse proxy.
Good to know, and what to watch
- Provides network, Hosts & VMs, and rack views.
- IPAM detects duplicate IPs and suggests an available address.
- Self-hosted mode keeps five rolling backups.
- Docker Compose and writable data volumes are supported.
- Docker images support AMD64 and 64-bit ARM.
- No authentication or TLS is included.
- Topology data may expose sensitive infrastructure details.
- Read-only mode does not hide configured topology.
Plans
Every plan and priceOpen Network Diagram
Free plan
Getting started
- Open the project repository
- Deploy the Docker image or use Docker Compose
- Provide a writable data volume for persistent JSON data
- Configure networks, hosts, virtual machines, racks, subnets, and cables
- Restrict access with a firewall, LAN, VPN, or authenticated TLS-terminating reverse proxy
- Set NETWORK_READ_ONLY=true for a public read-only demonstration
Limits to check
The project has no built-in authentication or TLS. NETWORK_READ_ONLY=true disables changes but does not conceal a configured topology or add authentication.
The Club's review
Open Network Diagram is a free, self-hosted system for turning a home lab’s topology and equipment inventory into a maintained operational record. It is most appropriate for technically confident individuals who can run Docker and control network access. The strongest case is its structured, reusable model; the biggest concern is that securing the deployment is entirely your responsibility.
Overview
This GNU GPL v3 project combines a visual editor with a JSON source of truth. The same data can be backed up, reused and optionally versioned, so the diagram is not trapped in a one-off drawing. That approach suits a lab where hosts, virtual machines, devices and rack positions change frequently and the documentation needs to keep pace.
Its scope is deliberately practical rather than enterprise-wide: topology, inventory, cabling and basic IP address management are covered in one self-hosted application. There is no runtime dependency on external APIs, and the icon catalogue is bundled locally, which helps an offline or tightly controlled environment. Sensitive topology data can include host names, addresses and MAC addresses, so deployment boundaries matter.
Key features
The network view records connections with Ethernet labels and supports declared subnets and VLANs. Hosts & VMs adds inventory and service context, with expandable virtual-machine lists for each machine. Rack view goes beyond a simple rack picture: managed racks hold U positions and equipment heights, shelf items can sit side by side, and items link through to the editor. This makes the product useful when physical placement matters as much as logical relationships.
Its IPAM panel reports utilisation for each subnet, identifies duplicate IP addresses and suggests the next free address. Those are valuable safeguards for a small network, although the feature should be viewed as focused address bookkeeping rather than a replacement for a larger network-management suite. Cable records capture type, colour and length; colour-coded links and hover details make the physical path easier to interpret.
Self-hosted edits autosave to JSON, write atomically and retain the last five rolling backup files. Docker Compose, writable data volumes and images for AMD64 and 64-bit ARM—including Raspberry Pi systems—give administrators several sensible deployment patterns. The runtime exposes GET and PUT operations at /api/network-data, useful for controlled automation around the same source of truth.
Security is the hard limit. There is no built-in authentication or TLS, and a writable instance should not be placed directly on the public internet. A firewall, LAN or VPN boundary, or an authenticated reverse proxy that terminates TLS is therefore part of a responsible deployment. Setting NETWORK_READ_ONLY=true is suitable for a public demonstration because it disables changes, but it neither conceals the topology nor authenticates viewers.
Pricing
Open Network Diagram costs nothing under its single “Open Network Diagram” plan. The plan is self-hosted, Docker-based and distributed under GNU GPL v3, with no seat, device or usage quota stated. That makes it a natural fit for a personal lab or a small engineering environment that already owns its hosting and can manage security. The trade-off is operational: hosting, backups beyond the rolling five and access control remain your responsibilities.
Platforms
The published platform coverage is API, self-hosted and web. Docker images support AMD64 and 64-bit ARM, including Raspberry Pi, while Docker Compose and writable volumes support conventional server or lab deployments.
Who it's for
Choose it if you run a home lab and want one maintained map for machines, VMs, network links, IP addresses, cables and rack locations, with the underlying record available as JSON. It also suits operators who prefer local, offline-friendly tooling and are comfortable placing an authenticated proxy or network boundary in front of an application.
It is a poor fit for an internet-facing service that must provide user login and encrypted transport itself, or for organisations seeking a broad, centrally governed infrastructure-management platform. The missing security layer is not a minor convenience gap when topology data is sensitive.
Pros and cons
Pros
- Structured documentation: JSON remains a reusable source of truth rather than a static exported image.
- Broad lab context: network, Hosts & VMs and rack views connect logical topology with inventory and physical placement.
- Useful small-network IPAM: utilisation, duplicate detection and next-free-IP suggestions address common lab mistakes.
- Resilient local storage: atomic persistence, autosave and five rolling backups reduce the risk of losing edits.
- Flexible hardware target: AMD64 and 64-bit ARM images include Raspberry Pi deployments.
Cons
- No authentication or TLS: access control and encrypted delivery require your firewall, VPN or reverse proxy.
- Read-only is not private: demonstration mode blocks edits but still exposes configured topology to viewers.
- Focused scope: the product documents infrastructure and basic IPAM but is not a full infrastructure-management platform.
- Self-hosting overhead: you operate the container, protect sensitive JSON and provide any additional backup or availability measures.
Alternatives
Scanopy is the better choice when you want a freemium product with a hosted-platform path, broader desktop and server coverage, or a defined starter plan; its Community Edition is free for one network and one user seat when self-hosted.
GestióIP is preferable when dedicated IPAM is the priority: its free standard package is free, with a configuration-management module priced at $400 a year for up to 50 devices.
LOGINventory suits teams wanting a device-inventory product with a stated cap: its Forever-Free plan is free for up to 20 devices with no time limit.
Obelinf is an option for a small managed team needing explicit workspace limits; its Personal plan is free for one user, one organisation, one site, four racks and 30 devices.
Nautobot is worth considering for an open-source, self-managed platform aimed at exploring workflows and limited production deployments.
Danbyte offers a free, open-source self-hosted alternative with all features included and no seat licence or expiry.
Hudu is the paid route for teams that want a commercial documentation platform; its Hudu plan is $30 a month with no user minimums.
ITFlow is another free, open-source self-hosted option, with hosting and sponsor support sold separately.
For a wider set of network-documentation tools, browse the Network Documentation Software directory.
Verdict
Open Network Diagram is a strong pick for a home-lab operator who wants detailed topology, inventory, rack and basic IPAM data in a portable JSON-backed application, especially on Docker or a Raspberry Pi. Choose it for that focused control and zero licence cost; look elsewhere if built-in authentication, TLS or a more expansive infrastructure-management platform is non-negotiable.
The verdict
Open Network Diagram brings infrastructure maps, inventory, and basic IPAM into a self-hosted Docker-first tool. Its lack of built-in authentication and TLS makes access restrictions important before deployment.
Questions people ask
Is Open Network Diagram free?
Yes. The plan costs nothing and is self-hosted with Docker deployment under GNU GPL v3.
Which platforms are supported?
It is available as self-hosted software, a web product, and an API. Published Docker images support AMD64 and 64-bit ARM, including Raspberry Pi systems.
Does it require external APIs?
No. The runtime has no dependency on external APIs and includes a locally vendored icon catalogue.
Does it provide authentication or TLS?
No. Documentation recommends restricting access or using an authenticated reverse proxy that terminates TLS.
How is topology data stored?
JSON is the source of truth. Self-hosted mode autosaves changes and keeps the last five rolling backups.
What the maker publishes
- API
- The runtime exposes GET and PUT operations at /api/network-data. source
- API
- The documented runtime API endpoint is GET/PUT /api/network-data. source
- Audience
- The project is positioned for home lab users who need an up-to-date map of machines, virtual machines, devices and rack placement. source
- Cabling
- Connections can track cable type, colour and length with colour-coded links and hover details. source
- Data model
- The application keeps a JSON source of truth that can be backed up, reused and optionally versioned. source
- Deployment
- The project is Docker-first and supports writable data volumes plus Docker Compose deployment. source
- Deployment
- The project provides Docker and Docker Compose deployment instructions with writable data volume support. source
- Integrations
- The tool has no runtime dependency on external APIs and includes a locally vendored icon catalogue for offline-friendly operation. source
- Integrations
- The project says it has no runtime dependency on external APIs and includes a locally vendored icon catalog for offline-friendly behavior. source
- IPAM
- The IPAM panel shows per-subnet utilisation, detects duplicate IPs and suggests the next free IP. source
- IPAM
- The IPAM panel shows per-subnet utilization, detects duplicate IP conflicts, and suggests the next free IP when adding machines, devices, or VMs. source
- JSON source of truth
- The app documents infrastructure in a visual UI while keeping a JSON source of truth that users can back up, reuse, and optionally version after reviewing for sensitive information. source
- License
- The repository is licensed under GNU GPL v3. source
- License
- The repository identifies the software as GNU GPL v3 licensed. source
- Network and host views
- It provides a network view with Ethernet labels and a Hosts & VMs view for inventory and service mapping. source
- Persistence
- Self-hosted mode autosaves JSON data and keeps the last five rolling backups. source
- Persistence and backups
- In self-hosted mode, changes autosave to JSON, writes are persisted atomically, and rolling backups retain the last five files. source
- Platforms
- Published Docker images support AMD64 and 64-bit ARM, including Raspberry Pi systems. source
- Purpose
- Open Network Diagram is a declarative, self-hosted containerised tool for visualising and managing home lab and network architecture diagrams. source
- Purpose
- Open Network Diagram is a declarative, self-hosted tool for visualising and managing home lab and network architecture diagrams. source
- Rack inventory
- Rack view supports managed racks with U positions and heights, side-by-side shelf items, and click-through to the editor. source
- Read-only mode
- NETWORK_READ_ONLY=true disables changes for public demonstrations but does not hide a configured topology or provide authentication. source
- Read-only mode
- Optional read-only mode prevents changes and is offered for public demonstrations and sharing. source
- Security
- Open Network Diagram does not include authentication or TLS. source
Checked against the maker's pages on 2 Oct 2026.