Netbox vs. phpIPAM

Netbox is very well suited when you want to consolidate your inventory in one place. Netbox is also very well suited when you want to generate network configurations. You can request the REST API to get the date of a device and generate network configurations with a templating tool, and that is very easy.

Incentivized

phpIPAM is great for a team environment and complex network environments so all members are informed. It's not very user-friendly for administrators to maintain; a IT individual with Linux OS experience is needed in my opinion.

Incentivized

• Device modelling
• Device inventory
• IPAM

Incentivized

• Static IP tracking
• DHCP Pool leases
• Break down networks in different subnets and VLANs
• Device documentation

Incentivized

• The GraphQL implementation could be better integrated
• Netbox is usually very reactive except but performance start to drop when requesting 250 devices or more per page

Incentivized

• Visual aid is limited
• Interface is old and could use a refresh
• Updating the software is difficult

Incentivized

The API is just very well designed. All tools say that what you can do with webUI, you can also do it via the REST API. That is usually not the case except for Netbox, where you can really do everything with the API. For instance with GLPI, you cannot get rack and rack units data with the API, while you can do it via the webUI

Incentivized

• It could integrate very easily in our ecosystem thanks to the API
• It can be used as a tool for conformance purposes

Incentivized

• Software is free so ROI is immediate
• phpIPAM is easy to use and enter information
• Installing phpIPAM is pretty difficult and requires Linux OS knowledge.
• There are minimal requirements to access phpIPAM interface.
• Takes a while to get phpIPAM setup and populated with detailed information.

Incentivized