Self-Hosting Is Not Free: Accounting for Your Own Time

The bill you never see is the one with your evenings on it

We love to tell ourselves a story about self-hosting: cancel the £10/month subscription, run the open-source equivalent at home, and pocket the difference. It’s a satisfying story. It’s also, in cold accounting terms, frequently nonsense — because the one cost we never put on the spreadsheet is the most expensive one we own. Our own time.

I’m not writing this to talk you out of self-hosting. I host more than is sensible, and I’d do it again. But I’ve watched too many people justify a setup on pure financial grounds, then quietly spend forty hours a year keeping it alive while telling themselves they “saved money”. Let’s be honest about the ledger.

Advertisement

When you replace a SaaS subscription with a self-hosted equivalent, here’s what actually goes on the bill that the comparison blogs never show:

  • Initial setup. Reading docs, fighting reverse-proxy config, getting TLS working, the first three things that don’t work. Call it 4–12 hours for anything non-trivial.
  • Updates. Every container, every month, sometimes with a breaking change that eats an evening. A handful of services is a couple of hours a month. A dozen is a part-time hobby.
  • Backups. Setting them up is the easy part. Testing a restore is the part everyone skips, which means their backups are theoretical until the day they aren’t.
  • Incidents. The disk that fills at 2am. The certificate that expired because the renewal cron died silently three weeks ago. The update that bricked the database. These don’t happen on a schedule; they happen when you have plans.
  • Decision tax. The hours spent reading forums about which of four self-hosted photo apps to pick. This is real time, and for some of us it’s the most expensive line of all.

None of these appear in “£10/month vs £0/month”. All of them are real.

Put a number on your hour. It doesn’t have to be your billed rate — use whatever your leisure time is honestly worth to you. Say £20. Now reconsider that £10/month service you replaced. You “save” £120 a year. If standing it up and maintaining it costs you eight hours, you’ve spent £160 of your time to save £120 of money. You are, in pure financial terms, down £40 and you’ve acquired a pager.

This isn’t an argument against self-hosting. It’s an argument against a bad reason for it. The maths above is damning only if money was your sole motive. The moment you value the other things you got — control, privacy, learning, the absence of a vendor who can change terms or vanish — the ledger looks completely different. The mistake is pretending those are bonuses on top of a financial win, when usually they are the win.

After enough years I’ve sorted my services into rough buckets, and the sorting principle isn’t cost — it’s how much the time investment pays back in something other than money:

VerdictWhyExamples
Easily worth itPrivacy or control genuinely matters; low maintenancePassword manager, DNS/ad-blocking, file sync
Worth it if you enjoy itReal ongoing upkeep, but the learning is the pointMedia server, home automation, monitoring
Think hardHigh stakes if it fails; cloud does it better and cheaperEmail, anything family depends on daily
Usually notThe SaaS is cheap and the self-hosted version is a second jobGroup video calls, large-scale collaboration

Email is the perennial flashpoint. People self-host it to “save money” and then spend a weekend a year fighting deliverability and reputation services, all to avoid a £3/month mailbox. If you do it because running your own mail server is a thing you find genuinely interesting, brilliant. If you do it to save £36 a year, you have catastrophically mispriced your weekend.

The healthiest framing I’ve found is to stop calling it “saving money” and start calling it what it is: buying control with time. Once you say it that way, the decisions get clearer. Is this a thing where control actually matters to me? Then the time is well spent, even if the spreadsheet disagrees. Is it a thing I’m hosting out of reflex or thrift? Then maybe the £10/month is the bargain, and my evenings are better spent elsewhere.

The corollary is that maintenance time is the real budget, not the money. The right question before adding a service isn’t “can I run this for free” — you almost always can. It’s “do I have the hours this will demand, and do I want to spend them here”. A home lab isn’t constrained by money or by rack space. It’s constrained by how many things you can keep alive before the whole thing becomes a chore that resents you.

Self-hosting is one of the most rewarding hobbies I have, and I’m not stopping. But it is not free, and the people who insist it is are the ones who haven’t priced their own time — usually right up until the 2am disk-full alert teaches them. Host the things where control, privacy, or sheer enjoyment justify the hours. Pay the subscription for the rest, and feel no guilt. The goal was never to spend nothing. It was to spend deliberately.

Advertisement

Related Content

Advertisement
Smarc
Written by Smarc

Founder and editor of vo.rs. A lifelong tinkerer who self-hosts far more than is sensible, hardens Linux boxes for fun, and prods the latest AI tools to see what they can really do. The how-to guides here are the notes Smarc wishes had existed the first time round.