Yes, I'm a solo founder and I can take a break and sleep etc. The key to me is to keep thing simple and have it fail in a predictable way by not mixing server

Yes, I'm a solo founder and I can take a break and sleep etc. The key to me is to keep thing simple and have it fail in a predictable way by not mixing server roles. I run an email forwarding service so I clearly say this is incoming mail server, this is outgoing server. For each of them we have a pair of 2 with automatic failover. Keeping stack simple so if they failed, only a portion of it failed. Example, it's ok if the landing page is down. People can still send and receive email. If the mail service down, we have a check on our homepage to say that our mail service is down and we're working on it. In other words, try to design the system in a way where you have a clear boundary between components of system, so when they failed you know exactly what failed and can do thing like restart to fix, scale up server(cpu/mem) to fix it.