And if you get hit by a car? Or worse --- maybe you get married and have kids<g>?
One big reason people *buy* service is sustainability/longevity/redundancy.
There are no absolute guarantees but I think most commercial endeavors nowadays would bet on AWS/Google/MS/Apple over "Hosting by Joe and Friends".
Personally, I'm betting on those who are highly incentivized and have the resources and structure needed to sustain reliable service.
I maintain 3 copies --- no hosting required. One copy is strapped to my wrist at all times so it is always just as safe as I am --- if not safer.
This is the "1" part of my 3-2-1 backup strategy.
Can you say more? What solvent would I use? What material would I choose to make the parts from? (I would be using a service to print the .stl file.)
Also, FWIW I am married and have kids. Hasn’t stopped me from homelabbing.
I’d do it for free. I’ve long been frustrated that I have more reliable infrastructure in my homelab than most companies I’ve worked for, and that none of them have any interest in shifting out of the cloud.
I don’t see a market for it, though. Most people are generally happy with Google, Apple, etc. to host their stuff, and I get it - it’s quite reliable, integrates with the rest of their respective products nicely, and Just Works. Add to that the economies of scale, and it’s a non-starter unless you find a niche group of people.
Google One is $99/year for 2 TB of storage. For me to have confidence in uptime to offer public storage, I’d need at least 4U of colo rack space, and ideally 6U (2x 2U for HDD servers, 2x 1U for hosting applications in HA-ish). That would cost a few hundred USD/month, not to mention an initial outlay of tens of thousands of dollars for servers and drives (mostly the drives… high capacity enterprise-rated HDDs aren’t cheap). And that’s only for one site - ideally, of course, there are at least two, or at the very least, off-site backup like rsync.net.