For two years I had been handing over $50 a month to a small cloud provider to run four pieces of software that, between them, barely touched the network. Pi-hole (a tool that blocks ads and trackers at the DNS level for every device on the network). Syncthing (peer-to-peer folder syncing between my laptop and desktop). A Mosquitto MQTT broker (a tiny message-passing server used by home automation sensors). A Tailscale node (a private mesh VPN that lets me reach my home network from anywhere without poking holes in the firewall). None of those things need a fast CPU. None of them move a lot of bytes. The cloud bill was paying for the convenience of not owning hardware, and after two years of that math, I bought a Raspberry Pi Zero 2 W for $15 and moved everything over a single weekend. The cloud subscription is gone, and the Pi has not blinked since.
I want to be honest about what the board is. The Zero 2 W is the slowest option in the current Raspberry Pi lineup: a quad-core 1 GHz ARM Cortex-A53 chip, 512MB of RAM, no full-size USB ports, no gigabit ethernet. On paper, this is a hobby board for blinking LEDs and learning GPIO. In practice, for the specific set of small, quiet, always-on services I wanted to run, the spec sheet is irrelevant. What matters is that the board can stay powered on for weeks at a time, draw less than a watt at idle, and handle four small daemons without breaking a sweat.
Why a tiny board works for tiny services
Most people who run a Pi Zero 2 W as a home server start with Raspberry Pi OS Lite, which is the official image and the one most guides assume. On a board with 512MB of RAM, that image leaves around 400MB free after boot. The remaining 112MB or so is enough headroom for tinkering, but it gets tight the moment you start adding services that want to actually run in the background.
DietPi is a third-party Debian-based distribution (Debian is the Linux distribution that Raspberry Pi OS is built on) built specifically for low-memory single board computers. The whole project is about squeezing more out of less. Where the official Lite image sits at roughly 100MB at idle, DietPi idles around 70MB on the same hardware. Armbian, which is the other common alternative for low-end boards, lands somewhere around 130-140MB. That 30MB gap between DietPi and the official image is not a marketing number. On a board with 512MB total RAM, it is the difference between having room for two more small services and watching the system start swapping to the SD card.
- DietPi base image idles around 70MB on a Zero 2 W
- Raspberry Pi OS Lite idles around 100MB on the same board
- Armbian idles around 130-140MB on the same board
- The 30MB headroom matters most when you stack several small services
- Storage footprint is smaller too, which matters when the OS lives on a small microSD card
The other thing DietPi gives you is a single command-line menu called dietpi-software that installs and configures the common self-hosted services. Pi-hole, Syncthing, Nextcloud, Jellyfin, WireGuard, Tailscale, MQTT brokers, dozens of others. You pick what you want, DietPi handles the systemd units (the small configuration files that tell Linux how to start and stop a background service), the dependencies, the firewall rules where needed, and the initial config. The same setup on a stock Raspberry Pi OS image means following half a dozen different blog tutorials and debugging permission errors at midnight.
What I actually run on it, and why it fits
The Pi Zero 2 W is not a NAS. It is not a media server. Anyone trying to stream 4K video through it is going to have a bad time, because the single USB 2.0 port is shared with the ethernet adapter and tops out around 40-50 MB/s in real-world conditions. If you need to push gigabytes around regularly, the sensible choice is a Pi 4 or Pi 5 with real gigabit ethernet, and this whole article does not apply.
What the Zero 2 W is genuinely good at is running small, always-on services that do not need fast disks or fast networking. The four I picked are exactly that kind of workload.
- Pi-hole blocks ads at the DNS layer for every device on the network
- Syncthing keeps a few folders in sync between my laptop and desktop
- Mosquitto passes messages between my home automation sensors
- Tailscale lets me reach my home network from anywhere without port forwarding
Together they use a sliver of the available RAM and barely register on the CPU. None of them touch the disk in any serious way. None of them need anything close to gigabit networking. They are exactly the kind of workload where the cloud bill felt most insulting, because I was paying $50 a month to rent a server that was less useful than a $15 board I can hold in two fingers.
The limits that matter, named honestly
There is a reason this is not a more popular setup, and pretending the limits do not exist would make this writeup useless. SD card reliability is the biggest worry for any Pi-based server, and the Zero 2 W has no easy way to boot from a real SSD. The whole OS lives on a microSD card. Cards fail, especially under heavy write load or sudden power loss. If you are running this as a serious home server, you need regular image backups, and you need to accept that an SD card death is a matter of when, not if.
The other limits are mostly physical. The mini-HDMI port means you need an adapter most people do not already own. Power comes in through micro-USB, not USB-C. The board runs warm under sustained load. There is exactly one USB port, and the ethernet adapter uses it, so adding a keyboard or storage means a USB hub.
- No gigabit ethernet, the USB 2.0 bus caps real-world throughput
- microSD-only storage caps both performance and long-term reliability
- Display and power adapters usually are not in the box
- CPU is slow enough that compiling anything from source is painful
- Only one USB port, which the ethernet adapter already occupies
None of that disqualifies the board for the four services I run. None of it would be acceptable if I were trying to run a database or serve a household full of 4K streams. Picking the right board for the right job is most of what this experiment was about, and the Zero 2 W is the right board for the small end of that job.
Trade-offs
The Pi Zero 2 W is not free. Realistically, the all-in cost is $15 for the board, $10-15 for a name-brand microSD card (Samsung or SanDisk, not the no-name five-packs), another $10-15 for a power supply and case if you do not have those already. That lands at roughly $40-50, or one month of the cloud subscription it replaced. After the first month, the math is in your favor for as long as the board runs.
Local hardware also means trading one set of failure modes for another. The cloud subscription was not free in other ways: a provider outage took my services down with everyone else on that provider, a price hike meant I either paid or migrated, and any single terms-of-service change could have meant a weekend of work. Owning a Pi on a shelf means I avoid all of that, and I get a different set: card failures, power outages, and the need to physically swap the board if it dies.
The migration itself took about two hours. The hard part was getting Pi-hole DHCP settings to match what my router was already doing, because getting that wrong on the wrong day would have taken the whole network offline for a few minutes. The easy part was installing Tailscale, which was three commands and a single login. If you want to replicate the setup, the order matters: flash the card, boot, install Pi-hole first, then add the rest one at a time and check memory after each install.
Anyone running small, always-on, low-bandwidth services should think about a Pi Zero 2 W before paying another cloud bill. Anyone streaming video, running a database, or pushing serious data should pick up a Pi 4 or Pi 5 instead and accept the higher price.
What I would tell past me
If I could send a message back to the version of me that started the cloud subscription two years ago, I would say three things.
- Audit what your services actually use. A $50/month server sounds reasonable until you check and realize none of your daemons need more than 256MB of RAM. That is a Pi Zero 2 W, not a cloud VM.
- Buy a name-brand microSD card. The savings on a five-pack of no-name cards are not worth the Sunday afternoon you will spend restoring from a backup when one dies.
- Install one service at a time. Installing everything in one pass feels productive and ends with you debugging four things at once. Pi-hole first, confirm it works, then add the next one.
The cloud is convenient. It is also a recurring bill for things a $15 board can usually handle just fine. The Pi Zero 2 W is not the answer for every self-hosting question, but for the specific set of small, quiet, always-on services that most home networks actually need, it is a hard deal to beat.