Self-hosting

Running a service on infrastructure you control instead of renting it from whoever wrote it. The software is usually the same software; what changes is who is responsible when it stops working.

The claim and the bill

The pitch is control, and it is real: your data on your disk, no subscription, no vendor deciding your feature set, no account to be locked out of. hometube states the standard version of it — “No cloud dependencies, everything runs locally.”

The cost is paid later and in a different currency, which is why the trade is easy to misjudge. Backups, upgrades, TLS certificates, disk pressure, an OS that needs patching, and — the one that actually decides whether a self-hosted install survives — somebody noticing when it breaks. A hosted service has a team paid to notice. A self-hosted one has whoever set it up, and their attention is not on a rota.

The sources here bracket the range. hometube is one container that a household can plausibly run for years. ever-gauzy is a monorepo application with PostgreSQL, Redis, OpenSearch, MinIO and Jitsu behind it, running the payroll-adjacent functions of a business, where the same operator now owns disaster recovery. openpanel sits between them at seven containers, three of which hold state.

Only one of the three writes the bill down. OpenPanel’s self-hosting docs say updating means reading the changelog and applying the changes to your instance, and that managed Redis needs a config flag set by hand. Naming the recurring chore is rarer in this corpus than promising there isn’t one.

Relocation, not removal

The finding this corpus supports most strongly is that self-hosting moves a dependency rather than deleting one, and that the marketing consistently describes the move as a deletion.

HomeTube is the clean demonstration because both halves are in its own README. Storage and playback genuinely move in-house — the library is yours and nothing phones home to watch it. Acquisition does not move, and cannot: the tool needs cookies from an authenticated session because the upstream platform still decides what can be fetched, at what quality, using “encrypted signatures” the downloader has to keep up with. The operator is independent of a vendor’s player and entirely dependent on a vendor’s platform.

The test to apply to any self-hosting claim: name the resource the software needs that you do not own. If there is one, autonomy stops there. anysoftkeyboard passes the test by needing nothing remote at all, which is why it can promise more than either self-hosted service here.

Where the seam runs to other spokes

Operating a service in production — SRE, observability, incident response, the whole discipline of keeping distributed systems up — belongs to ../platform-ops-wiki. This spoke’s interest is the decision and the operator: one person, no SLO, no on-call, deciding to take that work on. The two meet exactly at the question of what happens at 2am, and the answers are different because the staffing is.