Question 1

What media servers does Tracearr support?

Accepted Answer

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.

Question 2

How do I install Tracearr?

Accepted Answer

Tracearr is distributed as a Docker container for easy deployment. Simply pull the image and configure your media server connections. Check our GitHub repository for detailed setup instructions and docker-compose examples.

Question 3

How do I log in to Tracearr?

Accepted Answer

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.

Question 4

Is Tracearr free?

Accepted Answer

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.

Question 5

What is impossible travel detection?

Accepted Answer

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.

Question 6

How does trust scoring work?

Accepted Answer

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 trust score reflects all of it, 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.

Question 7

Can I get notifications when violations occur?

Accepted Answer

Yes! Tracearr supports Discord webhooks, push notifications via Apprise, and custom webhook endpoints. You'll be instantly notified when suspicious activity is detected so you can take action.

Question 8

Can I browse my media library in Tracearr?

Accepted Answer

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.

Question 9

Can Tracearr find duplicate media across my servers?

Accepted Answer

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.

Question 10

How do I find media nobody watches?

Accepted Answer

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.

Question 11

Does Tracearr store my media or credentials?

Accepted Answer

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.

Question 12

Does Tracearr have an API?

Accepted Answer

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.

Question 13

Where are the API docs?

Accepted Answer

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.

Got Questions?

Getting Started

Features

Technical