Affiliate disclosure: As an Amazon Associate, HomeNode earns from qualifying purchases at no additional cost to you. Product availability subject to change.
A Raspberry Pi is not going to replace a rack of enterprise servers, and it should not try to. What it is very good at is running the handful of small, always-on services that make a home network noticeably better – ad blocking, a shared drive, a password manager, a dashboard – for around 10 watts of power and less than the cost of one dinner out. This is a start-to-finish setup guide, including the point where a Pi stops being the right tool.
Video: how to build a Raspberry Pi NAS (it's AWESOME!!) by NetworkChuck, via YouTube.
Pick the Right Board
For a home server build in 2026, get a Raspberry Pi 5 8GB. The 4GB model works for a single lightweight service (Pi-hole alone, for example) but 8GB gives enough headroom to run several containers without swapping to storage, which is where a Pi’s performance falls off a cliff. The Pi 4 is still fine if you already own one – do not buy a Pi 4 new in 2026 when the 5 costs about the same and is noticeably faster on I/O.
Skip the case-and-fan kits that only include a passive heatsink. The Pi 5 runs warm under sustained load (Docker containers, a Samba transfer, Pi-hole logging) and will throttle without active cooling. A case with a small fan, like the official Raspberry Pi 5 Active Cooler, is worth the extra few dollars.
Boot From SSD, Not microSD
This is the single biggest quality-of-life upgrade for a Pi server. A microSD card will work, but SD cards wear out under the constant small writes a server generates (logs, databases, container layers), and read/write speeds bottleneck anything you’re doing with files. Boot instead from a USB SSD:
- A small USB 3.0 SSD enclosure with a cheap 2.5″ SATA SSD, or a single USB 3.0 external SSD drive
- 120-256GB is plenty for the OS plus a handful of containers; go bigger only if this Pi will also store files
The Pi 5 can boot natively from USB without any SD card involved at all – flash the OS to the SSD with Raspberry Pi Imager, plug the SSD in, and it boots. Keep a microSD card around only as a rescue/recovery option.
Flash the OS and Set Up Headless
Use the official Raspberry Pi Imager on your main computer. Pick Raspberry Pi OS Lite (64-bit) – there is no reason to install the desktop version on something that will live headless in a closet. Before writing the image, click the gear icon (advanced options) and set:
- Hostname (e.g.
homeserver.local) - Enable SSH, with a password or your SSH public key
- Wi-Fi credentials if you’re not running Ethernet (Ethernet is strongly preferred for a server – it’s more reliable and doesn’t compete with the rest of your household’s Wi-Fi)
- Username and password
Write the image, plug the Pi in, and after a minute or two connect with ssh username@homeserver.local from another machine on the same network. From here everything else happens over that SSH session – you never need a monitor or keyboard plugged into the Pi itself.
Update and Set a Static IP
The first commands on any fresh install:
sudo apt update && sudo apt full-upgrade -y
sudo rebootGive the Pi a static IP, either by reserving its address in your router’s DHCP settings (the easier, more portable option) or by editing /etc/dhcpcd.conf directly on the Pi. A static address matters because most of what you install next – Pi-hole, a file share, a dashboard – gets referenced by IP or hostname from other devices, and you do not want that to change every time the Pi reboots.
Install Docker
Nearly everything worth running on a home server ships as a Docker container, and Docker keeps each service isolated so a broken update to one thing doesn’t take down everything else. Install it with the official convenience script:
curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker $USERLog out and back in for the group change to apply. Then install Portainer, a free web dashboard for managing containers without memorizing Docker CLI flags:
docker volume create portainer_data
docker run -d -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latestVisit https://homeserver.local:9443 from a browser on your network to finish setup.
The Services Worth Running First
- Pi-hole – network-wide ad and tracker blocking at the DNS level. Runs comfortably on a Pi 3 by itself, let alone a 5.
- Samba or NFS – turn an attached USB drive into a shared network folder visible from Windows, Mac, or a phone.
- Vaultwarden – a lightweight, self-hosted Bitwarden-compatible password manager.
- Homepage or Homarr – a single dashboard page linking out to every service you run, so you’re not bookmarking a dozen IP addresses.
- Uptime Kuma – a status page that pings your other services and alerts you (email, Telegram, etc.) if one goes down.
Start with two or three of these, confirm they’re stable for a week, then add more. A Pi 5 with 8GB can comfortably run all five at once with room to spare.
Comparison: What Fits on a Pi vs What Doesn’t
| Workload | Runs well on Pi 5 | Notes |
|---|---|---|
| Pi-hole / DNS ad blocking | Yes | Trivial load |
| File sharing (Samba/NFS) | Yes | Limited by USB/network speed, not CPU |
| Password manager (Vaultwarden) | Yes | Tiny footprint |
| Home Assistant | Yes, for most homes | Fine under ~50 devices; heavier setups want more RAM |
| Plex/Jellyfin with transcoding | No | No hardware transcoder; 1080p transcodes will stutter |
| Self-hosted AI chatbot (Ollama) | Limited | Only tiny quantized models; see the Pi vs Mini PC comparison below |
| Security camera NVR (Frigate) | No, without a Coral accelerator | CPU-only object detection overwhelms the Pi |
Back Up Before You Forget To
The most common way a home Pi server dies is a corrupted boot drive with no backup. Once your services are stable, set up something as simple as a weekly rsync of your Docker volumes to another drive, or use a tool like Duplicati for scheduled encrypted backups. It takes twenty minutes to set up and it is the only thing standing between you and rebuilding everything from scratch.
When to Move Past a Pi
If you eventually want hardware transcoding for Plex, real object detection for security cameras, or to run a genuinely useful local AI chatbot, a Raspberry Pi is the wrong tool – not because it’s bad, but because it’s an ARM board with no GPU and a hard RAM ceiling. At that point a small x86 mini PC with an Intel N100 or similar chip, often available for not much more than a Pi 5 plus accessories, opens up hardware video transcoding and far better single-thread performance. Keep the Pi running the lightweight always-on stuff and add a mini PC as a second box rather than trying to make one machine do everything.
Related Auburn AI Products
Building a homelab or self-hosting content site? Auburn AI has practical kits: