Earlier quoted context omitted.
I'm mostly thinking about all the stuff that goes wrong. Corrupted data files, server(s) die, monitoring, getting paged, backups, testing restores, yada yada. It works until it doesn't, and then the value you derive from self-hosting is questioned when there's a failure. If you can self-insure against shit happening & like doing so, then it's probably worth it. Mostly just point this out for the potential self-hoster…
If uptime is critical and you don't want this to be a full time job then don't do it... Opt for PaaS. But for me uptime isn't critical, I can happily be down for a few days if needed. It hasn't happened once yet but I can tolerate it were it to happen. Plus this is how I learn. By doing it I learn how to do it and what should be considered. When it goes wrong I learn how to avoid that in future and what I should do t…
As the project started to fade out, I moved to Hetzner Cloud to reduce the cost of standby infrastructure.
It was down for 4 hours in a row several times over these 18 years, but otherwise the uptime was close to six sigma (under 3 hours per year).
It's surprising how rock solid hosting providers are. Can't imagine hosting anything substantial on AWS after all these years.