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.

Raspberry pi was able to do it with $35.

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.

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.

If it came bundled around a bunch of DIY guides explaining the hows and the whys, it’d be far more appealling

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”.

Hard agree. In fact, I think there’s a market for JUST the guides. It’s true that there’s a TON of guides out there already, from old blogs to YouTube, but the issue is: all of them start or end with: “your use case might differ, so perhaps this solution isn’t for you.” Or “make sure this setup is compatible with your specific hardware”

For example: I want to set up some sort of backup/cloud storage type system. Well there’s about 1400 ways to accomplish that. I can easily just grab one and go, but I’ll always wonder- should I have done this a different way? Would my life be easier/more secure if I chose a different set up?

So offering hardware that is compatible with whatever “stack” of services included would be a huge plus. Sorta like getting a raspberry pi and following a specific raspberry pi tutorial- you know the issues you get aren’t gonna be due to incompatibility.

I think it really boils down to the scale of one’s home lab- are you just tinkering to get some skills and make something cool? Or are you hoping to do something much much bigger? Different software solutions fit those extremes differently.

Sorry, got off rambling there. I guess I’ve been down the home lab hardware/software wormhole for too long these last few weeks.

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.

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.

People who want the benefit of self housing without worrying about hardware will rent a vps or something simpler.

That’s certainly an option. I think of dedicated hardware as working for several different people, some of which care a great deal about not using a VPS provider because they don’t trust them with their data, or don’t trust them to be around for a long time, or don’t trust them not to raise the prices.

The hard part of hardware isn’t the purchase, it’s the maintenance.

I’m inclined to agree, but I’ve been doing hardware for a long time as a hobbyist and I sometimes forget how far I’ve come. It sounds like you might be somewhat like me in that regard. I’m often surprised when people see assembling system parts and flashing an OS as a complex, inscrutable task.

What do you see as the hard part of maintenance? Scheduling time to do it? Unexpected errors or failures?

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.

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.

Which problem(s) are you trying to solve? The networking issue of firewalls and port forwarding?

Within the scope of this question, yes. Also properly configuring IPv6, though that’s just to achieve the same things that port forwarding enables.

The admin tasks of installing and configuring applications?

That’s also on my list, but I was trying to keep the question focused. Do you think the answer makes a difference? In other words, if it was just networking would it be not worth it, but networking and application management would make it worth it?

Good point, I should have mentioned the plan is to sell support.

Was my first impulse too, but looking at their app selection now, it seems kind of … inutile? Unsexy? Old?

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…

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.