Skip to content

V1.0.0 - Initial Release

Choose a tag to compare

@Kazwahs Kazwahs released this 19 Aug 19:15
· 4 commits to main since this release

The first tagged release of arrVantage — a unified web dashboard for your media automation stack, built so you stop tab-hopping between five different UIs.

What's included

Library management

  • Unified dashboard for Radarr, Sonarr, Lidarr, and book managers like Chaptarr
  • Library browsing, search, and status tracking (downloaded/missing/partial) per instance
  • Cast, filmography, and artist images pulled from TMDB/TVDB/Fanart.tv
  • Cross-instance search — one search box across every configured library at once

Media servers

  • Plex, Jellyfin, and Emby support: Now Playing, Recently Added, Watch History, and Users
  • Richer activity data via Tracearr and/or Tautulli where configured
  • One-click library rescan

Indexers & downloads

  • Prowlarr indexer health monitoring, with individual and bulk ("Test All") testing
  • qBittorrent and SABnzbd queue management (pause/resume/delete)

Requests & transcoding

  • Overseerr / Jellyseerr integration for content requests
  • Tdarr transcode stats — space saved, per-node worker and queue status

Home dashboard

  • A single overview page pulling live stats across every configured service — library sizes and file counts, media server status, indexer health, transcoder savings

Under the hood

  • Single Docker container, one config volume, no database required
  • Automatic builds via GitHub Actions (build → test → publish to GHCR) — no manual rebuild step for updates
  • CSRF protection, login rate limiting, and a non-root container by default
  • An automated test suite covering core logic, authentication, and the Prowlarr integration

Getting started

See SETUP.md for the full installation walkthrough, including a reference table for where to find every integration's API key.

A note on how this was built

This project was built with substantial help from Claude rather than hand-writing every line — see the README for the full story on why. Being upfront about that here too, at the first tagged release, not just buried in the README.


Feedback, bug reports, and feature requests are always welcome via Issues.