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
Its perfectly viable to run your support software on your own hardware (whether local or VPS).
I do this for myself, as well as for companies sized from 50-5000 (roughly). Larger ones deploy off my specs. The question to me is what is the plan around it. How will backups be handled? What if it goes offline due to a hardware failure? Do you have backups in place? A cold or hot spare? Multiple machines in an HA configuration? Do you need to go to that level if there is an outage?
I also prefer to make use of solutions with a support model that allows for locally hosted, but has a phone number that can be called. Part of this is because I don't want to field all these calls, part of it is for the comfort of the client that they have a number they can call (or a dedicated email, whatever, the point is a support contact not how they are contacted), and part of it is to support the project.
My wife has a (small) business, I have a small business, and I work for a consulting firm (design and engineering). All three make use of on-prem f/loss, all three pay support fees to those projects who do that (and random annual contributions where possible to those that don't).
So the short answer is: Figure out your requirements and your disaster recovery scenarios, then figure out what option works best for your needs from there. Cloud, VPS, or internally hosted are all viable, and all come with their own pluses and minuses.