Guides
Self-hosting means operating the service
Running software yourself can be a good control choice, but it is an operating commitment rather than an escape from operations.
Scope: a concise editorial field note, not a universal recommendation, security audit, or guarantee.
Control changes hands
Self-hosting changes who controls the service, its data, and its access. It does not remove the work of keeping the service available and current.
The right question is not whether self-hosting is always better. Ask whether you can operate this particular service with the time, skills, and recovery path it needs.
The operating list is real
Plan for updates, monitoring, capacity, incident response, backups, restore testing, and at least one copy away from the main machine. A calm setup is still a setup that needs a plan.
Keep the plan proportionate. A household service may need a short runbook and scheduled checks, while a team service may need alerts, documented ownership, and a tested recovery window.
Immich makes the boundary visible
For a photo service such as Immich, keeping only the asset files is not enough. The database also carries the organization and state needed by the application, so both parts belong in the backup and restore plan.
This is a practical example of why a backup that merely looks large or completed is not proof of a usable recovery.
Practical checklist
- Write down update and monitoring responsibilities.
- Keep an off-site or otherwise separate copy.
- Restore both application data and database state.
- Set a recovery check that fits the service scale.
Sources checked
These first-party or authoritative sources ground the note. Checked 2026-08-11.