Introduction
Brokerr reads media state from Plex, Jellyfin, or Emby and synchronizes it to supported tracking services. Profiles decide which libraries, target account, and rules are used.
What Brokerr provides
Section titled “What Brokerr provides”- Multiple Plex, Jellyfin, or Emby sources and multiple accounts for the same target provider.
- Profiles that select source libraries, one target, and explicit sync rules.
- Full, incremental, webhook-triggered, manual, and scheduled synchronization.
- Dry-run diffs with individual or bulk apply and revert operations.
- Manual mapping overrides, provider search, ignored items, and AniBridge anime mappings.
- Local authentication, encrypted credentials, audit history, diagnostics, and request telemetry.
Current boundaries
Section titled “Current boundaries”Plex supports native event webhooks. Jellyfin supports event webhooks through the official Jellyfin Webhook Plugin. Emby supports native Webhooks when the server license exposes that feature. Target capabilities differ, so Brokerr only shows supported rules. See the integration matrix before creating a profile.
Recommended workflow
Section titled “Recommended workflow”- Configure persistent storage and protect the master key.
- Add Plex, Jellyfin, or Emby and load only the libraries that should be available to profiles.
- Add and authorize a target account.
- Create a profile with conservative rules and dry-run enabled.
- Run a full sync, resolve unmatched items, and inspect the diff.
- Enable live writes and scheduling only after the result matches your intent.
Continue with the quick start, or read how Brokerr works.