Raspberry Pi Server: What Can You Self-Host?

Someone handed you a spare Raspberry Pi, or you bought one on impulse, and now it's sitting on the desk while you have twenty browser tabs open — one tutorial for a NAS, another for Minecraft, another for a security camera — each acting like its project is the only thing a Pi does. None of them tell you what the board actually handles versus where it quietly gives up.

Here's the map. I've run all six of the projects below on real Pi hardware in my own homelab, and this page consolidates the tested ceiling for each one — the actual number that decides whether it's worth building — plus where a Pi stops being the right tool.

TL;DR

A Pi is genuinely good at low-power, always-on, single-purpose jobs: file backup, one game server, a few camera streams, remote access. It struggles the moment a workload needs multiple simultaneous heavy users or serious CPU throughput.
NAS: ~65–113 MB/s over Samba (Pi 4), higher locally on Pi 5 with PCIe — but every Pi NAS is capped at gigabit's ~118 MB/s the moment data leaves the board.
Minecraft: 3–6 players on a Pi 4, 8–12 on a Pi 5, with PaperMC — vanilla roughly halves that.
Security camera: a Pi 5 with a Hailo-8L AI HAT+ runs 4–5 Frigate streams at ~10% CPU; storage, not compute, is what fills up first.
Retro gaming: NES through PS1 run full speed on any current Pi; N64/PSP/Dreamcast/Saturn need a Pi 5 to be reliably playable.

What a Raspberry Pi is actually good at

Every ceiling below traces back to the same three constraints. Single-thread CPU performance is the real limiter for anything simulation-heavy (world ticking, emulation, transcoding) — extra cores don't help a workload that's mostly single-threaded. No native fast networking beyond gigabit on most boards means local storage speed rarely reaches a client at full speed. And SD-card write endurance makes constant-write workloads (databases, continuous camera recording, game-world saves) a reliability risk unless you move to SSD or NVMe.

Where a Pi wins is the opposite side of that coin: it idles at a few watts, costs a fraction of a mini PC or NAS enclosure, and is genuinely fine left running in a drawer for years untouched.

The six things people actually self-host on a Pi

Each of these got its own deep dive with real hands-on numbers — this table is the fast version.

Project	Realistic ceiling	The number that decides it
NAS / file server	Fine for single-user backup	118 MB/s — the gigabit ceiling every Pi NAS hits regardless of drive speed
Minecraft server	3–6 players (Pi 4), 8–12 (Pi 5)	PaperMC vs vanilla — PaperMC roughly halves CPU load
Security camera (Frigate)	4–5 streams on Pi 5 + accelerator	~130 GB/day — what four continuous 1080p streams burn in storage
Retro gaming	NES–PS1 anywhere; N64+ needs Pi 5	3x single-core jump from Pi 4 to Pi 5
Server rack / cluster	Great for learning, not for RAM/€	Peak PoE draw, not idle — a Pi 4 pulls up to 15.3 W
Headless remote access	SSH always; VNC/RDP for GUI work	Never expose 22/5900/3389 raw to the internet

KEY-STAT: 8–12 players — the realistic ceiling for a tuned Minecraft server on a Raspberry Pi 5 — one of the six builds below, and typical of how far a single Pi genuinely stretches

NAS: is a Pi worth it for storage?

A Pi 4 NAS sustains roughly 65–105 MB/s over Samba; a Pi 5 with PCIe-attached NVMe or a SATA HAT pushes far higher locally, but a plain gigabit port still caps what actually reaches a client at around 118 MB/s. It idles under 3 W, so the annual electricity cost is under €9 — a fraction of a mini PC or a spinning-disk NAS. It falls short for multiple simultaneous users, parity RAID rebuilds, and Plex transcoding. The full breakdown, including the throughput and power tables, is in our Raspberry Pi NAS guide.

Game server: how many players can it hold?

Vanilla Minecraft on a Pi is rough, but PaperMC cuts CPU load by roughly 30–50%, and that's the difference between a server that holds a handful of friends and one that struggles past two or three. A Pi 4 (4GB) realistically holds 3–6 players; a Pi 5 (8GB) stretches to 8–12 at a trimmed view-distance. The official Bedrock server has no ARM64 build, so Bedrock friends join through the Geyser plugin instead. Full setup, Docker compose file, and the tuning levers that matter are in our Minecraft-on-a-Pi guide.

Security camera: Frigate or motionEye?

motionEye does simple pixel-diff motion detection and runs on almost anything. Frigate does real object detection ("a person, not a moving branch") but wants an AI accelerator — the Google Coral is now deprecated for new builds, and the current pick is the ~$70 Hailo-8L AI HAT+, which comfortably handles 4–5 camera streams at around 10% CPU. The part every tutorial skips: storage, not compute, is what kills the project — four continuous 1080p streams can burn roughly 130 GB a day, so recording on motion rather than 24/7 is not optional. Full storage math and a working Frigate config are in our Pi security camera guide.

Retro gaming: what actually runs well

NES, SNES, Genesis, GBA, and PS1 run at full speed on a Pi 3 or better — that part of the internet's advice is correct. N64, PSP, Dreamcast, and Saturn are a coin flip on Pi 3/4 and become genuinely playable on a Pi 5, thanks to roughly triple the single-core performance. PS2 and GameCube are still not a good time on any current Pi. The full per-console playability matrix across Pi 3, 4, and 5 is in our retro gaming breakdown.

A Pi cluster or rack: worth building?

A four-Pi rack looks great in photos, but the honest comparison is against a single mini PC: four Pi 5s cost roughly €500 all-in for 32 GB of RAM split across four separate pools, while one €180 mini PC gives 16 GB shared and lower idle power. Budget the PoE switch for peak draw, not idle — a Pi 4 alone can pull up to 15.3 W under load. A cluster earns its place if the goal is learning distributed systems or physical redundancy; if the goal is just running services, one box almost always wins. Power, thermal, and mounting numbers are in our Pi rack guide.

Headless setup and remote access

Whatever you build, you'll eventually need to reach it with no monitor attached. SSH is the right first tool for anything server-like — light, scriptable, and safe with key authentication. Reach for wayvnc (Bookworm's replacement for the now-removed RealVNC) or xrdp only when you need the actual graphical desktop. Whichever you use, never port-forward 22, 5900, or 3389 raw to the internet — tunnel it, put it behind a VPN, or use Raspberry Pi Connect instead. The full setup walkthrough is in our headless Pi access guide.

Warning

The single mistake that undoes all six of these projects is the same one: exposing a service directly to the internet without a VPN or tunnel. A raw port forward to SSH, VNC, RDP, or a game server is found by scanners within hours — always route remote access through a VPN or SSH tunnel.

When to reach for a mini PC instead

Every one of the six builds above hits the same wall eventually: a workload that needs real multi-user throughput, serious CPU for transcoding or heavy emulation, or storage beyond what USB or a single PCIe lane can move. That's not a Pi failure — it's a different tool for a different job. A small N100-class mini PC costs more up front but gives you shared RAM, real SATA/NVMe lanes, and a hardware video encoder, at only slightly higher idle power. Our mini PC home server guide covers exactly where that trade tips, and if you're deciding on the base layer before picking any of the six projects above, our homelab beginner's guide is the right starting point.

Tip

If you're only running one lightweight service — a password manager like self-hosted Vaultwarden, for instance — a Pi is not just adequate, it's the more efficient choice than a mini PC sitting mostly idle.

Picking your first project

Match the project to what you already own or actually need, not to whichever tutorial you found first:

Want to stop paying for cloud storage or backups? Start with the NAS build.
Want an always-on server for you and a few friends? Start with Minecraft.
Want your own doorbell/driveway footage, no cloud subscription? Start with the security camera.
Want to relive a specific console library? Check the playability matrix before buying hardware.
Want to learn how distributed systems actually behave? The cluster is the point, not the overhead — everyone else should buy a mini PC instead.
Whichever you pick, set up SSH with keys first — every other project on this page assumes you can already reach the Pi headless.

FAQ

What can you actually do with a Raspberry Pi as a home server?

Six well-tested projects: a single-user NAS, a small-friend-group Minecraft server, a local security camera system with Frigate, a retro-gaming emulation box, a learning-focused cluster, and headless remote-access infrastructure. Each has a real ceiling — covered in the linked guides above — past which a mini PC becomes the better tool.

Is a Raspberry Pi powerful enough to be a server?

Yes, for single-purpose, low-to-moderate-throughput jobs. Its single-thread CPU performance and gigabit-capped networking are the real limits, not raw "power" — a Pi 5 with the right accelerator or storage add-on handles several of these projects well within their tested ceilings above.

How many things can you self-host on one Raspberry Pi?

Technically several lightweight services at once via Docker, but each of the six projects above already uses a meaningful share of the board's CPU, RAM, or storage bandwidth at its realistic ceiling — stacking two demanding ones (say, Frigate and Minecraft) on one Pi will hit that ceiling faster than either alone.

Should I get a Raspberry Pi or a mini PC for self-hosting?

Start with a Pi if you're testing one project, want the lowest idle power, or are on a tight budget. Move to a mini PC once you need multi-user throughput, real RAID, hardware video transcoding, or you're running several of these projects simultaneously on one box.