Documentation
Run putiorr as the Transmission bridge for your *arr stack.
These pages cover the production container shape, the shared download target, put.io connection options, RR profiles, download profiles, and the exact download-client values to paste into Radarr, Sonarr, and Lidarr.
Guides
Setup Guide
Prepare persistent storage, run the GHCR image, connect put.io, and mount the shared download target into every importer.
Open setup guideConfiguration Guide
Create RR profiles, tune download profiles, and configure Radarr, Sonarr, Lidarr, Readarr, and Prowlarr with the matching RPC paths.
Open configuration guideAI Agent Guide
Share one URL with Codex or another assistant so it can inspect the user's stack, collect missing inputs, install putiorr, and validate the setup.
Open agent guideOAuth Relay
Use the static relay page as the browser handoff for hosted put.io OAuth authorization.
Open OAuth relayCore model
putiorr pretends to be Transmission for the *arr side, sends magnet and torrent grabs to put.io, then downloads completed put.io files into a local download target. Completed-download handling in Radarr, Sonarr, Lidarr, and similar apps then imports from that same mounted path into the normal media libraries.
put.io -> putiorr -> shared download target -> *arr import -> media library