Plan and install

Choose a home server job

Start from one useful workload and derive CPU, memory, storage, network, noise, and power needs.

A home server earns its place when it runs one service you understand and can maintain. Pick a single job first: file sync, backups, a private dashboard, or a dev service you reach from the LAN.

One service done well teaches you more than five half-configured containers.

Why one job first

Every service you add brings updates, storage growth, and its own failure modes. Start with three at once and you debug all three with no working baseline to compare against.

Pick the workload that solves a real problem for you today. You can add more later, on a host you already trust.

Write the requirement down

Before you look at hardware, write a one-page requirement:

service: private file sync
users: 2
storage now: 200 GB
storage in two years: 500 GB
downtime tolerance: one day
network: home LAN and Tailscale
backup target: encrypted offsite copy

Each line answers a question hardware will force on you anyway. Two users syncing files need almost no CPU. A media transcoder needs a lot. “Downtime tolerance: one day” tells you a single cheap machine is fine. You don’t need redundant anything.

Derive the hardware from the job

For a small workload like this, a used mini PC or an old laptop is enough. Check that it has room for the storage you projected, not just what you need today.

Power matters because the machine runs all day:

idle draw: 10 W
one year: 10 W x 8760 h = 87.6 kWh
at 0.30 EUR/kWh: about 26 EUR per year

An old desktop idling at 60 W costs six times that. Noise matters too if the server lives near where you sleep or work.

The mistake everyone makes

The common failure is buying hardware first, then hunting for jobs to justify it. That path ends with an expensive machine running nothing, or running twelve services nobody depends on.

Choose hardware only after the workload, growth, recovery, and power constraints are visible.

My advice: don’t put irreplaceable data on the new machine before the backup and restore path works. Family photos in week one and a dead disk in week three is a lesson you only want to learn once.

Lesson completed