Selfhosted
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:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I think your approach to monetizing towards companies is great and you should totally do that. As someone that works with an RMM everyday and I've tried nearly all the big box ones. They all suck. So seeing something new in this space is great. Especially if it works.
I think restricting the home lab level to 1-3 sites could be a viable path? Maybe even license agreement stating not to be used for business without subscription (you might already do this, I didn't read the license)? I'd expect that to be hard to enforce though.
I did read a bit about the self compiling and think that's a good idea and totally could have signed up with an alias email. But for me, when I want to test something I want it to be a quick docker/k3s deploy. Could you publish your docker containers for home lab, maybe restricting bare metal installs to a license would deter companies from installing due to most in house IT wanting things on VMs or bare metal.