Why I self-host things even when easier options exist


Why I self-host things even when easier options exist

There's a ready-made service for just about everything. Email from a big provider, files in the cloud, online voting on a subscription plan with a colourful dashboard. Three clicks and it works. No server, no updates, no responsibility. Sounds reasonable.

And yet, sooner or later, there's a server in the basement or a VPS in somebody else's data centre. Not because it's easier. Because at some point, easy stops being enough.

When convenient becomes complicated

Cloud services work brilliantly as long as you do exactly what the provider intended. Standard use cases are their bread and butter.

The trouble starts when real life gets involved.

A club meeting suddenly needs a feature that only comes with the next subscription tier. A provider changes the interface just before an important event. Or maintenance happens at precisely the wrong time. Statistically rare, perhaps. Remarkably familiar in practice.

That's not malice. It's what happens when software has to serve huge numbers of customers.

Self-hosting is rarely just a technical decision

From the outside, it looks like a technology obsession: Docker, Proxmox, reverse proxies and other things that people will explain only after making you promise not to run away.

Actually, it's about something much duller: having some control over when things break.

If a system fails, I'd at least like to know why. A status page telling me that other people are having the same problem isn't always much comfort.

The romantic phase doesn't last

At first, self-hosting is fun. Everything is new, everything gets optimised and every little CPU spike gets watched. For a while, you feel like you're running a miniature data centre.

That phase ends. Reliably.

Eventually, you realise the goal isn't maximum control. It's having to touch things as little as possible. Good infrastructure is invisible. If you're constantly working on it, something probably isn't right.

Why not host absolutely everything yourself?

Because that's exhausting, too. Hosting video calls sounds fantastic until you discover that globally distributed infrastructure exists for a reason.

Self-hosting is worthwhile when your workflows are unusual or when control and availability really matter. Not on principle and certainly not to prove something. Servers don't have egos. Their operators sometimes do.

What changes over time

My focus used to be on doing as much as possible myself. Now it's about having as little maintenance as possible.

A cleanly separated setup runs quietly for months. Updates happen deliberately. Backups work in the background. That's when self-hosting starts making sense.

Not because it's spectacular. Because nothing happens.

Conclusion

There are always easier options. Often they're the right ones.

Self-hosting isn't attractive because it means less work. It's attractive when you need things to behave predictably and accept that you can't outsource the responsibility.

In the end, this isn't about servers or software. It's about technology staying out of the way when you need it.

And when everything runs smoothly, you might even forget the server exists. Until the next update.

Previous Next