Tracearr

Self-hosted media server monitoring, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (AGPL-3.0) monitoring platform for Plex, Jellyfin, and Emby — unified watch history, stream analytics, geolocation, and account sharing detection from a single Docker deployment [website][README].
• Who it’s for: Self-hosted media server owners who run more than one server type and are tired of maintaining Tautulli and Jellystat separately. Also anyone who wants intelligent sharing detection — impossible travel flags, device velocity limits, trust scores — beyond Tautulli’s basic session counting [README].
• Cost savings: $0 for the software. The main alternatives (Tautulli, Jellystat) are also free — the savings story here is operational simplicity, not bill reduction. Running Tracearr on a $6/mo Hetzner VPS handles your entire monitoring stack for all three server types instead of running two separate tools.
• Key strength: The only open-source tool that monitors Plex, Jellyfin, and Emby in one dashboard. Ships with six sharing detection rules (including impossible travel), a mobile app on both iOS and Android, and a read-only REST API [README][website].
• Key weakness: Young project — 1,567 GitHub stars, single primary developer, no independent third-party reviews available at time of writing. Community testimonials are enthusiastic, but that’s a different evidence standard than a year of real-world stress tests [website community quotes].

---

What is Tracearr

Tracearr is a self-hosted dashboard that connects to your Plex, Jellyfin, and Emby servers — simultaneously — and gives you a unified view of activity across all of them. Watch history, active sessions, stream analytics, geolocation, and account sharing detection in one interface [README].

The project’s own framing is the clearest version of the pitch: “Tautulli only works with Plex. Jellystat only works with Jellyfin and Emby. If you run multiple servers, you’re stuck with multiple dashboards. Tracearr handles all three. One install, one interface.” [README]

That’s not marketing filler — it describes a real gap. The self-hosted media monitoring space has been siloed by server type since Tautulli emerged as the Plex standard. Anyone who later added a Jellyfin server for family members (common, since Jellyfin doesn’t require a Plex Pass for remote access) found themselves running two separate monitoring tools with two separate configs and no aggregate view.

Beyond the headline unification, what Tracearr adds on top of Tautulli-style watch history is worth examining separately: library analytics broken into four dedicated pages, geolocation data that includes ASN and postal codes for every session, a stream world map, and sharing detection logic sophisticated enough to flag impossible travel — the same account streaming from New York and then London 30 minutes later [README].

The project is built by a single developer (Connor Gallopo), is about a year old based on the Discord server creation, and sits at 1,567 GitHub stars. The developer is described as highly active and responsive by multiple community users [website community quotes].

---

Why people choose it over Tautulli and Jellystat

The comparison isn’t really Tracearr vs Tautulli on a per-feature basis. Tautulli has years of development, a large plugin ecosystem, and notification agents that can trigger almost anything. Jellystat is the mature choice for Jellyfin-only setups. The reason someone picks Tracearr over both isn’t that it outperforms them on their respective turf — it’s that those tools force you to pick one lane.

The multi-server problem is real. Once you’re running Plex and Jellyfin (increasingly common as Jellyfin’s feature set has closed the gap), your monitoring gets fragmented. Two dashboards, two alert configs, no unified view of total bandwidth or who’s most active across your whole infrastructure [README]. Tracearr eliminates that duplication.

Sharing detection is meaningfully different. Tautulli can alert when concurrent stream counts exceed a limit. Tracearr ships six rule types out of the box: Impossible Travel, Simultaneous Locations, Device Velocity (too many unique IPs in a short window), Concurrent Streams, Geo Restrictions, and Account Inactivity. These rules feed into per-user trust scores that decay automatically on violations. Discord webhooks fire the moment a rule triggers [README]. One community user on the website put the practical value plainly: “Family sharing always starts simple, then suddenly half the internet is on your server. Having something that actually shows patterns and flags weird usage makes a lot of sense.” [website]

The polish surprised the early adopter community. One user wrote: “For a first release, it is really polished too.” Another: “EXCELLENT example of TRUE hard work — no bullshit AI slop.” [website] The compose file specifically drew praise: “I also very much appreciate how clean that AIO compose file is.” [website] Early-release tools in the self-hosted space rarely earn that kind of specific feedback.

The honest qualification: every quote above comes from the project’s own website testimonials, sourced from Discord. No independent reviews of Tracearr existed at the time of writing — the project is too new to have accumulated external write-ups. Enthusiastic community reception is a signal, but not the same as an external audit.

---

Features: what it actually does

Core monitoring:

• Connect Plex, Jellyfin, and Emby simultaneously — no per-server install [README]
• Real-time WebSocket-powered updates — streams appear and disappear live [website]
• Complete session history: who watched what, when, on what device, from which IP [README]
• Full geolocation per session including ASN data, continent, and postal codes [README]

Stream analytics:

• Transcoding vs. direct play breakdown per user and device
• Bandwidth consumption per user, bitrate tracking
• Codec and resolution distributions
• Device health scores factoring in direct play rate, codec support, and transcode frequency [README]

Library analytics — four dedicated pages:

• Overview: item counts, storage usage, growth over time
• Quality: resolution and codec distribution, 4K vs 1080p ratio tracking
• Storage: duplicate detection across servers, stale content identification, usage predictions, ROI (watch hours per GB)
• Watch: engagement metrics, completion rates, viewing patterns by hour and month, binge detection [README]

Account sharing detection:

• Impossible Travel (NYC then London in 30 minutes)
• Simultaneous Locations (same account streaming from two cities at once)
• Device Velocity (too many unique IPs in a short window)
• Concurrent Streams (per-user stream limits)
• Geo Restrictions (country-level blocking)
• Account Inactivity notifications
• Trust scores that update automatically on rule violations [README]

Other capabilities:

• Live TV and music session tracking, not just movies and shows [README]
• Stream map — world map visualization of stream origins, filterable by user, server, and time period [README]
• Mobile app on iOS (App Store) and Android (Google Play) [website]
• Read-only REST API, Swagger UI at /api-docs, works with Homarr and Home Assistant [README]
• Bulk actions: acknowledge violations, reset trust scores, enable/disable rules, delete history [README]
• Data import from Tautulli or Jellystat — preserves existing watch history on migration [README]
• Discord webhooks and custom notifications [README][website]

Infrastructure:

• Docker and Docker Compose [README]
• PostgreSQL for storage, Redis for real-time data [merged profile]
• CI and nightly builds tracked on GitHub Actions [README]

---

Pricing: the VPS is the only cost

There is no SaaS tier to compare against. Tracearr is $0, full stop. No premium plan, no feature gates, no concurrent user cap, no server limit. AGPL-3.0 licensed, free to use forever [website]. The pricing page doesn’t exist because there’s nothing to price.

The relevant comparison isn’t against a SaaS bill — it’s operational:

Setup	Monthly cost	Coverage
Tautulli only	$0 + VPS share	Plex only
Jellystat only	$0 + VPS share	Jellyfin/Emby only
Tautulli + Jellystat	$0 + two services	Plex + Jellyfin/Emby separately
Tracearr	$0 + VPS share	All three, unified

If you’re co-hosting on your existing media server hardware, the incremental resource cost is roughly 200–400MB RAM for PostgreSQL, Redis, and the web app. If you need a dedicated VPS, a $6/mo Hetzner or Contabo instance handles the stack comfortably.

The closest paid comparison is Plex Pass at $6.99/mo (or $79.99/year, or $119.99 lifetime), which unlocks some analytics inside Plex itself. Tracearr gives you more depth in analytics and covers non-Plex servers, at $0 in software cost. But running both isn’t uncommon — Plex Pass covers remote access and sync features that Tracearr doesn’t touch.

---

Deployment reality check

The install path is Docker Compose. If you already run a Docker media stack (Plex, *arr apps, Overseerr, Jellyfin), this is the same workflow you use for everything else. Community feedback specifically praises the compose file quality [website].

What you actually need:

• Docker and Docker Compose
• PostgreSQL (bundled in the default compose or bring your own)
• Redis (same — bundled or external)
• Your Plex token, Jellyfin API key, or Emby API key to connect servers
• A local IP or domain for the dashboard

What can go sideways:

The geolocation features — the stream map, ASN data, impossible travel detection — all depend on outbound internet access for IP lookups. Offline or heavily firewalled setups will need to account for this; the geolocation engine won’t work without it [README].

The AGPL-3.0 license is more restrictive than MIT. For personal use, it doesn’t matter at all. If you’re building a product on top of Tracearr or distributing a modified version, you must open-source your modifications. Read the license before doing anything commercial with it [website].

The README doesn’t document upgrade procedures, backup strategies, or schema migration handling between releases. For early software, minor version bumps sometimes include schema changes. Check release notes and the Discord before upgrading in production [README].

The single-developer risk is real. Tautulli has years of contributors and community plugins. Tracearr is one person’s project at 1,567 stars. The developer is active and responsive — but “active single developer” is a different reliability tier than “large open-source project with organizational backing.”

Time estimates: For someone already running a Docker media stack, 30–60 minutes to a working install. For a non-technical user following a guide, budget 2–4 hours including Docker setup and server credential gathering. If you’ve never touched a Linux server, have someone deploy it for you.

---

Pros and cons

Pros

• Unique multi-server support. No other free, open-source tool monitors Plex, Jellyfin, and Emby from one dashboard. If you run two server types, this gap is real and Tracearr fills it [README].
• Sophisticated sharing detection. Six rule types, trust scores, impossible travel logic — more depth than Tautulli’s session limit notifications [README].
• Completely free, no feature gates. AGPL-3.0, all features included, no usage limits, no “pro” tier [website].
• First-party mobile app. iOS and Android. Tautulli relies on a third-party companion app (Tautulli Remote); Tracearr ships its own [website].
• Data import on migration. Tautulli and Jellystat history imports without losing your watch data [README].
• REST API included. Swagger UI, API key auth, works with Homarr and Home Assistant [README].
• Active developer with fast Discord response. Multiple independent testimonials specifically call this out [website community quotes].
• Library analytics depth. Storage ROI, duplicate detection across servers, binge patterns, completion rates — beyond what Tautulli offers natively [README].
• No telemetry. No data collection, no cloud dependency, all data stays on your server [website].

Cons

• Single developer, 1,567 stars. Tautulli has years of community development and a plugin ecosystem. The bus-factor risk is real, even with an active developer [merged profile].
• No independent third-party reviews. All available evidence is website testimonials and Discord reactions. Enthusiastic, but not an independent audit [website].
• AGPL-3.0 limits commercial use. Modifications must be open-sourced if distributed. Not relevant for personal self-hosting; potentially relevant for commercial deployments [website].
• Geolocation requires outbound internet. The most distinctive features depend on external IP lookups — not suitable for air-gapped environments [README].
• No documented upgrade or backup procedures. Schema migrations between releases aren’t covered in the README. You’re on your own for operations [README].
• Young project, rough edges possible. Early software means the edge cases haven’t all surfaced yet. Tautulli has absorbed years of user edge cases; Tracearr hasn’t [merged profile].

---

Who should use this / who shouldn’t

Use Tracearr if:

• You run Plex alongside Jellyfin or Emby and currently maintain two separate monitoring tools.
• You want real sharing detection logic — impossible travel flags, device velocity limits, trust scores — not just raw concurrent stream counts.
• You’re already running a Docker media stack and can absorb one more compose service.
• You want a mobile monitoring app without relying on a third-party companion.
• You’re migrating from Tautulli or Jellystat and want to preserve your watch history.

Stay on Tautulli if:

• You run a single Plex server. Tautulli is more mature, has a larger plugin ecosystem, and has been battle-tested. Don’t replace a working tool without a reason.
• You rely on Tautulli’s notification agents and scripts — no direct equivalent exists in Tracearr yet.

Stay on Jellystat if:

• You run Jellyfin or Emby only. Jellystat is more established in that lane and has a longer track record.

Wait before adopting if:

• Your monitoring setup is high-availability and downtime matters. Single-developer projects at 1,500 stars carry different stability guarantees than established tools. Watch the GitHub releases for another few months first.
• You’re evaluating for any commercial or redistributed context. Audit the AGPL-3.0 license requirements carefully.

---

Alternatives worth considering

• Tautulli — The established standard for Plex monitoring. Mature, large plugin ecosystem, notification agents that can trigger almost anything. Plex-only. If you only run Plex, this remains the better-proven choice.
• Jellystat — The Jellyfin/Emby equivalent of Tautulli. Free, Docker-based, well-regarded in the Jellyfin community. Does not support Plex.
• Overseerr / Jellyseerr — Different category: media request management and user approvals, not monitoring. Often run alongside Tracearr in the same stack.
• Grafana + Prometheus + Exporters — Custom dashboard approach. Plex and Jellyfin both have community Prometheus exporters. More flexible, significantly more setup and maintenance overhead. Right choice if you already have observability infrastructure.

The practical shortlist for most self-hosted users is Tracearr vs Tautulli + Jellystat as separate installs. If you only run one server type, use the dedicated tool. If you run two or more, Tracearr’s unified dashboard removes an entire layer of operational duplication.

---

Bottom line

Tracearr solves a specific, real problem: the self-hosted monitoring space has been fragmented by server type for years, and no one wanted to run two separate tools after expanding from Plex-only to a mixed environment. The unified multi-server dashboard is the headline and it delivers. The sharing detection — impossible travel, device velocity, trust scores — ships at a depth that Tautulli doesn’t match. Everything is free, the compose setup is clean, there’s a first-party mobile app, and the developer is active and responsive.

The risk is proportional to the project’s age. At 1,567 stars and roughly a year of development, Tracearr hasn’t accumulated the edge-case hardening that Tautulli has. No independent reviews exist yet. If you’re running a Docker media stack with multiple server types, the deployment investment is low and the operational gains are real — this one is worth trying. If you’re on a single Plex server with a working Tautulli install, wait until Tracearr adds another year of release history.

---

Sources

1. Tracearr Official Website — “The modern monitoring platform for media servers” — tracearr.com — https://www.tracearr.com — Feature descriptions, AGPL-3.0 license, pricing ($0 forever), mobile app, community testimonials
2. Tracearr GitHub README — “Real-time monitoring for Plex, Jellyfin, and Emby servers” — github.com — https://github.com/connorgallopo/tracearr — Technical feature details, comparison table vs Tautulli/Jellystat, deployment requirements, sharing detection rules, REST API documentation, data import capability