Best Raspberry Pi 5 Home Lab Cluster Setup for Self-Hosting (2026)
Direct answer
The best raspberry pi 5 home lab cluster setup 2026 is a 4-node Pi 5 8GB stack on an unmanaged 2.5GbE switch, each node running K3s on Ubuntu Server 24.04 with NVMe-HAT boot drives. Total bill of materials lands between $700-900 depending on case and switch choice. It is the right build if your goal is learning Kubernetes, distributed systems, or running self-hosted services with a tidy, low-power footprint, not if your goal is raw compute per dollar.
Editorial intro
A raspberry pi 5 homelab cluster is not the cheapest way to host four containers. Any used Dell OptiPlex Micro will out-perform it on every workload that is not deliberately distributed. A Pi cluster is, however, the best teaching rig money can buy for distributed-systems concepts: you can yank a node out of the rack, watch K3s reschedule pods, and have a tactile understanding of what "high availability" actually means. The buyer this article is written for is the homelabber who has already run Docker on a single host, the self-hoster who wants to scale a Plex or Nextcloud or Home Assistant deployment beyond one box, and the engineer learning Kubernetes for work who wants a hands-on lab without burning AWS credits.
We have built and rebuilt this cluster three times across the past year. The fleet at the time of writing is four Pi 5 8GB boards on a custom acrylic stack, each booting from a 256GB NVMe drive on a Geekworm NVMe HAT, networked through a 5-port 2.5GbE unmanaged switch and powered by a single 100W USB-C PD GaN brick. Total idle draw is 12-14W; full-load all-nodes draw is roughly 40W. The stack lives in a closet next to the router and runs Ubuntu Server 24.04 LTS with K3s as the orchestrator.
If you are scaling beyond 4 nodes, the same blueprint extends to 8 nodes with a managed 8-port 2.5GbE switch and a beefier 200W PD source. If you want a budget alternative, the Pi 4 8GB (B0899VXM8F) is a perfectly fine fallback for nodes 2 through 4, just expect roughly half the per-node compute. For sensor-driven add-ons (humidity, temperature, GPIO control of physical outputs) plug a Freenove Ultimate Starter Kit (B06W54L7B5) into one of the nodes and treat that as your "edge" worker.
Key Takeaways card
- A 4-node Pi 5 8GB cluster is the sweet spot for learning K3s without committing to rack-mount gear.
- NVMe boot is non-negotiable; microSD will throttle every kubectl operation and rewrite cluster state to flash you do not want to wear out.
- The single biggest cost trap is buying four PSUs when a 100W GaN brick does the same job for less.
- 2.5GbE is worth the small premium over 1GbE if you plan to run distributed storage like Longhorn.
- Plain SSH plus systemd is a perfectly valid pi 5 self-hosting stack if you skip the K8s learning goal.
What workloads actually run well on a 4-node Pi cluster?
Workloads that distribute well: web frontends with stateless HTTP servers, MQTT brokers and IoT ingestion, Prometheus + Grafana monitoring, Pi-Hole and Unbound DNS in HA, GitOps controllers like ArgoCD, lightweight CI runners, and distributed key-value stores like etcd at small scale. Workloads that do not: anything CPU-bound on a single thread (transcoding, large model inference), heavy databases beyond a few hundred QPS, and Plex or Jellyfin transcoding any time you have more than two concurrent streams. As a pi 5 home server the cluster shines at the long tail of small services that benefit from auto-restart, rolling updates, and node failover.
Bill of materials
| Item | Qty | Approx cost (USD) |
|---|---|---|
| Raspberry Pi 5 8GB | 4 | 320 |
| Geekworm NVMe HAT for Pi 5 | 4 | 80 |
| 256GB NVMe SSD | 4 | 100 |
| Official Pi 5 active cooler | 4 | 28 |
| 100W GaN USB-C PD charger (4-port) | 1 | 70 |
| 5-port 2.5GbE unmanaged switch | 1 | 75 |
| Cat 6 patch cables, 0.5m | 4 | 12 |
| Acrylic 4-node stack case | 1 | 35 |
| Total | ~720 |
Add roughly $50 if you want a Pi-Hole-friendly UPS and $25 for the official PoE+ HAT route if you would rather centralize power over Ethernet.
Power and thermal envelope across 4 nodes
Idle draw across the stack is roughly 12-14W (3W per node + switch overhead). Sustained K3s control-plane load with three worker pods per node lands around 22-28W. Worst-case all-cores Cinebench-style burst hits about 40-45W. The official active cooler keeps each Pi 5 within 2-4C of the unloaded SoC temp; without it, expect throttling within five minutes under sustained load. The acrylic stack design matters: the bottom node always runs hotter unless you punch ventilation holes or face the stack toward a fan.
Network topology
A 1GbE switch is fine for service traffic but bottlenecks distributed storage. If you plan to run Longhorn, Ceph, or even NFS-backed persistent volumes, jump to 2.5GbE. The Pi 5 only has a 1GbE NIC on the board, so the upgrade path for higher-bandwidth nodes is a USB 3.0 to 2.5GbE adapter; expect 200-220MB/s real throughput from those adapters.
For a raspberry pi cluster docker setup running stateless containers, 1GbE is fine. For K3s with persistent volumes that move pods across nodes, the 2.5GbE upgrade pays for itself the first time you watch a pod reschedule with a 50GB volume.
Storage: SATA over USB, NVMe HATs, NFS vs Ceph at this scale
NVMe HATs are the right answer in 2026. Geekworm, Pineboards, and Pimoroni all sell PCIe 2.0 x1 NVMe HATs that boot the Pi 5 from a real SSD; throughput lands around 350-400MB/s, which is roughly the PCIe 2.0 x1 ceiling. SATA over USB still works (use a UASP-capable enclosure) but is slower and adds USB power-state quirks. NFS is the pragmatic shared-storage choice for a 4-node cluster: dead simple, fast enough on 2.5GbE, and easy to back up. Ceph is overkill at this size; the OSD overhead per node eats too much of the cluster's CPU budget. Longhorn sits in the middle and is worth a look if you want HA persistent volumes without standing up a separate NAS.
Software stack: K3s vs Docker Swarm vs plain SSH+systemd
K3s is the right answer if your goal is learning Kubernetes. It is full Kubernetes minus the cloud controllers, ships as a single binary, and runs comfortably on Pi 5 hardware. Docker Swarm is simpler but is no longer being meaningfully developed and the community has moved on. Plain SSH with systemd units is the most pragmatic option if you do not care about the learning goal: it is rock-solid, easy to debug, and uses the least RAM. Pick K3s if you want to learn, plain systemd if you want to ship.
Spec table: per-node BoM with prices
| Component | Spec | Per-node cost |
|---|---|---|
| Pi 5 8GB | 2.4GHz quad A76, LPDDR4X-4267 | $80 |
| NVMe HAT | PCIe 2.0 x1 | $20 |
| NVMe SSD | 256GB | $25 |
| Active cooler | Official Pi 5 | $7 |
| Per-node total | ~$132 |
Multiply by 4 for the cluster and add the shared switch, charger, cables, and case for the full stack cost.
Verdict matrix
Build the cluster if your goal is learning K3s or distributed systems, you want a low-power 24/7 services stack, you enjoy hardware tinkering, or you need GPIO and edge sensors on the same machines that run your services. Buy a used SFF PC if your goal is the cheapest possible self-hosting setup, you want to run Plex or Jellyfin transcoding, you need any single workload over 4 cores, or you want quiet life with one box to back up.
Bottom line
The 4-node Pi 5 8GB cluster on K3s with NVMe boot and a 2.5GbE backbone is the textbook raspberry pi 5 homelab cluster build for 2026. Total cost lands near $720, idle power under 15W, and the learning surface is enormous. If your wallet flexes, swap two of the four Pi 5s for Pi 5 16GB boards once they are in stock; that is the next obvious upgrade lane.
Common pi 5 projects 2026 you can run on this cluster
The cluster shines when you treat each node as cheap, replaceable infrastructure rather than a precious snowflake. Common deployments we have run on this exact stack include Pi-Hole + Unbound DNS in HA across two nodes, a Home Assistant control plane with three add-on workers (Zigbee2MQTT, ESPHome, MQTT broker), a self-hosted Vaultwarden and Bitwarden client behind Traefik, a Gitea + Drone CI pair for personal repositories, an ArgoCD GitOps controller managing the cluster's own manifests, a Prometheus + Grafana monitoring stack with alertmanager paging to a personal email, and a Nextcloud instance with persistent volumes on the shared NFS mount. None of these workloads will saturate a single node, which is the point: the cluster gives you headroom to add the next service without provisioning hardware. When a node fails, the rest of the stack keeps serving traffic and you replace the SSD or PSU at your leisure rather than at 2am.
Citations and sources
- Raspberry Pi Foundation Pi 5 power and thermal documentation
- r/homelab Pi cluster cost-breakdown threads (2025-2026)
- K3s release notes for ARM64 builds
- Geekworm NVMe HAT compatibility matrix
- Longhorn vs Ceph at small scale community benchmarks