Raspberry Pi 5 Homelab: 10 Projects That Actually Advance Your Career
I have two Raspberry Pis running production workloads right now. Not test environments. Not “I’ll get around to it” boxes gathering dust. Actual services that my family and business rely on every day.
One runs our newsletter platform and website analytics. The other is about to become a Kubernetes worker node. Between them they cost less than two months of the cloud hosting they replaced, and they’ve been quietly doing their thing for months without intervention.
The Pi 5 isn’t a toy you play with for a weekend and shove in a drawer. It’s an ARM server that happens to cost £80. And the skills you build on it are the same skills that command £60-80k salaries in enterprise environments.
From the field: The Raspberry Pi 5 is genuinely impressive for homelab use. I run several across my infrastructure — monitoring, DNS, lightweight services. For the price, there is nothing else that gives you a full Linux environment with this kind of capability.
Career Context: Every project in this series maps directly to enterprise infrastructure skills. Docker, Kubernetes, reverse proxies, monitoring, automation, AI infrastructure — these aren’t homelab hobbies. They’re the skills behind DevOps Engineer, Platform Engineer, and SRE roles at £50-80k+. The only difference between your Pi homelab and a production environment is scale, and scale is the easy part once you understand the fundamentals.
Why Raspberry Pi 5 in 2026?
With DDR5 prices through the roof, the Pi 5’s fixed 8GB suddenly looks attractive. You’re not paying crisis prices for RAM — you’re paying £80 for a complete system that draws less power than a lightbulb.
The Pi 5 is a genuine step change from its predecessors. The quad-core Cortex-A76 at 2.4GHz is significantly faster than the Pi 4, but the real upgrade is the PCIe slot. NVMe storage via a HAT transforms the Pi from “SD card reliability anxiety” to “actual server I trust with data.” If you’ve ever lost a Pi 3 or 4 to a corrupted SD card under heavy writes, you know exactly what I mean.
What you need to get started:
- Raspberry Pi 5 (8GB): ~£80. The 4GB isn’t worth it for homelab use — you’ll hit the ceiling within a week.
- Official 27W Power Supply: ~£12. Don’t use a phone charger. Underpowered Pis throw bizarre errors that’ll have you debugging for hours before you realise the PSU is the problem.
- Active cooler or fan case: ~£5-15. The Pi 5 runs significantly hotter than the Pi 4. Passive cooling will throttle under sustained load.
- NVMe HAT + SSD (recommended): ~£40-100. This is the upgrade that turns a Pi from a hobby board into a real server.
Total cost: £80 bare minimum, ~£180 fully kitted with NVMe. Either way, less than a single month of the cheapest cloud Kubernetes cluster.
For detailed hardware comparisons, see Raspberry Pi vs Mini PC: Which Should You Choose? and Pi Cluster Build Shopping List.
The 10 Projects
Each project below has its own dedicated deep-dive tutorial with step-by-step walkthroughs, real gotchas, troubleshooting guides, and the career context that makes it worth your time. They’re ordered as a progression — earlier projects provide the foundation for later ones — but each tutorial stands on its own if you want to jump ahead.
Docker: Your Foundation for Everything
Every other project in this series runs on Docker. It’s not optional — it’s the foundation of modern infrastructure, and getting it running on a Pi teaches you containerisation on the same ARM platform that powers AWS Graviton and Azure Ampere instances.
But there’s more to it than curl | sh. The tutorial covers directory structure that scales, the permissions trap that catches everyone on their first day, ARM-specific image considerations, and why Docker Compose files should be your default from day one — not an afterthought.
Enterprise skill: Container orchestration Roles: DevOps Engineer, Platform Engineer
Portainer: See What Your Containers Are Actually Doing
When you’re SSH’d into a Pi at 11pm trying to figure out why something isn’t working, being able to check container logs, resource usage, and network config through a browser is a lifesaver. Portainer gives you that visibility.
More importantly, it changes how you think about containers. Instead of commands you ran once and forgot about, you start seeing managed resources with lifecycles, resource consumption patterns, and health states. That shift in thinking — from “running containers” to “operating infrastructure” — is exactly what separates junior from senior engineers.
Enterprise skill: Container lifecycle management Roles: Platform Engineer, SRE
Pi-hole: Network-Wide Ad Blocking and DNS You Control
Pi-hole blocks ads and trackers at the DNS level for your entire network. Every device benefits instantly — phones, smart TVs, IoT devices, everything — without installing anything on them. It’s the project that makes everyone in your house immediately grateful for your homelab.
But the career value goes deeper than ad blocking. You’re learning DNS fundamentals — the thing that’s involved in almost every network troubleshooting scenario you’ll ever encounter. The tutorial covers the systemd-resolved conflict that trips up every Ubuntu user, custom blocklist management, and what all those query logs are actually telling you about your network.
Enterprise skill: DNS infrastructure Roles: Network Engineer, Systems Administrator
Nginx Proxy Manager: Proper URLs and SSL for Everything
Once you’ve got a few services running, you’ll get tired of remembering port numbers. Is Portainer on 9443? Pi-hole on 80? n8n on 5678? A reverse proxy gives everything a proper URL with SSL certificates, and understanding how that works is infrastructure 101.
In enterprise environments, every web application sits behind a proxy or load balancer. When something “isn’t accessible,” the first thing you check is the proxy config. The tutorial walks through host headers, upstream servers, SSL termination, Let’s Encrypt automation, and the service routing decisions you’ll face when ports inevitably conflict.
Enterprise skill: Reverse proxy, ingress, SSL/TLS Roles: Infrastructure Engineer, SRE
Home Assistant: Event-Driven Automation That Teaches Enterprise Patterns
The career reason to run Home Assistant isn’t home automation — it’s that Home Assistant is an event-driven platform with an API, hundreds of integrations, state management, and YAML-based configuration. Those are the same patterns used in enterprise workflow engines, CI/CD pipelines, and integration platforms.
Even without a single smart bulb, Home Assistant is worth running for the automation engine. Build automations that monitor system metrics, send notifications when services fail, or trigger actions on schedules. The mental model of “when X happens, if Y is true, do Z” is identical whether you’re automating lights or deploying infrastructure.
Enterprise skill: Event-driven architecture, API integration Roles: Automation Engineer, Integration Architect
Ollama: Run AI Models on Your Own Hardware
Running large language models locally isn’t a novelty anymore. Data sovereignty, air-gapped deployments, cost control on API calls — there are real business reasons enterprises need people who understand local AI infrastructure. Having “I’ve deployed and managed self-hosted LLM infrastructure” on your CV is a genuine differentiator in 2026.
The tutorial is honest about what the Pi 5 can and can’t do here. You’ll run 3-4B parameter models at usable speeds — surprisingly capable for summarisation, text processing, and automation tasks. You won’t be having ChatGPT-level conversations. The guide covers model selection for ARM, memory management (critical on 8GB), Open WebUI setup, and connecting Ollama to your other services via API.
Enterprise skill: ML model serving, AI infrastructure Roles: ML Ops Engineer, AI Engineer
Uptime Kuma: Know When Things Break Before Anyone Tells You
If your Pi-hole goes down at 2am, how would you know? If a container quietly crashes, how long until you notice? Monitoring is the difference between running services and operating infrastructure. It’s also the thing that most homelab guides skip, and it’s the thing enterprise environments absolutely cannot do without.
The tutorial covers HTTP, TCP, and Docker container monitors, alerting via Telegram (easiest to set up), status pages you can share, and the operational instincts you’ll develop once you start watching your services systematically. You’ll find yourself checking the dashboard first thing in the morning — exactly like a real operations team.
Enterprise skill: Monitoring, observability, SLAs Roles: SRE, Operations Engineer
K3s: Real Kubernetes on a Raspberry Pi
Kubernetes is the container orchestration standard. EKS, AKS, GKE — they’re all Kubernetes underneath. And K3s is lightweight Kubernetes that runs beautifully on Raspberry Pis. One command gives you a working cluster. Add more Pis and you’ve got a multi-node environment that teaches real scheduling, pod distribution, and failure recovery.
The tutorial is upfront: Kubernetes will feel over-engineered for running a few containers on a Pi, and for that use case, it genuinely is. The point isn’t efficiency — it’s building muscle memory with kubectl, understanding manifests, and having real operational answers when an interviewer asks about your Kubernetes experience. “I run a K3s cluster at home” carries weight that weekend tutorials cannot provide.
Enterprise skill: Kubernetes orchestration Roles: Platform Engineer, Cloud Engineer
n8n: Connect Everything With Visual Workflow Automation
n8n turns your collection of individual services into a connected system. That’s the jump from “I have some containers” to “I have infrastructure.” Self-healing restarts when Uptime Kuma detects a failure. RSS feeds processed through Ollama for AI-powered summarisation. Automated backups that validate themselves and alert on failure.
This is the project that ties everything else together, and it’s the skill that separates a £45k sysadmin from a £70k DevOps engineer — the ability to make systems work together automatically. The tutorial covers real workflow examples using the other projects in this series, webhook architectures, and the automation patterns behind every “automate everything” job requirement.
Enterprise skill: Automation engineering, iPaaS Roles: Automation Engineer, Integration Specialist
Gitea: Own Your Code, Track Your Infrastructure
By now you’ve got Compose files, configs, automation workflows, and notes scattered across your Pi. Without version control, one bad command or corrupted SD card wipes out everything you’ve built. Gitea gives you self-hosted Git with a clean web interface, and more importantly, it builds the habit of infrastructure-as-code.
When your configs live in Git, you can rebuild from scratch in minutes, track exactly what changed when something breaks, and set up CI/CD pipelines with Gitea’s built-in Actions. The tutorial covers repository structure for homelab configs, what to commit (and critically, what never to commit), branching strategies, and why Git proficiency matters for every infrastructure role — not just development.
Enterprise skill: GitOps, IaC, CI/CD Roles: DevOps Engineer, Release Engineer
What Order Should You Build In?
Don’t try to do all 10 in a weekend. Here’s a realistic progression that builds each layer properly:
- Week 1: Docker + Portainer + Pi-hole. Get comfortable with containers and see immediate value from network-wide ad blocking.
- Week 2: Nginx Proxy Manager + Uptime Kuma. Proper access to your services and monitoring in place before you add more complexity.
- Week 3: Gitea and start committing everything you’ve built so far. Yes, I’m suggesting version control before the “fun” projects, because losing your configs to a corrupted SD card is painful and preventable.
- Week 4+: Pick from Home Assistant, Ollama, n8n, or K3s based on what interests you. They’re independent at this stage.
The temptation is to skip monitoring and version control in favour of the exciting stuff. Resist it. The exciting stuff is more fun when you’re not rebuilding from memory after something goes wrong.
Career Translation
Every project in this series maps directly to enterprise skills that employers actively hire for:
| Pi Project | Enterprise Equivalent | Job Titles (£50-80k+) |
|---|---|---|
| Docker | Container orchestration, runtime management | DevOps Engineer, Platform Engineer |
| Portainer | Container management platforms (Rancher, Lens) | Platform Engineer, SRE |
| Pi-hole | DNS infrastructure, network filtering | Network Engineer, Systems Administrator |
| NPM | Ingress controllers, load balancers, WAFs | Infrastructure Engineer, SRE |
| Home Assistant | Event-driven automation, API integration | Automation Engineer, Integration Architect |
| Ollama | ML model serving, AI infrastructure | ML Ops Engineer, AI Engineer |
| Uptime Kuma | Monitoring, observability, SLA management | SRE, Operations Engineer |
| K3s | Kubernetes (EKS, AKS, GKE) | Platform Engineer, Cloud Engineer |
| n8n | Enterprise automation, iPaaS | Automation Engineer, Integration Specialist |
| Gitea | SCM, GitOps, CI/CD foundations | DevOps Engineer, Release Engineer |
When someone asks in an interview “tell me about your experience with containers,” you don’t say “I did a tutorial once.” You say “I run 10+ services on infrastructure I built and maintain, with monitoring, automated recovery, and everything tracked in version control.” That’s a fundamentally different conversation.
For tips on translating homelab experience into job applications, see How to Write a Tech CV With No Experience.
Next Steps
- Start with Project 1: Docker — the foundation for everything else
- How to Build Your First Homelab in 2026 — complete overview including budget hardware options
- Installing Ubuntu Server on Raspberry Pi — detailed OS setup guide
- Pi Cluster Build Shopping List — for when one Pi isn’t enough
- Linux Commands That Get You Hired — essential skills reference
Working through the series? I’d love to hear what you’re building — share your Pi 5 setup in the comments.
Related Guides
If you found this useful, these guides continue the journey:
- How to Install Docker on Raspberry Pi — the first thing to deploy on your Pi 5
- How to Build Your First Homelab in 2026 — complete overview including budget options beyond the Pi
- How to Run Pi-hole in Docker — network-wide ad blocking on your Pi
- Raspberry Pi vs Mini PC — detailed comparison to help you decide what hardware fits your needs
- Best Refurbished Mini PCs for Your Homelab — when you outgrow the Pi and need more compute
ReadTheManual is run, written and curated by Eric Lonsdale.
Eric has over 20 years of professional experience in IT infrastructure, cloud architecture, and cybersecurity, but started with PCs long before that.
He built his first machine from parts bought off tables at the local college campus, hoping they worked. He learned on BBC Micros and Atari units in the early 90s, and has built almost every PC he’s used between 1995 and now.
From helpdesk to infrastructure architect, Eric has worked across enterprise datacentres, Azure environments, and security operations. He’s managed teams, trained engineers, and spent two decades solving the problems this site teaches you to solve.
ReadTheManual exists because Eric believes the best way to learn IT is to build things, break things, and actually read the manual. Every guide on this site runs on infrastructure he owns and maintains.
Enjoyed this guide?
New articles on Linux, homelab, cloud, and automation every 2 days. No spam, unsubscribe anytime.