> What’s your server’s uptime? Is it highly available? Who cares about uptime, when you use a server alone or with a small team? It can be down for 10 hours an

> What’s your server’s uptime? Is it highly available? Who cares about uptime, when you use a server alone or with a small team? It can be down for 10 hours and you would not even notice. You don't understand what you need. > How often do you patch? I patch the machine multiple times a week with some "apt update && apt upgrade" which takes literally less then a couple of minutes a week. > Do you test them first? I don't need to because I'm using ZFS and make a snapshot before upgrades, so in case of a disaster (which already happened multiple times) I can roll back within minutes, which happened multiple times, once when the machine didn't even booted. > How is your security team in general? Do they monitor for stolen credentials? Do pen-tests? Watch for network scans and attacks? Look for weird traffic patterns? You don't need any of that. If you think you do, you think you are far more important than you really are. Maybe framework authors or super-popular library writers would need to worry about that, but self-hosting makes you an order of magnitude lower chance of being a target. > Is someone always on call? What are they experts in? How do you get support? We might not talk about the same thing... > And that’s not including the network effects of having so many projects in the same site. This is the only valid point you came up with.