Skip to content
RelaySub.
Sign in

RELAYSUB CONNECT · TECHNICAL PREVIEW

Your server stays private.

RelaySub Connect runs beside your media server. It reads library metadata over your LAN, asks RelaySub for the best matching subtitle, and can write a language sidecar only inside folders you approve.

Four adapters

Plex, Jellyfin, Sonarr and Radarr use their documented local APIs and standard authentication headers.

Local credentials

Media-server tokens come from environment variables. They are never sent to RelaySub Cloud or written to command output.

Safe by default

Sync starts as a dry run. Writing requires both a config change and --write; existing files stay untouched by default.

PAIR YOUR SERVER

Connect without copying an API key.

Sign in, generate a short-lived code, then enter it on the device running RelaySub Connect.

Sign in to pair a device

RUN FROM SOURCE

Verify before you automate.

  1. Create a pairing code above and enter it with pair XXXX-XXXX. The scoped key is stored in a local file and never printed.
  2. Copy the example config. It reads the paired key with file:.relaysub-connect-key and media-server secrets with env:VARIABLE_NAME.
  3. Run doctor, then scan five items and inspect a dry-run sync.
  4. Map the media path, approve a write root, and enable writing only after targets are correct.
npm ci
npm run dev -- pair XXXX-XXXX
copy relaysub-connect.example.json relaysub-connect.json
npm run dev -- doctor radarr --config relaysub-connect.json
npm run dev -- scan radarr --limit 5 --config relaysub-connect.json
npm run dev -- sync radarr --limit 5 --config relaysub-connect.json
View RelaySub Connect source

The source preview has automated adapter and filesystem safety tests. Docker and platform-specific installers still need release verification on their target NAS systems.