Self-Hosting on Tom Meurs

Your Dependency's Business Model Is Part of Your Threat Model

Wed, 23 Sep 2026 19:00:00 +0200

TL;DR A vendor freezing its free edition belongs in your risk register next to the expiring certificate. Thirty-six dated cases below, three kinds of event, and five questions to score your own stack. My own register had the Vault row missing for three years.

On 11 September, Portainer’s CEO published “Portainer 3.0 is coming, and here’s what it means for you”. I read it the Monday after and shrugged.

Here’s what it says. 3.0 is a Kubernetes-first codebase for enterprise customers, and “we are not cutting a separate CE build of it”. Community Edition stays on 2.x. 2.45 LTS “is the last release in the 2.x line”. A few days later they added a clarification: 2.45 keeps getting security fixes, bug fixes and back-ports of any 3.x feature that has a Docker API equivalent, “for as long as that LTS is supported”. The lifecycle page puts that at May 2027. Want 3.x for free? There’s a Business Edition key called 3 Nodes Free, one per organisation.

Backup Strategy for Your Homelab: The 3-2-1 Rule in Practice

Mon, 18 May 2026 19:30:00 +0100

TL;DR Three copies, two kinds of media, one of them offsite. Restic for files, Velero for the cluster, a Backblaze bucket for the offsite copy, and a restore test on a schedule. Mine costs about €5 a month, and the restore test is the part I still have to make myself do.

Picture the disk in your homelab dying tonight. Not corrupting, not throwing SMART warnings for a week first, just gone. The git server with every repo you care about, the password vault, fifteen years of family photos, the home automation that runs the house. All of it on a drive that’s decided it’s done.

K3s Cluster Setup on Refurbished Mini-PCs

Fri, 24 Apr 2026 21:12:00 +0100

TL;DR Three refurbished mini-PCs, K3s with embedded etcd, kube-vip for one API address that survives a dead node, then MetalLB, Traefik and Longhorn on top. About €450 in hardware and an afternoon. Below are the commands, in the order I ran them.

Three mini-PCs sit on a shelf in my house. Between them they run my GitLab, my monitoring stack, home automation, file sync, a password manager, and a pile of other things I’d rather not hand to someone else’s computer. The whole setup cost less than one month of the managed Kubernetes bill for the same thing, and I know what every layer does because I put it there.

The Hardware Ownership Paradox: When Sovereignty Gets Expensive

Fri, 30 Jan 2026 14:00:00 +0100

In my previous post about self-hosting for everyone I drew a hopeful picture of managed self-hosting, where anyone can own their data. I skipped over something, and it’s been bugging me since. Hardware costs money, and the sum comes out very differently depending on whether a business or a person is paying.

So here are two rules. Both sound reasonable on their own. Then I’ll put them in the same room.

Self-Hosting for Everyone: A Vision for Digital Agency

Tue, 27 Jan 2026 14:00:00 +0100

Most people keep their photos at Google, their mail at Gmail, their documents in whatever cloud came with the phone and their passwords in a browser built by an advertising company. Every byte sits on a server they don’t own, under terms they didn’t read, in a country they didn’t check. Nobody finds that strange anymore, because the alternative looks like a second job.

I want to talk about that alternative, and about why it sits behind a wall most people will never climb.