Prerequisites

What JellyPass needs
You needDetails
Jellyfin 12.x or 10.11.xJellyPass supports the current Jellyfin release and the one before it, and tests both against a real Jellyfin before each release. On any other version, JellyPass 3.10.0 keeps serving household addresses but warns, in its log and in the admin site, until an administrator confirms that exact version; JellyPass 4.0.0 will refuse household requests instead (see Jellyfin versions).
A Jellyfin administrator API keyJellyfin Dashboard → API Keys. Only administrators can change item tags and user policies.
SeerrSeerr, or Jellyseerr, with users imported from or linked to Jellyfin; it sends JellyPass the webhook. Overseerr on its own supports only Plex and does not work. Giving JellyPass Seerr's API key as well is needed for the apps, the request backfill, 4K requests and the short webhook payload.
Docker with Compose v2The recommended install. Images are published for linux/amd64 and linux/arm64. You can also run it from source with Node.js 22 or later and pnpm.
A reverse proxy with HTTPSFor household addresses: a domain you control, DNS for each household name (or a wildcard), and a certificate covering them. See Reverse proxy.
A TMDB API keyOnly for the household apps, which read titles, posters and details from TMDB. A v3 API key or a v4 read access token from your TMDB account's API settings. Read TMDB's API terms.
Somewhere private for the state fileOne JSON file (grants.json) holds everything JellyPass decides. It contains Jellyfin user IDs and media names; keep it private and back it up.

Network