Uptime isn't the hardest part about running a solo SaaS shop -- you can solve it by a) bringing an appropriate amount of professionalism to engineering choices

Uptime isn't the hardest part about running a solo SaaS shop -- you can solve it by a) bringing an appropriate amount of professionalism to engineering choices and b) choosing to found a business which has appropriate uptime constraints relative to your resources. Don't do analytics or infrastructure software where a 15s blip in your availability causes hundreds of pagers to go off. There exist many things businesses use which have markedly lower uptime than every SaaS a HNer will ship -- remember, businesses are built around most of their vendors having five twos. (That's a joke, but it isn't a joke.) The harder part about running a solo SaaS company is building revenue takes _a very long time_, particularly if you're new at this. Most of my peers take ~18 months to hit the ~$10k revenue number that lets them durably transition to running the business as the full-time gig. If you want to run a one-person shop which creates value substantially related to software, but you don't want to bite off the complexity of writing and selling a SaaS app for your first rodeo, I'd recommend a business model like productized consulting (the glide path to shipping a SaaS app!), selling infoproducts, or selling some sort of addon to an existing software ecosystem (WordPress, Shopify, etc).