This Tool Treats Your Home Lab Like

Look, we need to talk about that one time you changed something in your home lab at 2 AM and six months later you're staring at your setup like "wait, which drive did I upgrade? And when? And why is everything broken now?"

Yeah. That feeling.

Brandon Lee from VirtualizationHowto has been wrestling with this exact problem, and he's found something that actually makes documentation... not terrible? It's called RackPeek, and the core idea is genuinely clever: treat your home lab documentation the same way you [treat your infrastructure code.

The Problem With How We Document Stuff

Most people start with good intentions. Maybe you make a Google Sheet. Maybe you export a pretty diagram from some drag-and-drop tool. Maybe you even write markdown notes that you'll definitely keep updated.

And then three hardware swaps later, that documentation is basically fan fiction. Brandon puts it bluntly: "Static documentation struggles to keep up with that kind of pace of change."

The issue isn't laziness—it's that traditional documentation tools actively fight against how modern home labs actually work. You're running Docker containers, swapping mini PCs, updating drives, changing network configs. Your setup is code-first, but your documentation is still living in 2015.

RackPeek: Documentation That Acts Like Code

So what's RackPeek doing differently? Instead of drawing your rack in some GUI and exporting a PNG that'll be outdated by next Tuesday, you define everything in YAML files. Racks, servers, switches, positions, specs—all structured text.

Then RackPeek renders the visual representation from that code.

Why does this matter? Because text files can live in Git. Which means your rack documentation now gets:

Version control ("upgraded from 1TB NVMe to 2TB" in your commit history)
Change tracking (exactly what you modified and when)
Easy rollbacks (something broke? Check what changed)
Collaboration (if you're into that)

Brandon describes it as documentation that "behaves like any other infrastructure as code such as Terraform, Docker Compose files and so on." For people already running their labs infrastructure-as-code style, this just... fits.

No more rack-diagram-v3-FINAL-actually-final-2.png buried in some folder you can't find.

The Real-World Trade-offs

Here's where we need to be honest about what you're signing up for.

The good: RackPeek gives you both a GUI for quick updates and a CLI for keyboard warriors. You can click through adding hardware specs, or you can bang out YAML if that's your speed. The tool is transparent—you can see the raw config files it generates, so you're never locked into a black box.

The less good: Brandon hit a permissions issue right out of the gate with Docker. The container started fine, but threw errors when he tried entering data. Others in the community reported the same thing. It's been fixed in later releases, but this is a young, community-developed tool. You're an early adopter, which means you'll hit edges.

Also—and this is me talking now—you're trading simplicity for discipline. A spreadsheet is lower friction for a single-PC setup. RackPeek makes more sense when you've got actual infrastructure to manage. If your "lab" is one Raspberry Pi running Pi-hole, this might be overkill. But if you're running multiple nodes, storage clusters, VLANs, and you're constantly swapping hardware? The structure starts paying dividends.

What This Actually Looks Like

Getting it running is straightforward if you're comfortable with Docker Compose. Brandon used the appode/rackpeek image, mapped port 8080, set up a bind mount for the config directory. Standard stuff.

Once it's up, you can add devices through the GUI—servers, switches, firewalls, access points, whatever. Input fields for CPU, RAM, drives, network interfaces. As you add entries, your environment takes shape both visually and in the underlying YAML.

The built-in CLI emulator is actually kind of nice. You can run help commands, view summaries of your environment, check individual device types, and—this is the part I find useful—view the raw YAML config that's being generated. You're never guessing what the tool is doing behind the scenes.

Brandon notes: "You're not locked into this black box solution. You can see exactly what's happening underneath the hood."

The Bigger Picture

What makes this interesting isn't just the tool itself—it's what it represents. Brandon's treating his home lab like production infrastructure. Everything in structured folders. Every Docker service gets its own directory. Every config is version controlled.

RackPeek fits that philosophy. When you upgrade a drive, you don't just physically swap it—you commit the change with a meaningful message. Now you have a timeline. When performance shifts or something breaks, you can correlate it to physical changes in your git history.

For people using their home lab as actual training ground for career skills, this discipline matters. The habits you build here transfer directly to enterprise environments.

What's Missing (And What Could Be Better)

Brandon mentions some obvious wish-list items. Native Git integration would be huge—right now you can commit the files manually, but having RackPeek handle pushes directly would smooth the workflow.

Automated inventory gathering is another one. Imagine RackPeek automatically pulling some hardware specs instead of manual entry. That'd be slick.

But honestly? For a community-developed tool, it's already doing something genuinely useful. The core concept is sound. The execution is transparent. The approach aligns with how serious home labbers are already thinking.

So the question isn't really "should you use RackPeek?" It's "are you ready to treat your home lab like real infrastructure?"

Because if you're still tracking changes in your head and hoping for the best at 2 AM when something breaks—this might be the nudge you need. Your future self will thank you when they can actually find that commit message from three months ago explaining exactly why you changed that network config.

Or you could keep using documentation-v7-final-ACTUALLY-FINAL.png. Your call. 🤷

—Tyler Nakamura, Consumer Tech & Gadgets Correspondent