Got Questions?

Tracearr supports Plex, Jellyfin, and Emby. You can connect multiple servers of any type to a single Tracearr instance and monitor them all from one unified dashboard.

Tracearr ships as a Docker image. Pull it, point it at your media servers, and open it on port 3000. The GitHub repository has compose files for Postgres 18, an all-in-one supervised image for Unraid, and the full setup instructions.

You can sign in with a local username and password, or sign in with Plex. Operators can also enable optional single sign-on (OIDC) for their instance if they run an identity provider like Authentik or Okta.

Yes. Tracearr is completely free and open source under the AGPL-3.0 license. You can self-host it on your own infrastructure with no subscription fees or usage limits.

Impossible travel detection identifies when the same account streams from locations that are physically impossible to travel between in the time elapsed. For example, if a user streams from New York and then 10 minutes later from London, that's flagged as suspicious activity.

Each person starts with a trust score that automatically adjusts based on their streaming behavior. If you've merged someone's Plex, Jellyfin, and Emby accounts into one identity, their identity score is the lowest of their active accounts, with a per-server breakdown available when you need to see where a violation happened. Violations like simultaneous streams from different locations, device velocity anomalies, or impossible travel will reduce their score, helping you identify potential account sharers at a glance.

Yes. A destination is where messages go, and there are nine kinds: Discord, a JSON webhook, ntfy, Gotify, Apprise, Pushover, email, mobile push, and a toast in the browser. You can add as many of each as you want and point one automation at several of them at once.

Automations, as of Tracearr 2.2.0. Instead of six fixed rule types you pick a trigger, add conditions, and choose what happens: notify a destination, adjust a trust score, message the player, or stop the stream. The old rules were converted automatically on first boot, and every detection they did still ships as one of the twenty-two built-in templates. Any automation can be exported as a share code and pasted into someone else's install.

Yes. Newsletters list new movies, shows with their new seasons, and albums, with an optional most-watched section, and go out daily, weekly, monthly, or on a cron expression. The window normally picks up where the last send stopped. Addresses come from a contact email you set, the person's Tracearr login, or their Plex account. Jellyfin and Emby expose no addresses, so Tracearr lists those people for you to type one in. Every email carries an unsubscribe link and a view-in-browser link, and each send keeps a per-recipient status with a retry for the failures.

Yes. The Media section shows movies and shows from every connected server in one poster grid, with filters for watched state, resolution, HDR, genre, year, server, library, and size on disk. Opening a title lists every copy of it with per-file quality and size, who has watched it, and how far each person got.

Yes. Tracearr groups titles that have more than one copy or file across servers, libraries, and versions, so the same film on your Plex server and your Jellyfin server shows up as a single group. Matches are scored Exact, Likely, or Possible against IMDB, TMDB, and TVDB ids, a fuzzy title match, or two versions of the same file, and every group shows how much space you would get back. Mirrored files are only counted once.

The Storage page has a Dead Weight report listing never-watched titles ranked by size, with the reclaimable total at the top. Alongside it, Stale Content flags media that has gone quiet and Content ROI ranks titles by watch hours per gigabyte, so you can see what earns its disk space.

No. Tracearr only stores session metadata and analytics. It connects to your media servers via their APIs using tokens you provide, and never accesses or stores your actual media files or login credentials.

Yes. The v2 public API covers history, live streams, media, users, libraries, and recently added content as read-only JSON with cursor pagination. What makes it different from a single-server stats API is that media and people are canonical across servers: a film sitting on both your Plex and Jellyfin servers has one stable id with every copy and every physical file listed under it, and one person with three accounts counts as one viewer. Requests authenticate with a bearer token you generate in Settings, and the rate limit is yours to set. Tracearr 1.4.6 and later also serve a v1 API, which adds trust scores, violations, and the one write endpoint: terminating a stream.

Tracearr serves its own OpenAPI spec and renders it inside the app, with your instance's real server ids already filled into the examples and your API key preloaded, so you can fire test requests without leaving the page. The specs are also attached to every GitHub release, and docs.tracearr.com/api renders the spec for your version.