Self-Hosting Does Not Mean 3am Pages
The biggest myth about self-hosting is that you will be on call constantly. Here is why a well-set-up VPS runs quietly and rarely pages you at all.
The most common objection to self-hosting is that you will be woken at 3am to babysit a server. It is mostly a myth. A VPS set up correctly runs quietly for months. I host a portfolio of products across a handful of boxes, and on a normal week I am not paged about any of them. The pages people fear come from bad setups and skipped fundamentals, not from the act of running your own server. Get the fundamentals right once and the machine mostly runs itself.
Why people believe self-hosting means constant on-call
The fear comes from a few real memories and a lot of secondhand horror stories. Someone ran a server in 2009 with no backups, no monitoring, and manual deploys, and it bit them. Or they read a thread where a managed-cloud vendor was quietly doing the reliability work that the poster then attributed to magic. The story sticks: own a server, live at its mercy.
The reality is that a modern Linux VPS is astonishingly stable. Processes do not randomly die. Disks do not fill overnight if you watch them. The machine reboots and comes back on its own if you configured it to. Most "the server went down" incidents are actually "I never set up the thing that would have prevented this." The problem is a missing practice, not the ownership. I made the fuller reliability case in is self-hosting reliable enough for production.
What actually causes 3am pages
The pages that do happen cluster into a short list, and every one has a boring preventive fix:
- Disk fills up and everything stops. Prevented by a disk-usage alert and log rotation. Five minutes to set up.
- A process crashes and does not restart. Prevented by
restart: unless-stoppedor a systemd service that restarts on failure. One line. - The box gets compromised because SSH was wide open. Prevented by key-only auth, a firewall, and fail2ban, covered in the SSH hardening checklist.
- A deploy breaks production and there is no way back. Prevented by deploying to staging first and keeping the last known-good build.
- A dependency's security update is ignored until something is exploited. Prevented by automatic security updates on the box.
Notice the pattern. None of these are inherent to self-hosting. They are each a one-time setup you either did or skipped. The people who get paged skipped them. The people who sleep fine did them.
Set it up once, then it runs quietly
The work that buys you quiet nights is front-loaded and small. Configure restart policies so crashes self-heal. Turn on automatic security patches so you are not chasing CVEs. Put a firewall in front and harden SSH. Set up backups and, critically, test a restore so you know they work. Add a few alerts on the things that actually page: disk, memory, and whether the site responds. That is a day of work, not a lifestyle.
The alerting piece is what converts fear into calm. You do not sit watching dashboards. You get a message only when something crosses a threshold you set, and the thresholds are chosen so the message is rare and real. I run this without a paid observability vendor, described in self-host monitoring instead of Datadog. The goal is not zero incidents. It is that incidents are rare, caught early, and mostly self-resolving.
The real tradeoff, stated honestly
Self-hosting does add a category of responsibility that managed platforms absorb. That is true and I will not pretend otherwise. If you skip the fundamentals, you will get the pages the myth promises. The honest version is: self-hosting means an afternoon of setup and an hour a month of attention, in exchange for owning your stack and cutting your bill. It does not mean living on call.
Compare that against what you give up going fully managed: cost, control, and the ability to see what your system is actually doing. For a solo operator or a small team, that trade favors owning the box, and the on-call burden is far smaller than the story claims. Run the fundamentals once on HostSSH, fold them into a standard setup you reuse across boxes like one runbook for twenty apps, and the 3am page stays a myth. The server does its job while you sleep, which is exactly what a server is supposed to do.