I’m considering a business plan for people getting in to self-hosting. Essentially I sell you a Mikrotik router and a refurbished tiny x86 server. The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.
The hypothesis is that $150 of equipment to avoid dozens of hours of software configuration is a worthwhile trade for some customers. I realize some people want to learn particular technologies and this is a bad fit for them. I think there are people out there that want the benefit of self-hosting, and may find it worth it to buy “self-hosting in a box”.
What do you think? Would this be a useful product for some people?
Interesting, so if you got hardware and it came with guides, what kind of guides would you want? I would assume something layered. At the top is just “I want to install these 5 apps and use them, I don’t care how it works” and in the middle is “I’m ready to SSH into the router and create some VLANs for fun” at the bottom is something like “I want to flash my own firmware with appropriate certificates for secure boot and my own root chain of trust on the server hardware”.
The guides, basically a quick and dirty walkthrough on setting it up, hopefully a few explanations about things, and a handful of common troubleshooting tips. Also pointers to a handful of communities that have helpful info in case something obscure pops up.
Basically, teach a man how to fish, as opposed to giving him a couple.
I think a lot of people who would otherwise dabble with a DIY home server never try because it’s pretty technical (beyond typical ‘build a pc’ stuff) so I think the education that would come with the hardware would be appreciated by many. Help them get their foot in the door by making the dive a little less scary. Nothing too over the top but point them to the places where people hang out discussing the more technical crap for when that day comes
I could see this being a use case for a NixOS deployment where your company manages the configuration file and versioning of the system, as well as providing support. Over time, I’d you’re diligent about building documentation based off of each support request, you’ll end up with a personalized guide. And if your customer decides take a break or quit entirely, they have a configured system that doesn’t lock them in into something too esoteric.
Disclaimer: I only know of Nix, never used it because I just don’t manage that many machines to be worth my while to learn it.