What to actually buy for a Raspberry Pi homelab node
Heads up: some links in this article are affiliate links. If you buy through them I may earn a small commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. I only recommend gear I'd run myself.
TL;DR: A Raspberry Pi as a homelab node lives or dies on four things: a real power supply (not whatever phone charger is in the drawer), boot storage off microSD, a case that actually cools it, and — if you’re running more than one — PoE to kill the outlet-and-adapter clutter. Get those four right and the Pi itself is the easy part.
The Pi is the cheap part of a Raspberry Pi homelab node. Where people end up with a flaky, randomly-rebooting node isn’t the board — it’s the accessories around it, bought as an afterthought because “it’s just a Pi.” Get four things right and a Pi node is genuinely reliable as a DNS server, a Pi-hole, a small Kubernetes node, or a sensor hub; get them wrong and you’ll spend more time debugging mystery reboots than the hardware cost you.
1. A real power supply — this is the one people get wrong most
Raspberry Pi boards, especially 4 and 5, are far more sensitive to power quality than people expect. A phone charger that’s fine for a phone can cause undervoltage warnings, random reboots, USB devices dropping out, or throttled performance under load — and the symptom looks exactly like a software bug, which is why it eats hours before anyone blames the power brick.
- Buy the official supply for your specific Pi model, or a third-party one explicitly rated for it — wattage and voltage requirements changed across Pi 4 and Pi 5, and a supply that was fine for an older model can undervoltage a newer one under load.
- If you’re running anything off USB (an SSD, a hub), budget extra headroom — those devices draw from the same supply.
The single most common cause of 'random' Pi instability — check wattage matches your specific board.
A power supply rated for your Pi model ↗2. Boot from SSD over USB, not microSD, for anything that matters
MicroSD is fine for a quick project or a read-mostly appliance. It is a bad choice for anything doing real writes — logs, a database, container image layers — because SD cards wear out under sustained write load and tend to fail unpredictably rather than gracefully, often corrupting the boot partition on the way out. If you’ve ever had a Pi node “just stop booting” for no clear reason, a worn SD card is the usual suspect.
Booting from an SSD over USB (supported natively on Pi 4 and Pi 5) fixes this: SSDs handle sustained writes far better, they’re faster, and a failing SSD tends to give you SMART warnings rather than a silent boot-sector corruption.
Boot from this instead of microSD for anything doing real write load — logs, databases, containers.
A USB SSD enclosure ↗If you do stick with microSD (fine for a genuinely low-write appliance like a read-only sensor display), buy a card explicitly rated for sustained random-write endurance, not just a fast one — sequential read speed on the box doesn’t reflect how a card survives years of small writes.
3. A case that actually cools it, not just protects it
A bare Pi throttles under sustained load once it hits thermal limits, and a plain plastic case with no airflow can make that worse, not better, by trapping heat against the board. For a homelab node that might run continuously — not a project you power on for an afternoon — cooling is part of the case decision, not an optional add-on:
- Passive (heatsink-only) cases are quiet and fine for light, bursty loads — DNS, a small web dashboard, a sensor hub.
- Active cooling (a case with a small fan) matters once the node is doing something sustained — a Kubernetes node under real load, a Pi-hole serving a busy household, anything compiling or transcoding.
Worth it for anything running sustained load — passive cases are fine for light, bursty tasks only.
A case with active cooling ↗Check GPIO access on whatever case you pick if you plan to add a PoE HAT or any other GPIO-connected board later — some cases fully enclose the header, which is fine until you want to add something.
4. PoE, once you have more than one or two nodes
A single Pi is easy to power with a wall wart tucked behind a shelf. A cluster of them turns into a genuine cable-and-adapter mess — one power brick per node, one outlet per brick, and a tangle that’s actively annoying to move or troubleshoot. A PoE HAT solves this by carrying both power and data over the single Ethernet cable each node needs anyway, which also means one less thing to plug into a wall.
- You need a PoE-capable switch for this to work — see 2.5GbE at home: the switch and adapters worth buying if you’re shopping for a switch at the same time and want to check PoE support while you’re at it.
- Match the HAT’s PoE standard (802.3af/at) to what your switch actually supplies — an underpowered PoE port can cause the same undervoltage symptoms as a bad wall adapter.
One Ethernet cable instead of a cable plus a wall adapter per node — worth it past a single Pi.
A PoE HAT for your Pi model ↗What to skip
- Overclocking kits and exotic cooling for a homelab appliance. A DNS server or a Pi-hole doesn’t need the headroom, and pushing clocks up reintroduces the exact instability a good power supply and case were supposed to eliminate.
- A case with no GPIO access “because it looks cleaner” if there’s any chance you’ll want a HAT later — you’ll end up buying a second case.
- The cheapest unbranded power supply you can find. This is the one category where a few dollars saved routinely costs an afternoon of debugging phantom instability.
Common mistakes
- Blaming software for undervoltage symptoms. Random reboots, USB devices
dropping, or a node that’s “just slow” under load is a power supply problem
far more often than people assume — check
vcgencmd get_throttled(or the undervoltage icon on Pi OS) before you start debugging anything else. - Running a database or heavy logging on microSD and being surprised when the card fails within a year. Move the write-heavy workload to SSD, or move the writes off the Pi entirely (log to a NAS instead).
- Buying a PoE HAT without checking the switch actually supplies enough power per port — a switch with PoE ports doesn’t guarantee every port supplies the wattage a given HAT and Pi combination needs under load.
The short version
Buy a power supply rated for your exact Pi model, boot from an SSD instead of microSD for anything doing real writes, pick a case with cooling that matches the workload, and add PoE once you’re past a single node. None of these cost much more than the cheap alternative — they’re the difference between a Pi that quietly runs for years and one you keep having to walk over and power-cycle.