Set up your home server so someone else can find your files in five years

Forums for self-hosted people have been preoccupied this spring with mortality. A thread titled “Killswitch in case of death” jumped to the top of r/homelab. Someone else posted “So long, old friend” about a Raspberry Pi that had finally gone quiet. Another asked, plainly, when does a homelab become a chore or a job. The same anxiety keeps surfacing in different forms. The work of leaving the cloud was supposed to feel durable. It is starting to feel fragile in a way the cloud was not.

The cloud's answer to the question is brutal but legible. You die, the account stops being paid, the data is eventually deleted. Your spouse may recover something through customer support, or may not. Most people accept that bargain because it is the default and they never had a real chance to negotiate it.

The home-server answer is supposed to be better. In practice it is often worse. The thing in the closet works because you remember the IP address, the SSH key, the docker-compose file, the share name, the password rotation schedule. None of that survives you. Your family inherits a black box.

This is fixable. The fix is not a checklist of cryptographic backups in safe deposit boxes. The fix is to set the system up, from the start, as if a stranger will need to read it.

Why the question keeps coming up

The Killswitch thread asked how to make sure a rack did not keep running indefinitely after the owner was gone. The replies split into two camps. One wanted automation: dead-man's switches, monthly check-ins, encrypted vaults that unlock if the owner stops responding to a ping. The other camp pointed out, gently, that the question was wrong. The problem is not that the rack keeps running. The problem is that the people who survive you cannot use what is on it.

A typical setup makes the same point sideways. People list services like badges: Authentik, Pangolin, Traefik, Nextcloud, Immich, Paperless-ngx, Vaultwarden. A working stack for one operator. If you are hit by a bus, the file your spouse needs is behind a reverse proxy, behind an OIDC provider, behind a VPN, behind your password manager, behind a seed phrase nobody else has memorized.

The cloud's terrible default is at least a default everyone in the family understands. Open Photos, sign in with Mom's email, here are the photos. The home-server version needs to be at least that legible.

What someone else actually needs

The audience is not technical. The audience is your spouse on a Tuesday in February, two months or twenty years from now, sitting at the kitchen table with the family laptop, looking for the photos from the year your kid was born. They are not going to learn SSH. They are not going to read documentation. They will spend ten minutes trying before they give up and feel like they failed you.

What that person needs is small. A drive they can plug into a normal computer and have it appear in Finder or Explorer like any external drive. Folders with plain English names. Filenames that make sense without metadata. One sheet of paper, taped to the case, with the password (if the drive is encrypted) and the answer to one question: what goes where.

The reverse proxy and the OIDC provider and the dashboard are for you. The drive and the folders and the sheet of paper are for everyone else.

The boring layout that works

Here is one shape, with no special software. The drive uses a filesystem any modern operating system can read: exFAT for cross-platform readability, ext4 if the next reader is comfortable on Linux. The top level holds six folders, no more.

Photos by year, then by event, with names like “2017-08 Maine trip” rather than serial numbers from a phone. Documents for taxes and school paperwork and scans of important records, organized by year. Receipts and warranties for the boring things you might need to look up later. Family videos following the same year-and-event scheme. Letters for emails that mattered, exported to PDF, and any cards or notes that should outlive your inbox. And one plain text file at the root, called Read-me-first.txt.

The layout has nothing to do with self-hosting per se. It is the layout that survives you whether the drive lives in a desk drawer, on a small ARM box on your network, or paired off-site at a sibling's house. Harbor Dock happens to be a small ARM box that exposes the drive over a private Tailscale network, but the layout's value does not depend on the box. Plug the drive into any computer; it reads the same way.

The Read-me-first file is the part most setups skip. Three short paragraphs is enough. Where the originals came from. Where the off-site copy lives, if there is one. Who to contact if a folder does not make sense. Date the file the day you write it. Update it once a year. If you cannot bring yourself to write three paragraphs about your own family's files, the rest is theater.

What this layout cannot do

Two honest limits.

First, this is durability for files, not for services. The Vaultwarden instance, the photo-sync app, the home-assistant rules. None of it survives you in a usable form. Plan to retire those in a way that leaves the data on the drive in plain form. Export Vaultwarden to a CSV, encrypt the CSV, put it in Documents/Passwords. Print one copy. Tell one person where it is. The fancy version of this is Shamir secret-sharing across three relatives. The honest version is a printed sheet in a fireproof box and one conversation with the person you trust most.

Second, this is not a substitute for off-site backup. A drive that is readable but in a house that burned down is not a useful drive. The layout above is the local-readable layer. The off-site layer is the same drive, copied to a second box at a friend's house, or to a cloud-free-tier setup, or both. The point is that the off-site copy reads the same as the local one. Whichever copy survives is the one that gets opened.

The home-server answer to mortality is not a clever script. It is a drive a stranger could pick up and use. That part has been quietly available the whole time.