What Self-Hosting Actually Costs (That the READMEs Don't Mention)
Every self-hosted tool’s README says the same thing: “get started in five minutes with Docker Compose.” That’s true, and also the least useful information for deciding whether to self-host it.
The five-minute setup is real. The ongoing cost is the part worth knowing before you commit six tools to a homelab or an internal platform.
What actually costs time, ranked
1. The upgrade you put off, then regret putting off. Every self-hosted tool ships breaking changes eventually. Defer three point releases and the eventual upgrade is a multi-hour project instead of a five-minute one. This was the single biggest time cost across everything reviewed here — not setup, upgrades.
2. Backups you haven’t tested restoring. A backup script that’s never been tested against an actual restore isn’t a backup, it’s a hypothesis. This is the boring, unglamorous work that every self-hosting guide mentions in one line and nobody actually budgets time for.
3. The dependency you didn’t know you’d taken on. Self-hosting Grafana means also running Prometheus (or something like it) means also thinking about long-term metrics storage. Every tool has a shadow dependency graph the quickstart doesn’t show you.
What was and wasn’t worth it
Worth it: Vaultwarden, Gitea, most single-container tools with no external database dependency. Low blast radius if something breaks, and the value (owning your own data) is immediate and obvious.
Worth it, with caveats: Plane, Grafana + Prometheus — real value, but budget real ongoing time, not just setup time.
Reconsider: Anything that needs a dedicated person to run well — Backstage is the clearest example. Below a certain team size, the maintenance cost isn’t paid back by the value, no matter how good the tool is.
The actual question to ask before self-hosting anything
Not “can I get this running” — you can, in five minutes, just like the README says. The real question: “am I willing to be the person who gets paged when this breaks at 2am, indefinitely?” If the honest answer is no, that’s not a reason to avoid self-hosting entirely — it’s a reason to be selective about which tools earn that commitment.