The Best Self-Hosted Apps for a First Home Server: What to Install in Week One

A new home server is exciting and slightly paralysing. There are thousands of self-hosted apps, and every list online recommends forty of them. Install too many in the first week and you end up with a fragile pile of containers you do not understand, no backups, and an evening lost every time something updates.

This list is deliberately short. It covers the apps that give the most value to a household in the first weeks, in the order that makes sense to install them, with the foundations first. Everything here runs in Docker on a modest mini PC or NAS, and every app is free and open source or has a free self-hosted edition.

Week one in one table

Foundations before apps

Docker Compose. Run each app from a Compose file in its own folder, with data in clearly named volumes or bind mounts. Keep the files in a Git repository. A graphical manager such as Dockge or Portainer helps you see what is running, but the Compose files remain the source of truth. If you are choosing the operating system underneath, the trade-offs are in Ubuntu Server vs Debian for a home server.

Remote access without open ports. A mesh VPN such as Tailscale, or a self-hosted WireGuard setup, lets phones and laptops reach the server from anywhere without exposing apps to the internet. Install it before any app that holds personal data. Add a reverse proxy such as Caddy later, when you want nice names and HTTPS.

Backups. Set up a backup tool before you move in photos and documents. Kopia and restic both make encrypted, deduplicated backups to a USB drive, another machine or cloud storage; they are compared in Kopia vs restic. Back up the app data folders and databases, not just media, and test one restore.

Monitoring. Uptime Kuma checks that each app responds and alerts you on your phone when it does not. A light resource monitor such as Beszel shows CPU, memory, disk and per-container usage. Send alerts somewhere you will actually see them, a choice covered in Apprise vs ntfy.

Quick wins the whole house notices

Pi-hole or AdGuard Home. Network-wide ad and tracker blocking is often the first self-hosted service a family appreciates, because pages load faster on every device without installing anything. Point your router’s DNS at it, keep a fallback in mind for when the server is down, and whitelist the occasional site that breaks.

Vaultwarden. A lightweight server compatible with the Bitwarden apps, so the family gets a polished password manager on every phone and browser. It uses very little memory. Treat it as a critical service: backups, updates and VPN-only access. The trade-offs against a file-based manager are in Vaultwarden vs KeePassXC.

Photos, files and paperwork

Immich. The closest self-hosted experience to Google Photos: automatic phone backup, a fast timeline, face recognition and search by description. It needs more RAM than most apps here, especially during the first import. Alternatives with different privacy models are covered in Immich vs Ente Photos.

File sync. For a couple of laptops, Syncthing syncs folders directly with no server app. For a family with phones and web access, Seafile or Nextcloud provide shared folders with apps; the differences are in Seafile vs Nextcloud for family file sync.

Paperless-ngx. Scan or email household paperwork, such as bills, contracts and warranties, and Paperless-ngx reads the text, tags documents automatically and makes them searchable. It quickly becomes one of the most valued apps on the server.

Media and everyday extras

Jellyfin. A free media server for films, TV and music, with apps for TVs, phones and browsers. Use a CPU with hardware video decoding, such as a recent Intel chip, if devices will need transcoding. It is compared with its commercial cousin in Emby vs Jellyfin.

Audiobookshelf. If anyone in the house listens to audiobooks or podcasts, it does the job far better than a general media server.

Mealie. A family recipe library with meal planning and shared shopping lists. A small app that often gets used more than expected.

A start page. Homepage or Homarr gives everyone one page with every app, plus live status. Set it as the home page on family devices.

What to leave for later

Some popular apps are better left until the basics are solid:

• Home Assistant is excellent, but it is a project in its own right. Start it when you have time to learn it, ideally on its own device or virtual machine.
• Self-hosted email involves deliverability, DNS and reputation work that is very different from running containers.
• Single sign-on such as Authelia or Authentik is worth it once you have many apps and several users, not in week one.
• Exposing apps publicly through port forwarding. Keep everything behind the VPN until you understand the risks and have authentication in place.
• Kubernetes and clustering. Interesting to learn, unnecessary for a household.

Sizing the hardware

All of the apps above, apart from heavy media transcoding and the first big photo import, run comfortably on a modern low-power mini PC with 16 GB of RAM and an SSD for app data, with bulk storage on a NAS or extra drives. Immich and Jellyfin are the most demanding. Plan disk space for photos and media generously, and keep app data on fast storage. If you have not bought hardware yet, mini PC options are compared in Beelink vs Minisforum.

Updates without breakage

Self-hosted apps update often, and most problems on a young home server come from updates rather than hardware. A few habits keep this calm:

• Pin versions for critical apps. Use specific version tags for Immich, Vaultwarden and Paperless-ngx rather than “latest”, and update them deliberately after reading the release notes. Some apps, Immich in particular, occasionally require manual steps.
• Automate updates only for low-risk apps. A tool such as Watchtower or Diun can update or notify you about updates. Let it update simple apps automatically and only notify you for the important ones.
• Back up before updating. A snapshot or a fresh backup of the app’s data folder takes a minute and turns a broken update into a short rollback.
• Update the host regularly. Enable automatic security updates for the operating system and reboot during a quiet time each month.
• Keep notes. A short text file per app, with where its data lives, how it is backed up and anything unusual about its setup, saves hours when something breaks months later.

Making it usable for the family

A home server succeeds when other people in the house use it without asking for help. That depends less on the apps than on how they are introduced:

• Set up apps on their devices with them. Install the photo app, the password manager and the VPN on each phone in person, and check that automatic backup and autofill work.
• Use plain names. “Photos”, “Passwords” and “Movies” on the start page, not software names.
• Give each person their own account, so progress, photos and passwords are separate, and so you can remove access later.
• Write a one-page guide with the start page address, what each app is for and who to ask. Print it if needed.
• Keep the old service for a while. Leave Google Photos or the old password manager in place for a month as a fallback while habits change.

Expect questions in the first few weeks, and fewer afterwards. The apps that stick are the ones that felt easy on day one.

An install order that avoids regret

1. Operating system, updates, SSH keys, Docker.
2. VPN for remote access.
3. Backup tool, pointed at an empty data folder, with a tested restore.
4. Uptime Kuma and a resource monitor, with phone alerts.
5. Pi-hole or AdGuard Home.
6. Vaultwarden.
7. Immich and file sync.
8. Paperless-ngx, Jellyfin and the extras.
9. A start page linking everything.

Steps one to four take an evening or two and are the least exciting part, but they are what make every later app safe to depend on. Skipping them is the most common reason first home servers get abandoned after a bad update or a dead disk.

Add one app at a time, use it for a few days, and make sure it is in the backup and the monitoring before installing the next. A home server with eight apps that are backed up and watched is far more useful than one with forty that nobody dares to update.