Open-Source IPAM Options

Four open-source options, what each is actually for, and what you sign up for by running them yourself.

The options

What each one is for

NetBox is a source of truth for infrastructure, of which addressing is one part. Its value is that other systems read from it: configuration generation, provisioning, monitoring inventory, firewall rule generation. If nothing reads from your NetBox, you are running a large application to do a small job.

It does not discover anything. That is deliberate — the database describes what the network is supposed to be, and drift is found by comparing reality against it rather than by overwriting intent with whatever a scan found. Populating it for an existing undocumented estate is a project. Quickstart.

phpIPAM answers “what is out there and what is free”. Scanning populates it without a data-entry exercise, the interface is direct, and it runs on a modest LAMP stack. It models addresses rather than infrastructure, so it will not become your inventory system, but for address management specifically it does the job with less setup than anything else here. Quickstart.

NIPAP does address management and stops. The CLI is fast enough to use during an incident, the data model is clean, and there is no surface area you are not using. Choose it when the alternative is a platform where you will touch one module in ten.

GestioIP covers addresses and VLANs with SNMP discovery. Smaller community than the others, which matters mainly for how quickly you find answers when something breaks.

Feature-level comparison including commercial products is in the tools reference.

What self-hosting commits you to

The licence is free. These are not.

Upgrades. NetBox in particular moves quickly, with breaking changes across major versions and a database migration each time. Falling behind is easy and catching up is worse than staying current. Budget a maintenance window per quarter and treat skipping it as accruing debt.

Backups you have tested. The database is the asset. An untested backup of the system that tells you which addresses are in use is worth discovering during a restore, not during an outage.

Availability. Once provisioning reads from IPAM, IPAM is in the critical path. Deciding whether that justifies redundancy is a real question and the answer is not automatically yes — but it should be answered before the first outage rather than after.

Integration. Nothing works with your existing systems until you make it. The API is the enabling piece, not the finished product, and this is where most of the engineering time goes.

No escalation path. When it breaks at an inconvenient hour, you debug it. Community support is good on all four projects and it is not a support contract with a response time.

None of these is a reason to avoid open source. They are the reason the comparison against a commercial product is not “free versus expensive” — it is engineering time versus licence cost, and which is cheaper depends on how much of the former you have.

Choosing

Three questions decide it in most cases.

Will something read from it automatically? If yes, NetBox, because the API and data model are built for that. If no, a lighter tool will serve you better and you will actually keep it current.

Do you know what is deployed? If no, pick something that scans — phpIPAM or GestioIP — so you are not starting with a manual audit.

Do you need infrastructure modelling or just addresses? Devices, circuits, and VLANs alongside addresses point to NetBox. Addresses alone point to NIPAP or phpIPAM.

Related

• IPAM tools reference — including commercial DDI platforms
• NetBox quickstart — running NetBox with Docker
• phpIPAM quickstart — running phpIPAM with Docker
• IPAM best practices — practices independent of the tool