Comparison
Aurral vs Jellyseerr for Music: Requests or Discovery
Jellyseerr and Overseerr brought the Plex request model to music, and for a lot of people that was the missing piece. It solves a different problem from Aurral, and knowing which one you have decides whether you need the other.
The short answer
If you know what you want
Jellyseerr. A request interface is exactly right for that.
If you do not know what you want
Aurral. That is the whole problem it exists to solve.
If you are running Lidarr already
Both. Requests feed Lidarr, discovery feeds Aurral.
The difference in one sentence
A request tool requires you to already know the artist or album. A discovery tool supplies the artist you did not know to look for.
That is a genuine gap rather than a feature preference. People who use request tools well already know their music. People who want to be surprised do not, and no amount of interface quality changes that.
| Capability | Jellyseerr for music | Aurral |
|---|---|---|
| Request a specific artist | Yes, this is the core feature | Yes |
| Request a specific album | Yes | Yes |
| Recommend an artist you do not know | No | This is the core feature |
| Build a weekly discovery mix | No | Yes, via Flows |
| Fetch music automatically without a request | No | Yes |
| Multi-user request tracking | Yes | Yes, plus per-user recommendations |
| Filter release quality before downloading | Limited | Yes, with post-download verification |
| Nearby concerts | No | Yes, with Ticketmaster |
Why a request tool cannot recommend
The design assumes a known-unknown. Someone wants an album, requests it, a download runs, and the request gets tracked until it is available. Everything about that flow presumes the requester already has something in mind.
A recommendation has to come from somewhere, and the somewhere is a signal about your taste. Jellyseerr has no such signal because it only ever sees explicit requests. Adding recommendations to it would mean building exactly the layer Aurral is.
Using both together
This is the sensible arrangement and it is not redundant. Jellyseerr handles the requests that come from you and your household, with tracking and notifications. Aurral handles the expansion, filling your library with artists you would not have searched for.
They also compose: use Aurral to discover an artist, then find something specific from them, then request it through your normal request flow. The discovery supplies the search terms you would not have had.
- Keep your request tool for anything you can name.
- Let Aurral fill the gaps you cannot name.
- Promote any Aurral discovery you like into your request flow.
- Let Flows run on a schedule so the expansion is automatic.
Where Aurral is genuinely better on its own
When there is no request tool at all, which is common with Lidarr setups where Aurral manages the library itself. Then Aurral is doing requests and discovery, and the quality profile with post-download verification is doing something no request tool offers.
Quality verification is worth dwelling on. A request tool searches, downloads and imports. Aurral searches, downloads, then reads the actual file and rejects it if the format, bitrate, sample rate or bit depth does not match the profile. That closes a hole most request workflows leave open.
Frequently asked questions
Is Jellyseerr or Aurral better for music?
They answer different questions. If you know what you want, a request tool is better. If you do not, you need discovery, and only Aurral provides it.
Can I run both at the same time?
Yes, and that is the sensible setup. Requests for what you can name, discovery for what you cannot. Both feed the same library.
Does Aurral replace a request interface?
No. It can request artists and albums itself when connected to Lidarr, but it does not replicate the request tracking, notification or household approval workflow that request tools are built around.
Why does Aurral check the file after downloading when Jellyseerr does not?
Because search results lie about bitrate and format. Aurral reads the finished file and rejects anything that does not match the enabled quality tiers.
Other comparisons
Aurral vs Lidarr
They are not competitors. One manages the library, the other decides what goes into it.
Aurral vs Spotify
Discovery shaped by your own history, no subscription, no DRM, and files you keep forever.
Aurral vs Navidrome
Navidrome plays. Aurral decides what to play. They sit next to each other, not on top.
Try Aurral against Jellyseerr yourself
One container, one port, and it works alongside whatever you already run. Nothing you have needs to be replaced.