My Home Lab Update: Built to Learn, Built to Break, Built to Keep Me Sharp

There is something about working in IT and security for a long time that changes how you view technology.

You stop being impressed by slide decks.
You stop getting excited about buzzwords.
You stop assuming that because something sounds smart, it actually is.

You learn that most of the truth shows up when you have to build it yourself.

That is a big part of why my home lab matters to me.

It is not just a pile of hardware.
It is not just a hobby.
It is not just me buying gear because I like tech.

It is one of the few places where I can still work on technology without all the garbage that usually comes with it. No politics. No pointless meetings. No people talking in circles. No one pretending to know a framework is the same as actually knowing how something works.

Just the work.

And honestly, that is part of what keeps me sane.

Why I Built It

I built this lab because I still like to learn by doing.

That sounds simple, but in a lot of jobs, especially the farther up you go, you get pulled away from the hands-on side of things. You spend more time in discussions, more time reviewing, more time listening to people with opinions, and less time actually touching the technology.

That gets old.

I do not want to become one of those people who only know how to talk about architecture. I want to build it, test it, break it, fix it, and understand where it falls apart. That is where the real learning is.

My lab gives me that.

The Core Setup

The environment is built around three Intel NUCs, each with 64 GB of RAM and internal storage. That gives me enough compute to run a real virtualization environment without needing a giant rack in the basement or an electric bill that looks like a car payment.

For storage, I am using a 10 GB Synology NAS and a Synology switch. The storage network is separated on its own network with jumbo frames enabled, because if I am going to do it, I want to do it right. I did not want storage traffic mixed in with everything else like an afterthought.

At the center of the lab is a Proxmox cluster that I converted from VMware.

That move was worth it.

The built-in tools in Proxmox made migrating the VMs easier than I expected, which is not something I say often about migration projects. Usually, migrations have a way of becoming more annoying than they need to be. This one was refreshingly straightforward.

The cluster is also configured for failover, which was important to me. I did not want just a few hosts running VMs. I wanted an environment with some resilience built in. On top of that, all the VMs have daily snapshots. That gives me a safety net when I am making changes, testing something new, or doing what IT people do best: confidently clicking something and then immediately wondering if that was a bad idea.

Making It Feel Like a Real Environment

I wanted this lab to feel like more than just a few virtual machines floating around.

I added two Pi-hole DNS servers for ad filtering and malware filtering. That gives me better visibility and a little more control over what is happening in the environment. Plus, there is something deeply satisfying about blocking junk before it gets where it wants to go, kind of like deleting vendor emails before they finish loading.

I also built two Windows Server 2025 Active Directory servers and configured them redundantly with DHCP and DNS. Their DNS forwards requests to the Pi-hole servers, so I have a layered design that mirrors the kind of thinking I would want in a real environment.

That matters to me because I do not want a fake lab.
I want a useful one.

I want services talking to services.
I want dependencies.
I want to see what happens when things fail.
I want the lab to teach me something.

The Security Side

Because I work in security, I also wanted a place where I could test from both sides.

I have a Kali Linux box in the lab to perform security testing and validate controls. I have no interest in just assuming something is secure because a configuration page says it is. That is fantasy football for security people. I would rather test it.

I also built two AI servers that sit behind a pfSense firewall. Those systems live on a virtual network shared by the Proxmox cluster, but they are isolated from my production network. They are only allowed access to the Internet and not back into the rest of the environment.

That isolation was intentional.

I am testing newer tools, automation, AI workflows, and code integrations. I am not going just to let that stuff wander around my network because some vendor somewhere says their platform is “enterprise ready.” That phrase has covered a lot of sins over the years.

What I’m Testing

These two AI servers are not just there to look interesting.

Both pull code from Git, and each has a specific job.

One handles scheduled emails around threat intelligence and investing. That lets me experiment with automation in a way that is actually practical, not just academic. It is doing something useful for me instead of just existing, so I can say I built it.

The other is running an AI bot that lets me query NIST and MITRE ATT&CK documentation using natural language questions. That has been one of the more interesting things I have worked on because it turns a mountain of framework documentation into something more usable. Sometimes I do not want to dig through pages of content to find one answer. Sometimes I want the machine to earn its keep.

I have also been testing Codex and OpenAI in the lab. That has been good for me because it gives me a controlled place to see what is real, what is useful, and what is just hype, and wear better clothes.

That is another reason the lab keeps me grounded. It lets me separate what actually works from what people are just excited about this week.

Backup Still Matters

I am also using the NAS to back up my OneDrive files.

That is not flashy, but neither is losing data.

People love to talk about innovation, AI, transformation, and all the other words that get sprayed around in IT. Meanwhile, basic things like backup, recovery, failover, segmentation, and DNS design are what save you when the wheels come off.

That is why I care about this lab. It gives me room to work on the exciting things and the boring things. And the boring things are usually the ones that matter most when everything goes sideways.

Why This Means More to Me Now

At this point in my career, I think that is the deeper reason I value the lab so much.

It reminds me of why I liked this field in the first place.

Not the politics.
Not the posturing.
Not the people who talk a great game and cannot build a sandwich.
The actual work.

The problem-solving.
The design.
The troubleshooting.
The testing.
The learning.

The lab gives me a place where effort, skill, and results still matter. It keeps me connected to the technical side of who I am without all the noise that tends to come with corporate environments.

And there is something healthy about that.

When work gets frustrating, when teams get dysfunctional, when leadership gets messy, or when you start wondering whether half the people in the room have ever actually touched the technology they are talking about, the lab is a reminder that I still can.

I can still build.
I can still learn.
I can still figure things out.

That matters more than people realize.

What I May Do Next

At some point, I may expose selected services more securely using Cloudflare, probably through a reverse-proxy-style approach, only when I feel the environment is ready for it. But I am not in a rush. I have been in IT too long to mistake “possible” for “good idea.”

The lab has already taught me plenty.
There is no prize for exposing something early just to create my own future headache.

Final Thoughts

My home lab is built on three Intel NUCs, a Proxmox failover cluster, a separate storage network with jumbo frames, daily VM snapshots, a Synology NAS, redundant Windows Server 2025 domain controllers, Pi-hole filtering, a Kali Linux test box, isolated AI servers behind pfSense, Git-based automation, and OneDrive backup.

That is the technical description.

The real description is simpler.

It is my place to keep learning.
It is my place to stay sharp.
It is my place to work on technology without the usual nonsense.
And in a field that can wear you down if you let it, that has real value.

This lab does not just help me test ideas.

It helps me remember why I still give a damn.

TBJ Consulting

TBJ Consulting