HOMELAB / SELF-HOSTED / LEARNING

My Homelab:
Proxmox, Raspberry Pi, and home networking.

A small, always-on environment where I run useful services, experiment with infrastructure, and learn by troubleshooting the real thing.

START HERE

What's a Homelab?

A homelab is a small setup of computers, servers, and networking equipment that you build at home to experiment with technology.

Think of it as your own mini data center. Instead of just reading about cloud computing, networking, and servers, you get to build and manage them yourself.

I started mine to get more hands-on experience, experiment with new technologies, and host applications I actually use.

Here's what mine looks like and what I've built with it.

WHY BUILD ONE?

What can you do with a homelab?

A practical place to learn by making, testing, and fixing.

Host applications

Run your own services, such as photo storage, media servers, and monitoring tools.

Learn virtualization

Run multiple virtual machines and containers on one physical computer.

Practice networking

Set up and troubleshoot networks, DNS, remote access, and connectivity.

Experiment & learn

Try new technologies, break things, troubleshoot problems, and learn how to fix them.

THE PHYSICAL SETUP

Take a look at my homelab

My setup started with a few pieces of used hardware and has grown into a small home network where I run servers, host applications, and experiment with new technologies.

Open full-size photo ↗
Compact 10-inch homelab rack with patch panel, network switches, shelves, and compute equipment
My compact 10-inch rack. Click the photo to view it larger.

THE BUILDING BLOCKS

My hardware

Each piece has a simple job. Together they make a small environment for compute, storage, and connectivity.

01

Lenovo Tiny

My main Proxmox server, used to run containers and self-hosted applications.

6-core Intel i5 · 16 GB RAM · 256 GB SSD
02

Raspberry Pi

A small computer that runs several always-on services and automation projects.

128 GB microSD · always-on services
03

Network switches

Connect my servers and other wired devices together so they can communicate.

Managed and unmanaged switches
04

Router & access points

Provide connectivity for my home network and the devices that use it.

Netgear Nighthawk · mesh access points

MY NETWORK

A simple view of the architecture

The diagram shows the verified high-level path from the internet to the router, switch, lab nodes, and connected devices. My home network is consolidated on 192.168.1.0/24.

Open diagram ↗
High-level homelab architecture: Internet connects to a Netgear Nighthawk router, then the network switch connects the Lenovo Tiny Proxmox server, Raspberry Pi, and other connected devices
High-level roles only. Specific ports, VLANs, and cable paths are intentionally omitted.

ALWAYS-ON WORKLOADS

What I run in my homelab

These services turn the hardware into something I use every day.

⌘

Proxmox

Virtual machines and containers on the Lenovo Tiny server.

Virtualization
Cropped Proxmox dashboard showing node health and workloadsView screenshot ↗
▧

Immich

Self-hosted photo and video management. I migrated about 255 GB of personal media into the Proxmox environment.

Storage · migration
▶

Jellyfin

A personal media server running in the lab, giving me hands-on practice with storage, Linux, and service networking.

Media · Linux
◌

Uptime Kuma

Monitors service availability and sends outage and recovery notifications through Discord.

Monitoring
Cropped Discord recovery alert from Uptime KumaView alert ↗
⌁

Pi-hole

Network-level DNS filtering used selectively for devices. I have experimented with DNS and DHCP settings.

DNS filtering
▦

Portainer

A web interface I use to inspect and manage Docker workloads in the lab.

Containers
↗

Tailscale

Secure remote connectivity into parts of the homelab without exposing each service publicly.

Remote access
▤

Morning Motivation Bot

Python and cron on the Raspberry Pi send a quote, an Immich video, and daily goals to Discord each morning.

Automation · Python
Cropped Discord morning check-in notification from the Motivation BotView message ↗

THE TAKEAWAYS

What I've learned from building it

  • Linux administration
  • Networking and DNS
  • Virtualization
  • Docker and containers
  • Monitoring and troubleshooting
  • Storage and data migration
  • Automation

KEEP EXPLORING

Follow the build as it grows.

I'll add detailed service notes, screenshots, and network information as I document the setup.