New to this? You're in the right place. This post doesn't assume you know what "hosting" or "self-hosting" mean. If a word needs explaining, it's explained right where it shows up.
The one concept everything else builds on
Every website or app you use lives on a computer somewhere — it doesn't just float in the abstract "internet." That computer is always owned and run by someone, and that someone is responsible for keeping it on, keeping it secure, and fixing it when it breaks. "Hosting" is just the word for whoever's computer that is, and what it takes to keep it running.
Most of the time, you don't think about this because a company you're paying for a service (Slack, Dropbox, Google Drive) handles it entirely — you never see the computer, you just use the app. "Self-hosting" means choosing to be that company yourself — renting a computer, putting the software on it yourself, and taking on the responsibility that came with it, in exchange for not paying a subscription and having full control.
Why a business would choose to do this
Team chat and file-sharing tools charge per person, per month, forever. For a growing team, that adds up fast — often into the thousands of dollars a year. Self-hosting swaps that ongoing per-person cost for a much smaller, mostly-fixed cost of renting one computer, because the same rented computer can serve the whole team no matter how many people are on it.
The tools themselves are usually the exact same kind of thing you already know: a self-hosted team chat tool works like Slack or Microsoft Teams — channels, direct messages, video calls. A self-hosted file tool works like Google Drive or Dropbox — upload, share, sync, edit documents together. The difference isn't what the tool does; it's who's running the computer it lives on.
What you're actually responsible for, if you self-host
This is the honest trade-off, because overselling it doesn't help anyone: a company like Google or Slack handles a long list of unglamorous but important tasks behind the scenes — keeping intruders out, making sure your data survives if something breaks, keeping traffic encrypted so nobody snooping on the connection can read it. When you self-host, that list becomes your job (or your IT team's), not automatically handled for you. Concretely, that means things like: closing off every access point to your rented computer except the ones you actually use, getting a valid security certificate so the connection is encrypted, turning on automatic backups, and keeping an eye on whether the computer is actually healthy.
None of that is exotic — it's mostly a one-time setup, plus periodically checking that it's still working — but it's real work that doesn't happen unless someone deliberately does it.
What this isn't
An honest note, because overselling doesn't help anyone: self-hosting isn't free, and it isn't "set it up once and forget it." You're paying for the rented computer every month, and you (or someone) owns the security and reliability work a subscription service would otherwise have handled invisibly. It's a genuinely good trade for a lot of small and mid-sized teams — but it's a trade, not a free lunch.
Ready for the deeper version?
Everything above is the plain-language shape of a real, step-by-step technical guide to actually doing this — deploying, securing, and maintaining a self-hosted chat tool and file-sharing tool. If you want the real detail — exact setup commands, security hardening steps, and real cost comparisons — the full version is here: Self-Host Rocket.Chat and Nextcloud on DigitalOcean: Step-by-Step Guide.
If this was your first time reading about hosting and self-hosting, you now know enough to follow that post — and enough to tell whether self-hosting would make sense for your team.