There are so many servers and apps being installed by Sovereign that I'm certain few would be able to keep it secure (<a href="https://github.com/sovereign/sovereign/wiki/Software-used-by-Sovereign" rel="nofollow">https://github.com/sovereign/sovereign/wiki/Software-used-by...</a>). The big win for the cloud is that you're paying a fraction of the cost for access to a, typically, enormous security and operations team. If you want to build software like this that allows people to self-host, you need to scale down what you deploy to what a single person can reasonably manage. This isn't it.<p>Fun todo: Install this somewhere, nmap it for open ports, then ask "How many of these services had a remotely exploitable CVE in the last year?" "If one of these services had one tomorrow, would I know to patch it and take action faster than someone would takeover my box?" I don't see any containment mechanisms on any of these services beyond what's included by default so a compromise of one service likely leads to total compromise of the entire box.<p>I had to think about this a lot with AlgoVPN (<a href="https://github.com/trailofbits/algo" rel="nofollow">https://github.com/trailofbits/algo</a>), and we built a system with no out-of-the-box remote administration, strong isolation between services with AppArmor, CPU accounting, and privilege reductions, and limited third party dependencies and software. You can't count on a full-time, expert system administrator.