Would you buy "self-hosted in a box" hardware?

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.

Isn’t that basically just a commercial NAS?

Is it? I haven't bought one, nor have I built a TrueNAS box. I've heard from folks that run applications on a NAS, particularly VMs and containers, but my understanding is that your price-per-unit-compute is really high since that's not what it's optimized for. I've got an old Zyxel NAS, it's quite low-end, and I can't run anything beyond NFS/Samba/audio streaming.

you can just plug the NAS in anywhere and you’re golden.

Do they have some kind of VPN or TURN system? I'm expecting that customers will want to access the device outside of their LAN.

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

How beefy? Multiple CPU? If you could buy 4 boxes and have them load balance would that be interesting, or do you have a strong preference for single-box compute?

I could absolutely be wrong here, that’s just my $0.02.

Thanks, your $0.02 is exactly what I'm looking for!

For once I'm #1 in something 🥳

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.

I appreciate your thought process here! Where did you end up as far as self-hosting?

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.

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.

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.

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?

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?

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?

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.

Although any commercial business will be dead or the new problem to avoid in 15 years.

This sounds like an interesting point, could you expand it a bit? Are you saying that there's no way this kind of business will last that long, or if it does it'll become something bad?

Do you still need help with docker?

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

Is that just a dig on TrueNAS, or is it just a particularly daunting hill in the march up the difficulty curve?

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

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

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?

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.

Thanks, yeah, there's a lot of work for us to do in testing hardware and understanding what a common workload (if such a thing exists) would need.

Do you have any particular evidence that causes you to think the audience would be niche or wouldn't want to pay subscriptions? I can understand if this is just an opinion you hold, but if there's data or experience behind it, that would be good to know.

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.

Do you already have an idea of what kinds of things you'd want to run on it?

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?

These are great points, and I fully agree. I'd be interested in knowing what kind of license or corporate structure or contract would give you confidence that the organization is worth investing in. I could put all the software out with a really strong Affero license so that you've got the source code, but I get the impression that you, like me, want more than that. Corporations like Mondragon are interesting to me, and I'm aware of a few different tech cooperative organizations. I'm not confident that a cooperative structure alone is enough. Yes, it helps avoid the company taking VC money, shooting for the moon, failing, and then selling everything that's not clearly legally radioactive. But it doesn't protect you against more insidious forces like the founders selling to private capital and adjusting the EULA every few months until they have the right to sell off your baby photos.

I've been batting around the idea of creating a compliment to the "end-user license agreement" - the "originating company license agreement". Something like a poison pill that forces the company to pay out to customers in the event of a data breach, sale of customer data, or other events that a would-be acquirer may think is worth it for them.

I'm just not sure yet what kinds of controls would be strong enough to convince people who have been burned by this sort of thing in the past. What do you think?

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.

this price point is not realistic even for used equipment, not including RAM or storage

I'm doing experiments currently on a refurbished Intel i5-6500 with 8Gb DDR4 and a 0.5Tb SSD. It's tiny, quiet (~45 decibels) and so far runs ~8 watts idle, 25 watts normal usage. I haven't stress-tested the power draw. The router I'm testing with is a Mikrotik hEX lite 5. That's around ~$150, though clearly if you are accustomed to more "rack-mount" style homelab these will seem very modest.

What I'm testing for now is getting representative loads on the devices to see how they perform.

I’m not really sure what value add you are bringing to the table that one wouldn’t get from just buying used hardware from an office surplus and if one is very inexperienced in self-hostong, looking into something like LTT is partnered with like Hexos.

Oh, I totally agree, my value add just isn't there if you are experienced at hosting. The value add is to help people get started, and to keep them running at a modest level. Not everyone wants to experiment with Kubernetes at home or train LLMs. Some folks just want a password manager, a shared calendar, something to organize their tax documents, a pihole, and a Minecraft server for their kids.

I don't follow LTT, I was under the impression it was more hardware reviews for the experienced than tutorials to help people get started.

I've read a bit about Hexos, I'm thinking of some similar things, and it would make sense to work with them. I'm excited for their coming beta.

A small home media server running off a raspberry pi could be that cheap.