Digarr

Digarr is an AI-powered music discovery engine for self-hosted music stacks.

  • Media Applications
  • Tools & Utilities
Digarr is an AI-powered music discovery engine for self-hosted music stacks. It connects to Lidarr, Last.fm, ListenBrainz, Spotify, and more to find new artists and albums you will actually like, drawing on your listening history or a chosen mood. It supports auto-playlists, subscription feeds, mood-based discovery, and genre browsing, and ships with a built-in embedded database so no separate PostgreSQL container is needed.

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.

73/100 Good

Maintained
100last commit 15 days ago
Popular
50331 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM
Security check
71no serious findings, 4 minor, CI, tests

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

GitHub stars
331
Open issues
15
Last commit
2026-11-06
Latest release
v2.2.1
License
MIT
Activity
rising

Checked 10 days ago - source: GitHub (iuliandita/digarr)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Easiest start: PGlite built-in database For the easiest start, download the PGlite (built-in database) Docker Compose file and .env settings file, edit the .env, then start Digarr with Docker Compose. If you skip the .env edits, the container may start with wrong settings or need to be recreated. source
  • First run needs AI provider and model On first run, choose an AI provider and model (the service and which AI model to use) because Digarr cannot complete setup without them. If you add Lidarr or Emby, enter the full details together—URL, API key (access token), and Emby user ID—so the connection is not incomplete. source
  • Separate Postgres needs a password file If you use the external PostgreSQL (separate database) option, put one database password in the secrets folder’s password file and edit .env before starting. Both Postgres and Digarr read that same password file, so a missing file or wrong permissions can keep the app from reaching its database. source
  • Data folder and external database Data is stored in the mapped data folder (/mnt/user/appdata/digarr/data), which must be writable by the container user (uid 1000). To use an external PostgreSQL instead, set the (advanced) Database URL variable. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I use my own AI provider or a local model?

Yes, you can bring your own AI provider or use a local model.

Can I approve only one album instead of an artist's full discography?

Yes, it recommends individual albums and lets you approve a single album without grabbing the whole discography.

Does Digarr support scheduled discovery runs?

Yes, it supports scheduled discovery runs.

Answers sourced from docs.elfhosted.com, github.com, github.com

Community

Collected 53 days ago - public community threads