A few years ago, self-hosting was considered a niche activity reserved for Linux enthusiasts and system administrators. Today, it is becoming a mainstream choice for individuals, small businesses, and organizations that want more control over their data and infrastructure.
### What Changed
Several forces converged to make self-hosting more accessible:
- **Docker and containers** made deploying complex software stacks as simple as running a single command.
- **Affordable VPS providers** brought the cost of a private server down to a few dollars per month.
- **Privacy concerns** around major cloud platforms pushed users to look for alternatives.
- **Projects like Nextcloud, Mattermost, and Bitwarden** built polished, self-hostable alternatives to popular SaaS products.
### What You Can Self-Host Today
The range of software available for self-hosting has expanded dramatically:
- **File storage and sync:** Nextcloud, Syncthing
- **Password management:** Bitwarden, Vaultwarden
- **Team messaging:** Mattermost, Element
- **Note-taking:** Standard Notes, Joplin
- **Media servers:** Jellyfin, Plex
- **Git hosting:** Gitea, Forgejo
For most of these, a Docker Compose file is all you need to get started.
### The Trade-offs Are Real
Self-hosting is not without cost. You are responsible for updates, backups, uptime, and security. A misconfigured server can expose your data more than a managed cloud service would.
The honest answer is that self-hosting is the right choice for some use cases and not others. The key is understanding what you are taking on.
### Why It Matters for Software Discovery
For a software archive, self-hostability is a first-class attribute. Whether an application can be self-hosted changes the privacy model, the cost model, and the trust model entirely.
**Knowing that an app is self-hostable is as important as knowing its price or platform support.**
