Sign In
Access to Author tools and Claude Code Assistant requires authentication.

[ About Lab Stack ]

Building enterprise infrastructure on a budget, one eBay find at a time

Why Build Lab Stack?

This site exists because I believe in a different approach to infrastructure. After 13 years working in cloud and DevOps, I’ve seen both the power and the limitations of “cloud by default” thinking. Lab Stack is my answer to a few questions I kept asking myself:

1. How do I keep track of what’s running where?

Every homelab eventually reaches a point where you forget what’s running where. Lab Stack solves this by pulling live data from my Proxmox clusters, TrueNAS, and Docker hosts to generate the network topology and service listings you see on the homepage. The infrastructure documents itself.

2. Does self-hosting actually save money?

If you don’t need 100% uptime guarantees, self-hosting makes economic sense. My entire homelab—243 vCPUs, 520GB RAM, 47TB storage—would cost approximately $15,000/month on AWS or GCP. I built it for a fraction of that by sourcing enterprise hardware from eBay.

The math is simple: even accounting for power, cooling, and occasional hardware replacements, I’ll save over $500,000 compared to cloud costs over 3 years.

3. Can AI actually help manage infrastructure?

This site is also an experiment in practical AI integration. The deployment pipeline includes Claude agents that:

  • Analyze infrastructure changes and generate documentation
  • Help write and validate configuration files
  • Assist with troubleshooting and optimization

It’s not AI for AI’s sake—it’s about making a single person capable of managing enterprise-grade infrastructure.

4. Can I self-host the entire publishing stack?

I wanted to prove out a complete self-hosted publishing stack:

  • Hugo generates static HTML from Markdown
  • Forgejo (self-hosted Git) handles version control and CI/CD
  • Cloudflare Tunnels provide secure public access without exposing ports

No external dependencies except Cloudflare for edge caching. The entire pipeline runs on my hardware.

5. Where do you even get enterprise hardware on a budget?

Perhaps the most important lesson: you can build serious infrastructure on a budget. My workstation runs dual Xeon 6430 processors (128 cores total) with 256GB DDR5 RAM and multiple GPUs—all sourced from eBay for a fraction of retail cost.

Enterprise hardware gets replaced on 3-year cycles. What’s “end of life” for a Fortune 500 company is perfectly capable of running AI workloads, video encoding, and development environments for individual use.


The Build Journey

Building a dual-socket Xeon workstation from eBay parts isn’t for everyone, but the results speak for themselves.

🖥 Workstation — pop-os

CPU 2x Intel Xeon Gold 6430 (128 cores)
Memory 256GB DDR5 ECC
Motherboard Gigabyte MS73-HB1
GPU NVIDIA GeForce RTX 3090
Storage 2x Samsung 990 PRO 4TB NVMe
Network 10GbE SFP+
OS Pop!_OS 22.04 LTS
Source eBay (enterprise surplus)

🖧 Proxmox Cluster — Main

homelab1 126GB RAM • Primary VM host
homelab2 16GB RAM • Light workloads
homelab3 126GB RAM • Development VMs
Cluster 3 nodes • HA capable

🚀 Proxmox — Mercury

Memory 94GB RAM
Role Edge services • API Gateway • DNS
VMs 8 running (Caddy, PowerDNS, Temporal)
Network Public-facing reverse proxy

💾 TrueNAS — Storage

Hardware UGREEN NASync DXP4800 Plus
CPU/RAM 6 cores • 63GB RAM
Pool: bulk 44.7TB ZFS (HDD array)
Pool: fast 1.9TB ZFS (NVMe cache)
Total Storage 46.5TB available
Services NFS • SSH • S.M.A.R.T.
Version TrueNAS-SCALE-24.04.2.5
Network 10GbE

💡 The Self-Hosting Philosophy

💰

Economics First

Cloud costs compound. Hardware depreciates but keeps working. For workloads that don't need 99.99% SLAs, self-hosting wins on pure economics.

🔒

Data Sovereignty

My data lives on my drives, in my house. No cloud provider can access, mine, or accidentally expose my databases, credentials, or personal files.

🎓

Deep Learning

Managing real infrastructure teaches more than any tutorial. Debugging a failed RAID array at 2 AM builds skills that clicking through AWS console never will.

Sustainability

Enterprise hardware gets replaced on short cycles. Giving it a second life keeps capable equipment out of landfills while providing serious compute capability.

This Site's Stack

Hugo Static site generation
Forgejo Self-hosted Git + CI/CD
Docker Container runtime
Caddy Reverse proxy + TLS
Cloudflare Tunnel + CDN

Every component except Cloudflare runs on my own hardware. Total external dependencies: 1.

Want to Build Your Own?

I'm happy to share parts lists, configuration files, and lessons learned. The homelab community thrives on knowledge sharing.