NetBox for the homelab: when your IP spreadsheet finally needs a real tool

For two years my homelab’s IP address allocation lived in a Google Sheet. A column for VLAN, a column for IP, a column for hostname, a column for “what is this thing.” It worked because there were 15 services. When the count crossed 35-40 — somewhere in mid-2025 — the spreadsheet stopped being useful and became a liability. Half-correct data, conflicting allocations, IPs that supposedly belonged to services that had been decommissioned 6 months earlier.

Christian Lempa’s December 10 NetBox tutorial was the nudge that finally moved me to a real tool. His framing: “In this video, I show you how to manage your network infrastructure like a pro using NetBox - the ultimate IP Address and Data Center Infrastructure Management platform… If you’re tired of tracking your HomeLab or IT infrastructure in spreadsheets and want a centralized, professional solution that integrates with your automation tools, this is the video for you!”

This piece is the working-engineer write-up after three weeks of migrating from spreadsheet-tracking to NetBox in a homelab context — what NetBox is good for, what it’s overkill for, and the migration patterns that worked.

What NetBox is

NetBox is an open-source IPAM (IP Address Management) and DCIM (Data Center Infrastructure Management) platform originally developed by DigitalOcean for managing their own network. It’s been open-sourced for years and has grown into the canonical “you have outgrown your spreadsheet” tool for network operators.

What NetBox tracks:

• IP addresses and ranges. With hierarchy (RIRs, aggregates, prefixes, IP ranges, IP addresses). Knows which addresses are allocated, which are free, which are reserved.
• Sites, locations, racks, devices. Physical inventory tracking with hierarchical structure.
• Manufacturers and device types. A library of device models so you don’t have to redefine “Mikrotik CRS328-24P-4S+” every time you add one.
• Virtual machines and clusters. Tracks VMs separately from physical devices.
• Cables, circuits, and connections. For users who care about cable management documentation.
• Tags, custom fields, custom links. Extensibility for use-case-specific tracking.

What NetBox is not:

• Not a network monitoring tool (use Prometheus, Zabbix, or LibreNMS for that)
• Not a configuration management tool (use Ansible / Terraform for that)
• Not an alerting platform (use Alertmanager / similar)
• Not a deployment tool

NetBox’s role is single source of truth for “what is on my network and where.” Other tools consume its data via API; nothing else owns it.

When the homelab actually needs NetBox

The threshold question: when does a homelab cross from “spreadsheet works” to “needs NetBox”?

The honest answer, after the migration:

Spreadsheet is fine when:

• Under ~15-20 services
• One or two VLANs
• One physical location
• Single user maintaining the doc
• Network rarely changes (low add/remove churn)

NetBox starts paying off when:

• 25+ services
• Multiple VLANs with deliberate IP ranges
• Tracking physical hardware (rack positions, device models)
• More than one person needs to look at the data
• Frequent changes (new services, IP reassignments, hardware swaps)

For most homelab enthusiasts, the threshold lands somewhere around year 2-3 of serious homelab investment, often when the count of “things with an IP” crosses 30 and the cost of “what is that IP?” becomes painful.

What Christian Lempa’s tutorial actually covers

Lempa’s December 10 video is a clean introduction. The structure (paraphrased from his described chapters):

1. Deploy NetBox in Docker using his boilerplates tool — typical Lempa pattern of “here’s the Docker Compose, run this.”
2. Create sites and racks — set up the physical inventory hierarchy.
3. Add devices and manufacturers — populate the device library.
4. Set up VM clusters — track virtual machines separately.
5. Organize IP addresses with IPAM — the core IP tracking feature.
6. Automate everything with Terraform — using NetBox’s API to drive infrastructure provisioning.

The tutorial covers maybe 30% of NetBox’s surface area, which is the right 30% for homelab users. NetBox has enterprise features (multi-tenancy, complex circuit modeling, cable tracing) that don’t matter for a homelab. The video correctly focuses on the homelab-relevant parts.

What the migration actually looked like

My homelab pre-NetBox:

• ~45 services across 2 physical hosts + 1 ARM NAS
• 3 VLANs (trusted, IoT, DMZ)
• IP allocations across 192.168.x.x ranges
• Google Sheet with 50+ rows including some stale entries

The migration over three weeks:

Week 1: Setup and basic data entry.

• Docker Compose deploy of NetBox following Lempa’s pattern
• Created sites, racks, manufacturers, device types matching my actual hardware
• Entered physical devices (NAS, mini-PCs, switches, AP)
• Set up IP address aggregates and prefixes for my IPv4 ranges

Week 2: Migrate the IP allocations.

• Went service-by-service from the spreadsheet
• Created VMs and assigned IPs in NetBox
• Discovered ~15% of spreadsheet entries were stale or wrong — services no longer running, IPs reassigned that weren’t updated in the sheet
• Resolved discrepancies as I went

Week 3: Automation integration.

• Connected my Terraform setup to NetBox via the provider
• Set up a workflow: when I create a new VM, Terraform queries NetBox for next available IP, allocates it, provisions VM
• Removed the spreadsheet entirely

The honest assessment after three weeks: NetBox does what the spreadsheet was failing at, and the Terraform integration is more valuable than I expected. The cost was ~6 hours total of setup and data migration. The ongoing maintenance is roughly the same as the spreadsheet was, but the data integrity is now actually trustworthy.

What r/selfhosted is saying about NetBox specifically

The NetBox-specific Reddit threads are sparse — it’s a stable, mature tool without much drama. The broader pattern is more visible in adjacent threads.

The 162-upvote December r/selfhosted “Rackula: a Drag and drop rack visualizer” thread captures the broader homelab visualization need. NetBox has rack visualization built in; Rackula is a lighter-weight alternative for users who don’t need the full IPAM. Both reflect the same underlying community pattern: spreadsheets stopped scaling, tools are emerging to fill the gap.

The 1554-upvote November “Selfhosting is not a hobby anymore” thread captures the deeper cultural shift. When self-hosting goes from hobby-grade to “I depend on this for my small business,” the tooling around documentation and tracking goes from “nice to have” to mandatory. NetBox is one of the load-bearing tools for that maturation arc.

What the alternatives are

NetBox isn’t the only option. The relevant tier of tools:

NetBox (the one Lempa covered):

• Mature, feature-rich, mid-heavy
• Docker deploy is straightforward
• Best when you need IPAM + DCIM + automation API
• Overkill for “I just want a rack diagram”

Rackula (the December tool):

• Drag-and-drop rack visualization
• Lighter weight, less feature surface
• Best for users who specifically want a rack diagram and don’t need full IPAM

phpIPAM:

• IPAM-focused (no DCIM)
• Long-standing in the network engineer community
• Lighter than NetBox but less integrated

NetBox Cloud (managed):

• NetBox as a hosted SaaS
• Useful for users who don’t want to self-host the IPAM tool
• Costs money; usually not the right choice for a homelab

Stay on a spreadsheet:

• Fine for 15-or-fewer-service homelabs
• Not fine at 30+

For most homelab users at the right scale, NetBox is the working answer. Below that scale, the spreadsheet is fine. Above NetBox’s complexity ceiling, you’re operating at enterprise tier and have different problems.

What YouTube creators usually skip

Lempa’s video is among the better introductions, but YouTube tutorials on tools like NetBox consistently skip:

• The migration story. “Set up NetBox” is straightforward. “Migrate your existing spreadsheet to NetBox without breaking your homelab” is the harder problem. The video covers the former; you have to figure out the latter.
• The data quality reality. Most engineers’ pre-NetBox tracking has 10-20% stale data. The migration surfaces this. YouTube tutorials gloss over this; the migration is when you actually clean up.
• Operational discipline post-migration. NetBox is only useful if you keep it updated. The discipline of “update NetBox before you provision the VM” has to be enforced. Tutorials usually skip the discipline question.
• When NOT to use NetBox. Homelab users with 10 services don’t need NetBox. The tutorials don’t really say this; they assume if you’re watching, you need the tool.

The verdict

If your homelab has crossed 25-30 services and you’re feeling the IP-tracking pain, NetBox is the right tool for the next stage of homelab maturity. The migration cost is real (6-10 hours of setup and data entry). The payoff is durable: trustworthy single source of truth, API-driven automation possibilities, real documentation that doesn’t drift.

If your homelab is smaller, NetBox is overkill. Stay on the spreadsheet. Revisit when the count crosses the threshold.

The broader pattern: homelab tooling is maturing in 2025 in ways that mirror the maturation of small-team production infrastructure. NetBox, n8n, Pangolin, the various dashboard tools — these are the same tools small SaaS teams use. The homelab community has stopped being “people running random services on a Pi” and become “people running production-grade self-hosted infrastructure with the appropriate tools.” NetBox is one of the canonical examples of this shift.

For working homelabbers in December 2025: if you’ve been on a spreadsheet for more than a year and your service count has tripled, set aside a weekend in January to migrate to NetBox. The cost is short-term; the value is sustained. Lempa’s tutorial is the right starting point. The official docs cover the rest.