Starr

Web UI for diagnosing and repairing the SQLite databases used by Sonarr, Radarr, Lidarr, Sportarr, Readarr, Prowlarr, Whisparr, and Bazarr.

  • Backup
  • Databases
  • Media Applications
  • Tools & Utilities
Web UI for diagnosing and repairing the SQLite databases used by Sonarr, Radarr, Lidarr, Sportarr, Readarr, Prowlarr, Whisparr, and Bazarr. It safely stops the target *arr container, takes a timestamped backup, runs SQLite PRAGMA repairs on the idle database, and starts the container back up, streaming every repair log line live to the browser.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

55/100 Fair

Maintained
93last commit 24 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
502 GB minimum RAM

Availability: platform listings confirmed today, links checked 33 days ago

GitHub stars
3
Open issues
0
Last commit
2026-10-27
Latest release
v1.3.11
License
GPL-3.0
Activity
declining

Checked 9 days ago - source: GitHub (Krippler/Starr)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 150 MB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start FE and BE nodes, and open their ports Start the FE (front-end) nodes first, then the BE (back-end) nodes, and keep the ports shown in the output open, such as 9010 for the FE change log and 9050 for BE heartbeats. If those ports are blocked, the cluster parts cannot talk to each other. source
  • Turn on NTP time sync before starting Install and enable the NTP (network time protocol) service on the machines. If their clocks drift apart, distributed operations can fail or become unreliable. source
  • Create and select the quickstart database Run the two SQL lines that create the quickstart database and then select it before running examples. This keeps sample tables in the intended database instead of the wrong one. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does Starr find my existing *arr containers?

Mount Starr at /appdata and expose the Docker socket. It then auto-discovers each *arr container, URL, database path, and bridge IP.

How is the Starr web dashboard protected?

The browser UI is gated by a single Web Key, so you can manage repairs without using SSH.

Does Starr back up the database before a repair?

Yes. It takes an automatic timestamped backup before every repair, and backups are zstd-compressed by default.

Can scheduled repairs avoid running when the database is already healthy?

Yes. Scheduled runs can use skip-if-clean, which probes quick_check and foreign_key_check before doing the full repair.

How does Starr handle stopping and restarting the target *arr app?

It stops the app with docker stop or the app shutdown API, re-polls for stability, and is designed to restart the container after the repair.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads