Field Notes
When not to self-host
I run a lot of services at home, and I love it. I also pay for a handful of things I could technically host myself. Knowing where to draw that line is as much a homelab skill as setting up a reverse proxy.
Self-hosting is about control. But control comes with duties: updates, backups, monitoring and being available when something breaks. For some services those duties are a pleasure. For others they are a burden that outweighs the benefit, or a risk that lands on people who never agreed to it.
The questions that decide it
- What happens if it is down for a day? If the answer is "mild annoyance", self-host freely. If it is "someone misses a payment, a job interview or a medical message", think hard.
- What happens if I am away for two weeks? If the service needs you to keep running, it needs a plan for when you are unreachable.
- Can I keep it patched? Not this month. For years.
- Can I restore it? From the off-site copy alone, on different hardware, without guessing.
- Does it need to be reachable from the internet? Public exposure multiplies the maintenance burden and the risk.
- Is the data sensitive? Sensitive data is a reason to self-host, but only if you protect it at least as well as a provider would.
- Is it fun or educational? Those are perfectly good reasons on their own, for services that nobody else depends on.
What I leave to others
The clearest case. Residential connections are widely blocked by receiving mail servers, deliverability needs ongoing attention, and mail servers are under constant attack. I own my domain and pay a small monthly fee for a hosted mailbox on it. If I ever leave the provider, my address comes with me. That is the part of email worth owning.
Public websites
My personal site and the household's shared photo album for distant relatives do not run at home. They run on a small rented server, isolated from my network, or as static pages on a hosting service. A traffic spike, an attack or a vulnerability in public software then affects a disposable server, not my house.
Authoritative DNS for my domain
My registrar's DNS service is reliable, distributed and free with the domain. Running public DNS from home would add risk and a single point of failure with no benefit to me.
Anything that must never go down
I cannot offer high availability from one house with one internet connection and one person on call. If a service truly cannot tolerate downtime, it does not belong solely in my lab.
Things that are a judgment call
- The password manager. Self-hosting one is very satisfying and keeps your vault on your hardware. It also makes your lab responsible for the one thing you need to recover everything else. If you self-host it, keep an encrypted export outside the lab and practice recovering from it. If you are not sure you can, a reputable hosted manager with end-to-end encryption is a perfectly sound choice.
- Family calendars and contacts. Wonderful when they work. If your household's day depends on them, give them the same backup and monitoring attention as anything critical.
- Collaboration suites. Very capable and very large. Keep one only if you will patch it promptly every time.
Things that belong at home
To balance the list: some services are clearly better at home for most of us. A photo library that keeps family pictures on your own storage, a file sync hub on your NAS, a notes system in plain files, a feed reader that respects your attention and home automation that works without the internet. These are where data ownership pays off most, and where the downside of an outage is small. Our Self-Hosting Services guide covers how to run them well.
Do not become the single point of failure
The quietest risk in a household homelab is the person who built it. If you were unavailable for a month, could anyone else get to the family photos, reset the internet or find the password vault?
- Write a one-page household guide: what each service is, what to do if it is down and who to call.
- Store recovery material where a trusted person can reach it.
- Make sure the internet works without your lab. If your firewall or DNS filter fails, can someone plug the provider's router back in?
- Keep critical family data exportable to ordinary formats that do not need your servers to read.
Self-hosting is at its best when it makes a household more independent, not more dependent on one person. Choose what to run with that in mind, and you will enjoy the services you keep far more.