Why not just have a script that sets up all of the software one would want to host?
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
Maybe migration of
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.
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.
Needs serious market research to not flop out of the box.
An interesting customer base might be small communal organisations. At our local scouts troop I had a discussion with a friend, who is also in IT. His idea (not fleshed out) was to provide small local organizations with a stack of already configured open source software to support the typical needs of such organizations (like a wordpress website, a nextcloud for file storage and common calender, limesurvey for surveys and event registration, mailman3 for mailing lists,...). Depending on the needs you could sell the initial setup process (your personal work in setting up and skill transfer) or ongoing support. Though such organizations normally don't have much money to give away. So probably its not really worth your time financially (though probably really appreciated in the community).
I probably would. However it has become increasingly obvious that the flaws with solutions so far have been in the organisation. Not so much the particular hardware or software. If I'm going to buy something I'd like some hope that it'll be there in 5 or 10 or 20 years. So please if you go serious with this, look into worker-owned organizations because I'm tired of dodging profit-maximizing traps and pretend-non-profit landmines. If the people building and supporting the thing aren't the ones deciding what to do with the revenue and profit, you're the only one doing it and you're going to make mistakes that will hurt them and us. And then you become a landmine to dodge.
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 don't know enough to say what the structure should be but this should not be possible:
But it doesn't protect you against more insidious forces like the founders selling to private capital
It implies that the founders have more voting power and ownership than the rest of the people in the org. In my mind, everyone should have an equal vote, which should prevent a sale on the whim of the founders or another minority group. If a sale is in the cards, a majority of the people in the org should have to approve for it to proceed. And this shouldn't be advisory but a legal barrier to pass.
If I were to start a firm today, I'd be looking into this because not only this is the kind of firm I'd like to work in, but I think so would quite a few people in software. And those aren't the dumb kids.
I can also say that as a customer, the few worker co-ops I've able to buy things from give me a much more trustworthy impression than the baseline. They just behave differently. Noticeably more ethically.
But it doesn’t protect you against more insidious forces like the founders selling to private capital
It implies that the founders have more voting power and ownership than the rest of the people in the org. In my mind, everyone should have an equal vote, which should prevent a sale on the whim of the founders or another minority group.
I'm not confident that simple democracy is enough. While I do expect that a one-worker-one-vote system would make it harder to sell out, it's still possible. I do think that a cooperative has many benefits. I just want to make it fatal to the business to go down certain dark paths: selling user data, seller user compute, selling user attention, etc.
I wish there were more examples of functional high-tech cooperatives I could learn lessons from.
If I were to start a firm today, I’d be looking into this because not only this is the kind of firm I’d like to work in, but I think so would quite a few people in software. And those aren’t the dumb kids.
I strongly agree with this sentiment.
Purely on the product side, if I decide to buy it, I wouldn't buy it for myself. I'd buy it for friends and family who are not that tech literate. Either to make my life easier to give them self-hosted services, or ideally for themselves to be able to do so. I want this product to be a non-shitty, open source "Synology," from a firm I can trist to support it for a very long time. Doesn't have to have that form factor. And I'm totally fine with an ongoing subscription. I'd like to be able to say - hey friend, buy this from ACME Co-op and sign up for their support plan. Follow the wizard and you'll have Immich, Nextcloud, etc. A support plan might include external cloud HTTP proxy with authentication and SSL that makes access trivial. Similar to how Home Assistant's subscription (Nabu Casa) works. It could also include a cloud backup. Perhaps at a different subscription rate.
I admire the thought of lowering the barrier to entry to start self-hosting for "normies". Not sure where you are located, but where I am, this price point is not realistic even for used equipment, not including RAM or storage. 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.
A small home media server running off a raspberry pi could be that cheap.
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.
I recently upgraded my homelab/self-hosting server from an old Dell T410 with dual X5650's (2 - 6 core/12 thread CPU) and 24 GB ram to an old Dell Optiplex (7020 I think) with an i5-4590 (4 core/4 thread) and 32 GB ram. Its barely enough for a proxmox host with 5 VMs; but way faster than the old T410.
If you are offering some sort of self-hosting box, would it be bundled with some sort of software for someone to easily spin up whatever services they want?
Are you going to be able to make money at the $150 mark with all this hardware and configuration? If you are targeting people who are new to self-hosting, it will need to be a complete package (will need to have ram and storage installed).
The tech savvy will just buy a Raspberry Pi and install yunohost on it.
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!