Redirecterr is a small, self-hosted webhook service that sits between Overseerr or Jellyseerr and your Radarr/Sonarr instances and decides where a request actually goes. When a user asks for a title and it lands in the pending-approval queue, Redirecterr receives the webhook, runs the request through a set of user-defined filters — keywords, genres, content ratings, requester, season count and dozens of other TMDB fields — and routes it to whichever instance matches: an anime library, a 4K library, a kids-safe set of root folders, or all of them at once.

Key Features

• Filter-driven routing — every filter names a media_type (movie or tv), an optional is_4k flag, a set of conditions and one or more target instances to apply them to.
• Dozens of matchable fields — keywords, genres, content ratings, requestedBy_email/requestedBy_username, max_seasons, vote average and count, original language, spoken languages, networks, production companies, countries, release dates and more, all taken from the incoming Overseerr/Jellyseerr payload.
• Three match modes per condition — require (all values must match), exclude (none may match) and include (at least one matches).
• Fan-out to several instances — one filter can apply to a list of instances, so a request can be sent to both sonarr and sonarr_4k in a single rule.
• Per-instance overrides — root folder, server ID (the left-to-right order of services in Overseerr), quality profile ID and an approve toggle per instance.
• 4K-aware routing — is_4k: true matches only 4K requests, false only non-4K, and leaving it empty matches both.
• Approve-on-no-match — decide once whether a request that matches no filter is approved automatically or left waiting for a human.
• Single container, one config file — configuration is a mounted config.yaml, logs go to a mounted directory, and there is no database to back up or migrate.

Why Use It

Overseerr routes a request to one service per media type, which is fine until a library grows into separate anime, 4K and kids collections. After that the routing decision lives in someone’s head: the admin reads the pending list, works out that this is an anime series, and manually picks the instance with the right root folder. Redirecterr turns that judgement into a rules engine that runs on every incoming request, in milliseconds, with the same answer every time.

It also replaces the usual pile of per-user workarounds. Instead of granting broad auto-approval because triage is tedious, you keep requests pending and let the filters approve the harmless ones, while the rules that matter — no adult content for the kids profile, no 4K for the metered connection — are stated explicitly in a YAML file you can read, diff and version.

Use Cases

• Anime library routing — send anything whose keywords or genres include anime or animation to a dedicated Sonarr/Radarr instance.
• 4K split — route 4K requests to a separate instance with its own root folder and quality profile while HD requests keep going to the main library.
• Age-appropriate libraries — exclude low age ratings so children’s requests never reach an unrestricted instance.
• Per-user limits — match on requestedBy_username and cap a heavy requester to short series with max_seasons.
• Fan-out for redundancy — apply one rule to several instances so a request is queued in more than one place at once.

The container listens on port 8481 and exposes a single POST /webhook endpoint, so point your Overseerr webhook at http://redirecterr:8481/webhook. There is no web interface by design: the service is operated through its structured logs and its YAML configuration.

Licence

MIT — free and open source. The licence is declared as MIT in the project’s package.json; the repository does not ship a separate LICENSE file.