How to Build a Low Power Homelab: Start With a Watt Budget

Most advice on how to build a low power homelab is a parts list wearing a disguise. The parts matter less than the order of operations: set a watt budget first, then buy the cheapest hardware that fits inside it, then verify with a meter that it actually does. Idle power is the only spec your homelab exhibits 23 hours a day, and it is the one number most build guides never mention.

The budget this guide designs around: 10W at the wall, warm idle, full stack running. Here is why that number, and how to hit it.

Who this is for, and who should skip it

This is for someone running a handful of always-on services (media server, sync, monitoring, maybe a game server) on their own power bill, with the box living in a home rather than a garage rack. Time cost is honest: an afternoon to build, an evening to set up.

Skip it if you need hardware transcoding for four simultaneous remote streams, more than about 4TB of storage, or a GPU. Those are real requirements, they just belong to a different build with a different watt budget. And if you already own rack gear you love, keep it; just put a meter on it so the decision is informed.

Set the watt budget before the parts list

At the U.S. average residential electricity rate of 18.44 cents per kWh (EIA Electric Power Monthly, May 2026), one watt running around the clock is about 8.8 kWh a year, call it $1.60. So:

• A mini PC idling at 8W costs roughly $13 a year.
• A repurposed desktop tower idling at 60W costs roughly $97 a year, every year, for the crime of being free.

That gap is the entire argument for building low power on purpose. The full arithmetic, including higher-rate states where the gap triples, is in the power cost math.

Hardware that works

The default answer in 2026 is an Intel N100-class mini PC (Beelink S12 Pro and its many near-identical siblings): four efficiency cores, a 6W TDP, and enough grunt for a dozen containers. When ServeTheHome tested a CWWK N100 system, it idled at 7.4 to 8W and peaked around 20 to 25W with SATA SSDs attached. That is the budget, met, with headroom.

Here is the trap: the chip does not guarantee the number. ServeTheHome’s review of a fanless N100 firewall appliance found 10.5 to 12W at idle on the same processor, worse than some 35W-TDP corporate 1L PCs. Board design and firmware decide your idle draw, not the CPU sticker. Two consequences:

1. Buy a $25 inline power meter with the PC. It is the only way to know what you actually built. The method is in measuring mini PC idle wattage.
2. Spend ten minutes in the BIOS. Enable deep C-states, set “restore on AC power loss”, turn off unused radios. This class of tuning is routinely worth 1 to 3W, and the AC-recovery setting is the difference between a box that comes back on its own after an outage and one that stays dark until you notice.

If the N100 feels tight, the N100 vs N305 vs N97 comparison covers when the step up is worth it. If even $150 feels steep, a used corporate thin client gets you most of the way for a third of the money.

The stack

Run Debian minimal and Docker Compose: services, networks, and volumes declared in one YAML file, brought up with one command, trivially rebuilt when you inevitably reinstall. A realistic starter stack:

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    ports: ["8096:8096"]
    volumes:
      - ./jellyfin/config:/config
      - /mnt/storage/media:/media:ro
    restart: unless-stopped
  syncthing:
    image: syncthing/syncthing:latest
    ports: ["8384:8384", "22000:22000"]
    volumes:
      - /mnt/storage/sync:/var/syncthing
    restart: unless-stopped
  uptime-kuma:
    image: louislam/uptime-kuma:1
    ports: ["3001:3001"]
    volumes:
      - ./kuma:/app/data
    restart: unless-stopped

Idle containers cost RAM, not watts; a stack like this leaves an N100 nearly asleep. Size the box by memory (16GB minimum, 32GB if the slots allow) and add services freely — though the order matters more than the list, and the deploy order that works puts reverse proxy, DNS, remote access and backups in before any of the applications above. DockerHomeLab keeps clean Compose layouts for the reverse-proxy stage, when you want real hostnames and TLS in front of all of this.

Storage and backups

Inside the box: SSDs only. A 3.5” hard drive adds several idle watts and a hum you will notice at 2 a.m.; one NVMe for boot and Docker plus a 2.5” SATA SSD for bulk data stays silent and inside budget. The day you genuinely need more than ~4TB, that is a NAS, a separate box in a closet with its own watt budget, and TrueNASGuide covers that tier properly.

Backups are two lines of discipline, not a product. Nightly restic or rsync to a USB SSD taped to the shelf, plus an off-site copy of the irreplaceable stuff (B2 or any S3-compatible bucket). Then the part everyone skips: once a month, restore one file and open it. An unrestored backup is a theory.

Networking

Do not port-forward services to the internet. Install Tailscale on the server and your devices: each machine joins a private tailnet with a stable address and a MagicDNS name, so http://minilab:8096 works from anywhere with zero exposed ports and nothing for a scanner to find. The free tier covers a homelab several times over. Public exposure through a reverse proxy is a legitimate later step; it should never be the first one.

Operations

Boring keeps the budget honest. Enable unattended security updates on Debian, update container images deliberately (monthly, after a glance at changelogs) rather than letting an auto-updater surprise you at midnight, and let Uptime Kuma send the alerts. Put the meter back on the box once a quarter: services accrete, and warm idle drifts up quietly. A small UPS finishes the job; sizing one for a 10W load is almost comically easy.

That is the whole method: budget, verify, keep it boring. A box that meets it costs about a dollar a month to run and is quiet enough to forget, and the 24/7 reference build shows the exact parts version of everything above.

Related across the network

• Sizing an Off-Grid Solar System for Always-On Homelab Loads — solarhomelabs.com
• MPPT vs PWM Charge Controllers for Homelab Solar — solarhomelabs.com