OpenIPAM

OpenIPAM is an open-source IP address management and configuration-management database (CMDB) tool for keeping network allocations and infrastructure records together. It is a strong fit for homelabs, small businesses, network engineers, and IT departments that can operate a browser tool or host a small backend. The zero-cost model and broad network coverage are compelling, but organizations needing granular permissions or DNS administration should choose another system.

Overview

OpenIPAM combines subnet planning, address allocation, DHCP records, and equipment inventory instead of treating IPAM as a separate spreadsheet from the rest of infrastructure. You can run the browser version from downloaded files, with data retained in that browser's local storage, or deploy the optional Python Flask backend with server-side SQLite for shared use. The first route is convenient for an individual or isolated lab; the second is the sensible choice when several people must work from one dataset.

Server operation adds authenticated routes, SAML 2.0 single sign-on through Microsoft Entra ID, signed eight-hour session cookies, HttpOnly and SameSite=Lax settings, and audit entries attributed to users. That is a useful security baseline for an internal service. It does not replace role-based access control, which is among the project's stated contribution needs.

Key features

Network management covers CIDR subnets, IP ranges, VLANs, assignments, reservations, duplicate-IP conflict detection, and a subnet calculator. Those functions address the practical work of planning ranges and preventing accidental reuse. DHCP tracking includes scopes, leases, reservations, options, and utilization, giving operators a view of both configured addresses and what the service is actually handing out.

The CMDB supports 14 host types, hardware lifecycle tracking, locations, racks, maintenance windows, and company records. This makes OpenIPAM more useful for infrastructure inventory than an address-only utility, particularly where physical placement and asset status matter. CSV host import and JSON backup and restore include DHCP data, helping with initial population and recovery.

With the backend enabled, a REST API supplies CRUD endpoints, cross-entity search, dashboard statistics, and JSON backup or import. Current two-version support is listed for Chrome, Firefox, Safari, and Edge, with WebAssembly and ES6+ required. These requirements suit modern managed browsers but may rule out older locked-down clients.

Pricing

There is no free trial because the product is free, and no paid tier or seat charge is given. The trade-off is operational rather than financial: browser mode favors a single local user, while multi-user access requires running the backend and managing its server-side SQLite data.

Platforms

OpenIPAM supports API, Linux, self-hosted deployment, and web access. The browser build can be opened from downloaded files, while the repository includes a Linux setup script for the optional backend. That combination works for teams comfortable hosting software themselves and for individuals who want to avoid infrastructure entirely.

Who it's for

Choose OpenIPAM for a homelab, a small business, or an IT/network team seeking one free system for IP allocation, DHCP visibility, and asset records. It is less suitable for organizations that require DNS record management, topology visualization, advanced reporting, or role-specific permissions as core workflows.

Pros and cons

Pros

• Broad network scope: Subnets, VLANs, reservations, conflict detection, and DHCP utilization cover everyday address operations.
• Useful inventory depth: Fourteen host types, lifecycle fields, racks, locations, and maintenance windows extend beyond basic IP lists.
• Flexible data location: Local browser storage avoids setup, while server-side SQLite enables shared access.
• Practical portability: CSV import and JSON backup/restore include DHCP information, and the backend exposes a REST API.
• No licensing cost: The sole plan is free and open source.

Cons

• No role-based access control: Teams needing different permissions by job function have a stated gap to work around.
• No DNS management: DNS records are a listed missing area, so address administration is not a complete name-and-address system.
• Self-hosting overhead for collaboration: Multi-user work depends on deploying and maintaining the Flask backend.
• Limited analytical scope: Advanced reporting and topology visualization are identified contribution needs.

Alternatives

BlueKing CMDB is a free, self-hosted and web-capable alternative with a Community Edition, one-click deployment, automated operations, and community documentation; choose it when CMDB deployment support matters more than OpenIPAM's focused IPAM/DHCP combination.

CMDBuild is another free AGPL self-hosted option; pick it when you want a broader configurable CMDB foundation and accept that its listed plan excludes data models, workflows, reports, and dashboards.

dust is a free command-line disk-usage tool, so it is relevant only for filesystem space analysis rather than IPAM or CMDB work.

iTop offers a free Community on-premise edition and paid operational service-management options; choose it when change and service management are priorities.

Ralph is free, Apache 2.0 open source, and self-hosted; consider it when you want a similarly deployable CMDB alternative.

teemIP provides a free Community edition with open-source distribution and community support; choose it when a dedicated IPAM-oriented alternative is preferable.

GLPI combines a free option with paid cloud service and broad platform support; pick it when you need an IT-service platform with hosted purchasing choices.

Hornbill IT Asset Management is a paid product with personalized pricing; consider it when you want commercially tailored packages instead of a free open-source deployment.

Verdict

OpenIPAM is a sensible recommendation for teams that want free, self-controlled IPAM, DHCP tracking, and CMDB inventory in one tool, especially in homelabs and smaller environments. Its browser mode lowers the barrier to trying it, and its backend adds shared access, SSO, API functions, and recoverable data. Look elsewhere if role-based permissions, DNS records, topology views, or mature reporting are requirements rather than future enhancements.