Self-hosted & servers
Self-Hosting Starter Stack: Files, Photos, Media and Monitoring
Bring files and photos back to your own machine: settle storage and backup first, then media and monitoring, and only then the nice-to-haves.
The classic self-hosting mistake is installing apps before deciding where backups live. This list follows dependency order: settle where files and photos land, then pick media and monitoring, and finally use directory-style references to widen your shortlist. Each item solves one concrete problem; you do not need all of them at once.
Shortlist（8）
- filebrowser · 深度导读卡 ¥4.9Apache-2.0 · Go · ★35.9k
A single-binary web file manager — a practical first browsing layer for a NAS before adding other apps.
- homebox · 深度导读卡 ¥4.9AGPL-3.0 · Go · ★7.7k
Home inventory and warranty records; complements file storage by tracking where physical things are.
- romm · 深度导读卡 ¥4.9AGPL-3.0 · Python · ★14.2k
Turns a local ROM collection into a browsable, metadata-rich library for people who already have the files.
- immich · 深度导读卡 ¥3.9AGPL-3.0 · TypeScript · ★118.2k
Photo backup is the hardest cloud service to replace; evaluate it before migrating your camera roll.
- WatchYourLAN · 生态位观察 ¥4.9MIT · Go · ★7.7k · Likely unmaintained
LAN device presence monitoring — useful while commissioning services to catch drop-offs early.
- netdata · 深度导读卡 ¥4.9GPL-3.0 · Go · ★81.3k
Resource and alert dashboard for spotting which container is eating your small host.
- awesome-selfhosted · 深度导读卡 ¥3.9NOASSERTION · ★333.5k
A directory-style list for comparing self-hosted alternatives; it does not replace per-item deployment judgment.
- umbrel · 项目速写 ¥3.9NOASSERTION · TypeScript · ★12.5k
An all-in-one distribution approach for people who do not want to wire reverse proxies and certificates themselves — at the cost of control.
Storage first, apps second
Every self-hosted app writes data. Write down where data lives, how it is backed up, and how long restore takes before judging interfaces. Without a backup plan, each additional app raises risk.
Install in dependency order
File layer, then media layer, then monitoring. Installing monitoring first gives you a baseline for each new service; the reverse leaves you without data when something breaks.
When not to self-host
If data loss is unacceptable and you lack off-site backups plus restore drills, do not migrate yet. The cost of self-hosting is maintenance and incident response, not installation.
Common pitfalls
Common traps: container data on the system disk, RAID without snapshots, exposing services publicly by default, and upgrading without reading release notes.
Alternatives
If maintenance is not for you, hosted storage plus local cold backups is still the calmer combination. Self-hosting buys control and portability, not necessarily lower cost.