Your phone's camera roll, the scanned documents, the photos from your nan's birthday: most of it sits on computers you will never see, in buildings you cannot visit, under terms you did not write. Self-hosting is the plain alternative. A small machine in a cupboard, running software you control, holding files that belong to you. It is cheaper than people expect and less complicated than it sounds — provided you get three things right: hardware, access and backups.

What self-hosting actually means

Self-hosting is running a service on your own hardware rather than renting it. Instead of paying a subscription for cloud storage, you run something like Nextcloud on a box at home and reach it through your own wi-fi. Immich does the same job for photos and can back up your phone overnight. Syncthing keeps folders in step between two devices with no server in the middle at all.

What it is not: a magic privacy switch. The moment you self-host, you are the system administrator. Security patches, failed disks and forgotten passwords are your problem now. Nor is it always cheaper than a few pounds a month for cloud storage — the value is control, and the fact that nobody can change the terms on you halfway through a contract.

If you would not maintain it, do not host it.

Hardware: what to put in the cupboard

You do not need a rack. Any of these will handle a household's files, photos and a media library:

• Raspberry Pi 4 or 5 with a USB SSD. Sips power, silent, cheap to replace. Fine for file sync; struggles with video transcoding.
• A second-hand mini PC. Business machines from the last few years — the tiny Dell, HP and Lenovo models — idle at around 10–15W and take an SSD plus a 2.5-inch drive. The best all-round choice for most people.
• An old laptop. The battery acts as a small UPS during power cuts. Close the lid and tuck it on a shelf.
• A dedicated NAS. Easier to set up, but you are back to trusting one company's software and update schedule.
• Avoid a full-size desktop tower. They idle at 50–100W, which shows on the electricity bill.

For storage, use an SSD for the operating system and current files, and a spinning disk for bulk archives. If a drive is 3.5-inch, put it in a powered enclosure: bus-powered drives that draw current from a USB port cause a lot of avoidable data loss. Two mirrored drives is nice. It is not a backup.

Setting it up in an afternoon

Keep it boring. One operating system, one service at a time, everything written down.

1. Install a server OS — Debian, Ubuntu Server LTS or Raspberry Pi OS Lite. No desktop environment; you will manage it over SSH.
2. Give it a fixed address by setting a DHCP reservation on your router, so the machine keeps the same IP.
3. Create a normal user with sudo, switch to SSH keys, and turn off password logins.
4. Install Docker and Docker Compose. Nearly every self-hosted app ships as a container, which keeps things tidy and easy to remove.
5. Add one service. Syncthing for file sync, or Nextcloud if you want calendars, contacts and shared folders too. Use it for a fortnight before adding the next thing.
6. Put a reverse proxy in front — Caddy is the least fiddly — so you can use names like files.home instead of remembering port numbers.
7. Turn on unattended upgrades so security patches install themselves.

Reaching it from outside the house

The obvious move is to open a port on your router and point it at the server. Please don't, at least not yet. Exposed services are found by scanners within hours.

A mesh VPN such as Tailscale, or plain WireGuard, is the simplest answer. Install it on the server and on your phone and laptop, and they join a private network. Your files are reachable from a hotel in Cornwall or a train, nothing is published to the open internet, and your router stays shut.

It also solves a very British problem. Some broadband providers — mobile and full-fibre networks especially — put households behind carrier-grade NAT, which means port forwarding simply will not work. A tunnel sidesteps it entirely. Cloudflare Tunnel is another option if you need a public address, but a private VPN is enough for family files.

What it costs to keep running

The maths is easy. Watts multiplied by hours, divided by 1,000, gives kilowatt-hours. Multiply that by your unit rate from your bill.

A mini PC drawing 12W around the clock: 12 × 24 ÷ 1,000 = 0.29 kWh a day, roughly 105 kWh a year. At an example rate of 25p per kWh, that is about £26 annually. A Raspberry Pi at 5W comes to around £11. A retired desktop tower at 70W would be nearer £150.

Check your own unit rate rather than trusting any figure you read; rates vary by region, tariff and season, and standing charges are separate. Add a few watts per spinning disk, and a little more when the machine is busy. If the number bothers you, spin disks down when idle or schedule heavy jobs overnight — but do not put the server to sleep if it is meant to catch your phone's photo backups at 3am.

A backup routine you will actually keep

A mirrored pair of drives keeps you running when one fails. It does nothing about fire, theft, ransomware or the command you typed at 11pm. Follow the old 3-2-1 rule: three copies, on two kinds of media, one of them somewhere else.

• Copy one: the live server.
• Copy two: an external USB drive you plug in weekly to sync, then unplug. Nothing can encrypt it along with the originals if it is not connected.
• Copy three, offsite: an encrypted backup to a cloud provider you do not otherwise use, or a portable SSD swapped with a relative every few months. Encrypt before it leaves the house.
• Snapshots: if your filesystem supports them (ZFS, Btrfs), switch them on. They rescue you from accidental deletions, not from burglary.

Then test it. Twice a year, restore a folder from each copy onto a spare machine and open a file. An untested backup is a hope, not

Photo: Peggy_Marco / Pixabay