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?
Isn't that basically just a commercial NAS? Go buy a Synology NAS, or get fancy w/ TrueNAS. You don't need an entry-level enterprise-grade router at all, you can just plug the NAS in anywhere and you're golden. You can usually install a few services like Plex/Jellyfin or HomeAssistant alongside the data storage if you like.
If that's not going to work for you, you probably have a good idea of what will work for you. For me, a tiny x86 server isn't going to cut it, because I want a beefier CPU to run CI/CD for my programming projects, so a beefier, modern CPU is quite valuable. That's totally overkill if all you want is a simple streaming setup with 1-2 transcoded streams.
So I think there are two main markets here:
The only other group I can think of is the group that can't afford 1 and doesn't know enough to do 2, but I really don't think that's a particularly big group, and they'd be better off reusing something they already have instead of getting some off-the-shelf solution.
I could absolutely be wrong here, that's just my $0.02.
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.
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 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.
Hi, I'm your customer base.
I'm a complete novice, no network or coding experience, but not afraid of computers either. I'm pretty worried about messing up something serious due to lack of knowledge.
In the end, I didn't choose Synology or the like due to:
lack of robust community support. I've noodled around with Linux for years and learned that community support is essential.
price. I'd pay 10% or 50% more for a good pre-configured system, but not 3-4x more (which is just the general feeling I get from Synology)
lack of configurability. I'm still not sure what I would like to do (and be able). I know I want to replace some storage services, replace some streaming services, control my smart home, maaaaybe access my files remotely, and probably some other stuff. I may want to have email or a website in the future, but that's not on my radar right now.
If there were some plug-and-play hardware/software solution that was still affordable and open, it would be a good choice for me.
What's the value-add over just buying a SFF PC?
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.
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.
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.
Which problem(s) are you trying to solve? The networking issue of firewalls and port forwarding? The admin tasks of installing and configuring applications? The task nobody does of maintaining software and keeping it up-to-date?
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?
If I don't have to fail to understand another "Docker's not that bad | complete beginners' tutorial" video, I'd sign up.
Although any commercial business will be dead or the new problem to avoid in 15 years.
Docker's secret that most "getting started" tutorials seem to miss is docker-compose.yml. Who wants to type these long-ass commands to start containers? I always just create a compose file, and then docker compose up -d.
Dockerfile is for developers, you shouldn't need more than a docker-compose.yml for self-hosting stuff.
what's your plan on teaching these people to maintain their selfhosted instances? Are you selling support? I mean you could script pulling and recreating containers, but without eyeballs on it, that stuff will die eventually.
Oooohhhhh boy. Another one of these 🤣
It's not like a package thing you can sell if you're not supporting it. Then you're just selling hardware at an inflated price. It's not even self-hosting at that point. Why wouldn't you just pay a regular company for a product?
Dual Core ARM Cortex-A7 processor running at 1GHz
1GB DDR3 RAM memory
Doesn't seem like you could self-host a whole lot with that...
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?
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'm not in the market, but I've actually had similar thoughts of building a project on top of NixOS that's focused on self-hosting for homes and small businesses. I recently deployed my own router/server on a BeeLink mini PC and instead of using something like OpenWRT, I used NixOS, systemd-networkd, nftables, etc.
DM me if you want to discuss more. I think the idea has potential and I might be interested in helping if you can get the business model right (even if it just ends up being some FOSS thing).
Only if it didn't have an insane markup for being pre-built.
150$ is rather ambitious for what you are describing as a custom made low power server. Managing to build something... Anything commercial out of new, hell even refurbished parts that has enough horse power to run anything more than a pihole/DNS server at this price point would be a challenge and a half. If you're going refurbished/2nd hand, you're likely gonna spend half of that on just shipping the parts to you.
I believe you are vastly underestimating the price of new low end parts and vastly overestimating the capabilities and availability of old micro servers. I'd say something like this would work at a price range of around 300~400$ (and even that's ambitious imo).
And even then, that's a NICHE audience you'd be targeting. It would be people who don't wanna pay subscriptions, but also don't wanna be bothered to spend a day or 2 figuring out how to set up a simple linux box on an old computer they have. I'm not saying that audience doesn't exist, it's just veeeeery niche.
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 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.)
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!