Every “self-host your subscriptions away” list makes it sound like flipping a switch. It’s not quite that simple, but for these five, the trade is genuinely worth it - the software is mature, the setup is reasonable, and you’re not sacrificing much beyond someone else being on call at 3am.

1. Immich → replaces Google Photos / iCloud Photos

Immich has closed the gap with commercial photo backup faster than almost anything else in the self-hosted space. Automatic mobile backup, facial recognition, timeline view, shared albums - it’s there. The real cost isn’t the software, it’s the storage: budget for real redundancy (see: data hoarding pillar) since you’re now responsible for not losing your own photos.

Resource footprint: modest for browsing and storage, but machine learning features (facial recognition, smart search) benefit noticeably from a GPU. It’ll run CPU-only, just slower on library scans and search indexing.

Run it if: you already have or are willing to build reliable storage. Skip it if: you don’t have a backup plan for the backup - self-hosted photo storage without off-site backup is a single point of failure, not an upgrade.

2. Vaultwarden → replaces 1Password / LastPass

Vaultwarden is a lightweight, Rust-based reimplementation of the Bitwarden server, compatible with all the official Bitwarden client apps. This is the lowest-risk item on this list - minimal resource footprint, mature codebase, and password managers are exactly the kind of tool that benefits from you controlling the data.

Resource footprint: tiny. This is comfortably an LXC container with a fraction of a CPU core and well under a gigabyte of RAM.

Run it if: you can commit to keeping it patched and backed up - a password vault is not the place to get lazy about updates. Set up automated backups of its database from day one, not after you’ve populated it with every credential you own.

3. Jellyfin → replaces Plex Pass / Netflix (for your own media)

Jellyfin is fully open source with no paid tier gating hardware transcoding or major features, which is the whole reason people migrate from Plex in the first place. Client app support has caught up on most platforms, and transcoding works well if you’ve got a GPU to offload it to.

Resource footprint: highly variable - mostly idle unless actively transcoding, at which point CPU-only transcoding can pin a core hard for high-resolution content. Hardware transcoding (Quick Sync, NVENC) is worth setting up if you have more than one or two simultaneous streams.

Run it if: you already have a media library. Skip it if: you’re expecting it to replace actual streaming services with current releases - that’s not what this replaces.

4. Paperless-ngx → replaces document scanning subscription services

Point a scanner (or your phone) at it, and Paperless-ngx OCRs, tags, and indexes documents automatically. It’s one of the more genuinely life-improving self-hosted apps because the payoff is immediate: searchable PDFs of every bill, receipt, and piece of mail you’ve fed it.

Resource footprint: light day-to-day, with brief CPU spikes during OCR processing on new documents. Storage grows slowly and predictably - text-searchable PDFs of paperwork aren’t large files.

Run it if: you actually have a document backlog to deal with. It’s a low-maintenance, “set it up once and feed it forever” kind of service.

5. Uptime Kuma → replaces paid uptime monitoring

If you’re running any of the above, you need to know when they go down. Uptime Kuma is a clean, actively maintained status-monitoring tool with notification integrations for basically everything (Discord, email, ntfy, ping, ports). It’s the smallest app on this list and arguably the most important - self-hosting without monitoring means you find out things broke when you go looking for them, not when they happen.

Resource footprint: negligible. This is the app you have zero excuse not to run.

Honorable mentions

A few more that didn’t quite make the top five, but are worth knowing about once you’ve got the core five running:

• Audiobookshelf - for anyone paying for an audiobook subscription and already has a library worth managing.
• Homepage/Homarr - a self-hosted dashboard that ties your growing pile of self-hosted services into one landing page, which stops mattering less than you’d think once you’re running six or seven of these.
• ntfy - dead-simple push notifications, useful as the delivery mechanism for Uptime Kuma and anything else that needs to reach your phone.

Where to start if you’re doing this for the first time

Don’t stand up all five at once. A sane order:

1. Uptime Kuma first, even before you have anything else running. It costs you nothing in resources and means every other app on this list is monitored from the moment it exists, not retroactively after something breaks silently.
2. Vaultwarden second. Lowest resource footprint, lowest risk, and once it’s running you can start migrating credentials off whatever paid manager you’re leaving - no rush, just move things over as you touch them.
3. Paperless-ngx or Jellyfin next, whichever matches an actual backlog you have (a stack of paperwork, or a media library that already exists). Don’t stand up Jellyfin speculatively if you don’t have media to serve yet.
4. Immich last, specifically because it’s the one where storage and backup planning matters most - get comfortable with the rest of your self-hosted stack, and your redundancy/backup setup, before you point your only copies of irreplaceable photos at it.

Each of these is a weekend project on its own, not a single weekend for all five. Treat it as a gradual migration off subscriptions, not a rip-the-band-aid-off weekend - the failure mode for “let’s do everything at once” is usually giving up halfway through with three half-configured services and no monitoring on any of them.

The honest trade-off

None of this is free in the way “free” gets used in marketing. You’re trading a monthly bill for your own time, your own backups, and your own uptime. For these five, that trade is worth it because the software is mature and the failure modes are well understood. The real ongoing cost isn’t compute - it’s the discipline to keep things patched, backed up, and monitored. Skip any one of those three and self-hosting stops being a upgrade and starts being a liability.

For anything less mature than what’s on this list, read the data-hoarding and hardware guides here before you commit real data to it.