Self-hosting is often presented as an answer to every problem. I do not think it is.

A service can be open source, privacy-friendly and technically interesting while still being the wrong thing for me to operate. Every service adds updates, storage, monitoring, backups, permissions and another failure mode. The aim is not to recreate every cloud product at home. The aim is to keep control where control is valuable without turning the homelab into a second job.

I do not self-host everything

I am cautious about services that handle especially sensitive information, need constant availability or have a large operational burden. A hosted provider can be the more sensible choice when it offers better security, accessibility or recovery than I could realistically provide myself.

That is not a failure of self-hosting. It is the point of making a deliberate choice instead of following a slogan.

Email is where I draw the line

I deliberately do not self-host email. Reliable delivery requires reputation management, filtering, authentication, security, storage, backups and recovery. AI-powered filtering and mailbox automation add another layer of risk because sensitive messages may be processed by systems that can be manipulated by malicious content or given too much access.

For me, hosted email with my own domain, clear export options and independent backups is the more sensible choice. That is not giving up on digital ownership; it is choosing not to operate a difficult and security-sensitive service when the benefit is not worth the work.

Questions I ask first

Before adding a service, I ask:

  • What problem does it solve for me?
  • Can I export the data in a useful format?
  • Can I back up and restore it without guesswork?
  • What happens if the project stops being maintained?
  • Does it need internet exposure or privileged access?
  • How often will it need attention?
  • Would I still want to operate it after the novelty disappears?
  • Is a hosted alternative cheaper in time and risk?

If the answers are weak, I do not add it simply because it is popular.

What I prefer to self-host

Self-hosting makes the most sense to me for services where local control has an obvious benefit:

  • personal photos and media;
  • documents and bookmarks;
  • local DNS and network services;
  • monitoring and notifications;
  • backups and recovery tooling;
  • services where a provider could change access, pricing or availability;
  • data that I want available on my own network even when the internet is unavailable.

These still need sensible backups and security. Local does not mean indestructible.

The practical answer

The right question is not “Can I self-host this?” Almost anything can be made to run somewhere.

The better questions are:

Does operating this service improve my control, resilience or privacy enough to justify the work?

Can I leave it later without losing the data?

If the answer is no, I would rather use a hosted service, keep a local export, or not use the service at all.

That is a more useful form of digital ownership than collecting dashboards.