Observe
Logs, packets, and the quiet clues hiding between the alerts.
A home lab journal / Chicago, IL
Buildthe lab.
Learn the skills. Own the infrastructure. A real-world lab for networking, cybersecurity, Linux and AI — built in public.
No shortcuts.
No cloud-only
experiments.
01 / The operator
iCommish Labs is a public workbench for the systems that make modern life run — and the person learning to understand every layer.
01—Curiosity is the operating system.
The goal isn't to collect gear. It's to build enough context to make better decisions: what to automate, what to secure, what to repair, and what deserves to be rebuilt from first principles.
02 / The environment
One station.
Many rooms.
An abandoned platform, rewired for a different kind of departure. The lab is part SOC, part server room, part classroom.
SOC / monitoring01.24.26 — ACTIVE
Rack / infrastructure10.10.0.0/16
Bench / repairTOOLS + PARTS
Understand
Linux, routing, identity, and the fundamentals that compound.
Make
Projects that turn theory into something with an IP address.
03 / Work in progress
What I'm
building.
The lab changes as the skills get sharper. Follow along as each project moves from a scribble in a notebook to a system that earns its place in the rack.
04 / Field notes
Reviews with
a point of view.
No star ratings. No unboxing theater. Just the useful part: what it does, what it costs, and whether it belongs in the lab.
The best hardware is the hardware that teaches you something.
A quiet server can still change the way you think.
05 / The kit
Tools I
actually use.
06 / The long game
Repair.
Refurbish.
Rebuild.
Infrastructure doesn't have to be new to be valuable. The lab gives old hardware a second job, documents the process, and keeps one more good machine out of the waste stream.
Read the refurb log ↗