nightowl logo
PROJECT 001 Running at home

nightowl

A self-hosted family movie server. Jellyfin in containers, private remote access for relatives over Tailscale, and no router ports opened by default.

Role
Design, build, documentation
Started
October 2026
Stack
Jellyfin · Docker Compose · Tailscale · Seerr
Host
Windows PC (WSL2) today, NAS next
Architecture

How it fits together

ClientsHome + family
TVs and phones At home, the official Jellyfin apps on Roku, Fire TV and Google TV. Relatives use a Google TV or Fire TV stick with Tailscale. → LAN, or a WireGuard tunnel
Network0 router ports
Tailscale sidecar Connects out, so it works behind CGNAT. Each relative's own account gets a share of one tagged node, which answers only on the Jellyfin port (plus HTTPS with the domain add-on). Title requests from inside Jellyfin use that same port. → jellyfin:8096
HostDocker Compose
One stack, opt-in add-ons
jellyfincore backupcore tailscaleopt-in proxyopt-in seerropt-in
→ media mounted read-only
StorageHost disks
Media and config Media is read-only to Jellyfin. The config is snapshotted every 24 hours to a separate backup folder, keeping the newest 7. Seerr, when it is on, gets its own backup sidecar and archives.
Fig. 1 · Request path, left to rightHardware transcoding (NVIDIA or Intel) is a per-host add-on
By the numbers

Small footprint, written down

0router ports opened by default
13architecture decision records
331plugin settings pinned by an allowlist, every one mutation-tested in CI
~90 sto rehearse an upgrade and roll it back, once the images are pulled

Defaults and measurements from the project's docs, October 2026. Faster direct connections are an opt-in: they open one UDP port on the router.

Design choices

Decisions and trade-offs

ADR 0004

A Tailscale sidecar, not port forwarding

Remote access runs in its own container with userspace networking, so the host never joins the tailnet. Relatives accept a share from their own free account; nobody is invited into the owner's network.

TRADE-OFFEvery remote device needs Tailscale, so a TV without it needs a streaming stick.
ADR 0003

Backups without stopping Jellyfin

Each database is copied with SQLite's online backup and must pass an integrity check before it is archived. No Docker socket, no stop window.

TRADE-OFFConfig only: no media, no encryption, no off-site copy yet.
ADR 0009

Pinned images, upgraded by a person

Dependabot proposes bumps and a weekly job files an issue for each new Jellyfin advisory, but a person merges every image bump. Rollback means restore, then re-pin.

TRADE-OFFA few minutes of manual work per upgrade.
ADR 0012

A third-party plugin, admitted on written criteria

Jellyfin Enhanced puts Seerr search, requests and discovery inside Jellyfin's web UI and calls Seerr from the server, so relatives on the tailnet can request titles without a new port. It was scored against written admission criteria: two not met, two only partly. One release is pinned by its SHA-256, all 331 settings by an allowlist, and the kids' rating filter is checked route by route against an independent certification source.

TRADE-OFFCode mostly from one maintainer runs inside the server. The request screens appear only where Jellyfin's web UI renders, not in native TV apps.
ADR 0013

A TMDB key behind a go-live gate

A TMDB key fills in the studio tiles, but it also opens a TMDB passthrough. A test on throwaway servers was set as the gate: if a kid account could pull a title list, the key stays out. The gate fired on one genre route. The owner accepted that risk in writing, and the key went live.

TRADE-OFFA kid calling that route directly sees a genre's titles and posters, unfiltered. No screen calls it, and requests and playback stay limited.
ADR 0014

Moonfin reviewed, and not adopted

Moonfin would bring discovery and requests to native TV apps. The review read its server plugin's source and scored it on the same criteria. Findings included a Seerr proxy with no route allowlist or rating filter, third-party calls on by default, and hand-built releases with no security channel. Nothing was installed.

TRADE-OFFTVs keep the official apps; requests happen on a phone or a computer. A later release can reopen the review.
Timeline

From an empty repo to the living room

  1. Guardrails firstPersonal-info and secret checks, an issue board, and a design review of every issue (a council of AI role agents) before any server code.
  2. Baseline to remote accessJellyfin on the LAN, hardware transcoding, config backups and the Tailscale sidecar. First tests on the real host, at home and remotely.
  3. Household setupProfiles and parental controls, a branded Jellyfin, an intro before movies, and live TV support for an antenna tuner (still to be tested on real hardware).
  4. Private HTTPSA custom domain that points at the server's tailnet address, so it only works on the tailnet. Certificates come from a DNS challenge, with no inbound port.
  5. First security upgradeJellyfin moved to 12.x to close open advisories, using the rehearsed upgrade path. The rehearsal showed the database migration is one-way, so a rollback restores the pre-upgrade backup.
  6. Fixing what the real host foundSwitching certificates from staging to production kept serving the staging one, so the proxy now loads only the active CA's state. Scripts moved to the API header 12.x requires.
  7. Title requestsSeerr as an opt-in add-on, on the home network only. A test reads its safe defaults back and must fail when any one is flipped.
  8. Requests inside JellyfinA vetted third-party plugin for search, requests and discovery, proved on throwaway servers. The check from a remote device is still open.
  9. Kids' librariesKids Movies, Kids TV and Holiday libraries. On a throwaway server, a kid account limited to the two kids' libraries saw only those, and the rating limit still applied inside them. Franchise box sets are switched on; how they group real titles is still a live check.
  10. Two plugin callsA TMDB key went live after its security gate fired and the owner accepted the risk. Moonfin was reviewed and rejected.
  11. Now
    Running at homeOn a Windows PC for the proof of concept. Next: a tested move to a NAS.