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?
I would be happy if I could pay you to just set up and periodically check my setup. I only say that because I would probably want to put together something that cost more than $150. But I am absolutely overwhelmed by what I don’t know. Every tutorial I read gives me more questions than answers.
I just want to self host, share it with a close circle of friends, and keep everyone else’s noses out of my business.
I am absolutely overwhelmed by what I don’t know. Every tutorial I read gives me more questions than answers.
I felt that in the very core of my being.
Looking at my setup, sometimes I look back and wonder how tf I’ve made it this far. Dozens, if not hundreds, of hours of searching, reading, watching YouTube tutorials, and I feel like little has stuck with me. If the boot drive in my proxmox server takes a shit on me before I manage to figure out how to properly back everything up before that inevitable failure occurs, I’ll be back at square one (as in, still clueless and destined to spend dozens/hundreds of hours getting things set back up and configured).
I can say that I am a bit more familiar with the linux terminal now than I was a couple years ago when I first started, so there is some learning and growth taking place. But I’m still just a wee lad still trying to figure out how to simply stand up on my own. And heaven help me if an actual problem arises.
Would you rather pay a higher price per single instance ($100 to fix something you broke on accident) or pay a lower constant price ($10-$20/month) like insurance?
Would you rather get help in the form of a conversation, a custom script someone wrote for you, or by giving admin access to the company to directly fix things?
I would be willing to pay an initial setup fee followed by some maintenance fee. I would expect the initial fee to be significant due to a custom setup/requirements. (I am talking just setup, not cost of hardware/ physical installation).
Unique home network with 2 managed switches.
Self hosted security DVR, automated computer backup, photo backup, network drive for document storage and then self hosting a Jellyfin server along with a torrent service.
(I am sweating just thinking about trying to set that up)
Storage will be a RAID setup where I can just upgrade by throwing a new drive into an open slot and replace (as necessary) existing drives by just swapping them out and server automatically handles the data management.
I have a VAGUE idea of what that takes
Maintenance would cover service calls to resolve problems due to security updates/patches, end of life upgrades, normal planned maintenance type of stuff.
User caused issues should be extra :) (i.e. I was just trying to install a Minecraft server)
Couple hundred bucks, at least, for setup. And that seems cheap.
I would pay $10-20 a month for a maintenance fee after an initial setup fee.
I would MUCH rather give my money to an individual sysadmin than a corporate megalith that will use my membership to force an arbitration clause to any future service of theirs I use. Fuck the mouse. Fuck em all. I tried to do it right and that still want enough for them.
It would make more sense to sell a management service
If we did, would you be comfortable giving the company a root SSH login to manage your system, or would you prefer a more limited method of access?
Neither honestly. However, I am also not really the unskilled user trying to self host
Okay, fair enough, any thoughts on what a good ‘management service’ might look like?
How will you provide long term maintenance of their server for a one time payment of 150$?
How will you provide long term maintenance of their server for a one time payment of 150$?
My current thinking is the margin on the hardware would be intentionally low, essentially the cost of the hardware %+10 for configuring it a bit, installing NixOS, etc.
The business would survive on support and hosted services. Something like $20/month which gets you access to support to answer questions, help configure applications, troubleshoot issues, etc. Possibly rolling upgrades of your installed software on your behalf. Alerts on urgent security vulnerabilities. Could also handle tricky things like custom DNS (email servers, certificates) and off-site backups. I’m not totally sure what all would be included, but the goal is to make money while providing value, not build a garden or rent-seek.
$20 per month would be enough to discourage me. It’s another relatively costly computer-related subscription and I already feel like I’m losing a battle to keep those minimal. There would have to be some very clear benefits for that price.
There would have to be some very clear benefits for that price.
Agreed, it would need to be very clear, and additionally we’d need to plan that a certain percentage of customers would grow out of a basic support offering, either by becoming experts or by growing their install size and complexity.
$20 per month would be enough to discourage me. It’s another relatively costly computer-related subscription and I already feel like I’m losing a battle to keep those minimal.
Understandable. Is there a price you think would be reasonable? What would you want for that price?
So the problem with thin margins on the hardware side is what’s stopping a user from just installing their own OS once they figure out they can do the same thing you’re doing on the same hardware?
Nothing stops them, but that’d be fine. If they buy the hardware they should be able to do what they want with it.
Raspberry pi was able to do it with $35.
Raspberry Pi is not a server. That people use it as one does not mean it’s fit for purpose.
While true I feel like your comment misses the point. A raspberry pi is just a computer, not a magic solution box that’s kept maintained and updated by some guy. Their product isn’t a service, it’s just the device.
The fact that it’s an option that even remotely works is my point. They sell hardware. They don’t support software. The community does that. There is something to be gained from having a uniform platform for learning self hosting responsibly.
A Raspberry pi isn’t particularly great at any one thing. It’s greatest strength comes in bundling everything you need in a box at an affordable price. Once you know where your pain points are then you can build/design a system that overcomes those shortcomings.
Having a starter kit would be an easy way to get more people in the space. Would it cost $35 of course not. Level1Techs made their KVM to meet their own requirements and then the community benefits. To me, this project has that kind of energy. Or at least the potential for it.
Why not just have a script that sets up all of the software one would want to host?
I’m not aware of a script alone that could do it, assuming you bought some hardware that came with Windows and wanted to run Linux. Is it possible these days to install Linux from within Windows? I’ve been flashing via disks for too long now.
I do know that some routers are scriptable, but not all routers are, so it may not be possible to do things like expose a port on the Internet with just scripts on whatever router they have.
If I wanted that I would just buy Synology/QNAP/Zima, etc.
What’s the value-add over just buying a SFF PC?
Probably not much for people on a self hosting community, but those that want to get away from subscriptions and steal your data as a service cloud providers that might need some reassurance that they’ll have a working system.
I assume “SFF PC” means “Small form-factor personal computer”.
The value add is not having to make a large number of technical decisions. IPv4 vs v6, which firewall rules to use, port-forwarding vs DMZ, flavor of Linux, partition scheme, filesystem type, application packaging system, and on and on. For many people they don’t care about these decisions, they want “to put something on the Internet” and do it safely. While safety isn’t a binary, and engineering is full of tradeoffs, an experienced practitioner can answer many of these questions reflexively and come out with good enough answers for some customers.
In the end the customer should be able to dig in and change whatever they want. But I want to see if flipping the decision dependency around will help. IE, start with stuff that works, then change things, rather than start with parts and make all the decisions before anything works.
Only if it didn’t have an insane markup for being pre-built.
Market to tax funded institutions. If you can market “self hosted” as cheaper and easier than mother solutions you’ll have guaranteed clients for a long time.
That’s an interesting idea I hadn’t thought much about. I’ve been more focused on individuals than organizations. Do you have experience with tax-funded institutions? I assumed they generally have strict procurement rules and long support contracts with large established players by policy.
I’d probably buy it.
Do you already have an idea of what kinds of things you’d want to run on it?
No. People who want the benefit of self housing without worrying about hardware will rent a vps or something simpler. The hard part of hardware isn’t the purchase, it’s the maintenance.
Also, why the separate router?
I agree with this. Self-hosting requires the user to understand their network, their software, how it all interacts.
If you provide a hardware product and call it a solution, people are going to expect a turn-key solution like a plug-and-play router.
You’re going to end up supporting a bunch of newbies who, by no fault of their own, can’t tell you an error code in the console let alone whatever UI you give them.
I think a better solution would be a course that walks newbies through self hosting.
From reading the comments, I think you could be a lot leaner by selling the $100 setup fee, and telling people which “kit” is supported, and they buy that on their own.
That way you don’t have to deal with any of the physical infrastructure of buying/selling/storing hardware, and people can do some customization.
However I do think you’d need to put some restrictions in place so that people don’t buy cheap crap that doesn’t work and expect you to set it up and support it. They have to buy the kit or other compatible hardware.
I’m not sure what services you’d support, but personally I’d be interested in something like a personal introduction and setup of
- docker
- proxmox
- yunohost
- backups / restore (practice restoring)
- smb shared folder
- pihole / pivpn (can you have wire guard and openvpn setup at the same time for different uses?
Maybe migration of
- nextcloud
You could make different prices depending on what service they want, kind of like a bike stop.
I wouldn’t want a perpetual subscription, but I could stomach something like $100 setup + $5/mo for limited support for a year.
Best thing for me is that community support also exists for all these things too, but it’s hard to do it on your own sometimes.
I think this needs to exist, but as a community supported system, not as a commercial product.
Pick a set of open technologies - but not the best, lightest weight, just pick something open.
Come up with a security architecture that’s reasonably safe and only adds a moderate amount of extra annoyance, and build out a really generic “self-hosted web hosting and VM company-like thingy” system people can rally around.
Biggest threat to this, I think, is that this isn’t the 90s and early 2000s any longer, and for a big project like this, most of the oxygen has been sucked out already by free commercial offerings like Facebook. The technical family friend offering to self-host email or forums or chat no longer gets gratitude and love, they get “why not Facebook?”
So… small group effort, resistant to bad actors joining the project to kill it, producing a good design with reasonably safe security architecture, that people can install step by step, and have fun using while they build and learn it.
I think a possibility is a series of open source anvil or nixos scripts that you can run on most hardware with minimal changes, in an extendable architecture of some kind to add or remove functionality and they perhaps get maintained by the community or some structure of the kind of Linux distributions.
This could enable people with minimal skills set up and maintain a reasonably useful but secure environment just by changing a few variables.
nixos scripts
What’s a nixos script?
Nixos is an os that’s defined by its config stored in .nix files. Everything is defined here all the software and configurations. Two people with the same script will have the exact same os.
Any changes you make that aren’t in the scripts won’t be present when you reboot.
You could maintain a very custom linux distribution (kinda) by just maintaining these config scripts.
So a user wouldn’t need to install all required software and dependencies. They could get a nixos and the self-host config and adjust some settings and have a working system straight after install.
I think this needs to exist, but as a community supported system, not as a commercial product. … The technical family friend offering to self-host email or forums or chat no longer gets gratitude and love, they get “why not Facebook?”
I think this is a great point, it doesn’t help much to create a business that ends up with the same incentives and the same end-game as the existing systems.
So… small group effort, resistant to bad actors joining the project to kill it, producing a good design with reasonably safe security architecture, that people can install step by step, and have fun using while they build and learn it.
That is precisely what I’m looking to build. I don’t want to get rich, I want people without 10 years of industry experience to get some of the benefits we have all been able to build for ourselves.
We already have that, the first problem is we have like a dozen of them, a few are even well supported. The second problem is that usually the technical knowledge required to set up the systems are still lower than the technical knowledge required to keep it running.
I’ve been struggling to wrap my head around a good security architecture for my mspencer.net replacement crap. Could I bug you for links?
I figured out a while ago to keep VM host management on a management VLAN, and I put each service VM on its own VLAN with heavy, service-specific firewalling and a private OS update repo mirror - but after hearing about ESXi jackpotting vulns and Broadcom shenanigans, I’ve gotten really disheartened. I’d love some safe defaults.
It sounds like you’re getting into the keeping it running phase.
First, going back to your previous comment, self-hosting email is difficult. It’s not hard for a small provider to end up blacklisted and you’re probably kind of just done at that point and it will feel very unfair. I get that it’s a fun set of technical challenges, but you couldn’t pay me enough to help someone self-host email.
Second, guessing, but it sounds like you may be trying to expose your services directly and doing a lot to make that work which goes against what most would recommend for hosting your own services. Big companies don’t expose their intranet like that, follow their example. Almost every guide or system is going to warn against that. If you’re going to host more than one thing, highly recommend focusing on minimizing entry points and looking into a VPN-like solution for accessing most if not all of your services. Still spend time on securing your intranet, but most of your risk is going to come from how hard it is for people to get past the front door (or doors).
What is the aim? People who want to get into it, but does not know how, or experts? Think half of the attraction of selfhosting is the diy aspect.
What extra would this bring if people can just buy the parts cheaper?
And for those who only want the out of the box experience why would this be better than, let’s say a beestation? (Yeah price, I know, but you obviously would not have the same support level.)
What is the aim? People who want to get into it, but does not know how, or experts? Think half of the attraction of selfhosting is the diy aspect.
I don’t disagree, and I would imagine what I’m offering would only be useful to people who are very early and don’t yet know they enjoy the DIY aspect.
The aim, though, is this: I’ve enjoyed self-hosting. It’s given me some powers that most people don’t get to have who aren’t also technical professionals. I’m also deeply frustrated by the environment created by the various major tech companies. If I can, I’d like to lower the barrier for people to get some of those powers without having to become experts and to make it more feasible for them to do what they want to do, rather than just what they are permitted to do.
What extra would this bring if people can just buy the parts cheaper?
Much shorter time going from “how can I control some of my own data” to "I’m running NextCloud, and its kinda like iCloud/Google Drive/Whatever Microsoft does and it’s running right here under my control! Not everyone knows the path from buying parts online to having a working reverse-proxy and reasonable firewall rules. Also, standardization makes it much easier to support people, which is really what the business would be doing.
why would this be better than, let’s say a beestation?
I knew about Synology, but as a NAS product, which assumes a certain familiarity with backup schemes, etc. Kind of a prosumer-only thing. The Beestation is new to me, thanks for the tip. Quite possible what I’m proposing would have some overlap and compete with it, I’ll have to read up on it.
The hypothesis is that $150 of equipment to avoid dozens of hours of software configuration
OK fair try, but you also need to sell me 20-25 TB of disk space on 5 spindles (plus a SSD for the bootdisk), 64 GB RAM (with a chance to go up to 128) and the CPU must have 16 threads or more.
What kind of workload do you run that makes you confident you need that much hardware? Do you think people just beginning could get buy on 4 cores and 8 GB RAM for a while? How long before you think most people need more?
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.
Why would I need a separate router for that? I’d need to configure the main router anyway.
I would absolutely want the extra router because most people have one from their service provider. For self hosting, you want an additional router with your own software.