Compared
Nexview, Seerr and Ombi, honestly side by side.
If one of the other two already runs for you, you are not looking for a replacement. You are looking for a reason. Over forty features stand side by side here, grouped by audience, including those where Nexview comes off worse.
The short answer
Three programs, three emphases.
Seerr
The yardstick for requesting. Mature, a large community, on every list of self-hosted tools. If requesting is all you need, you are well served.
Ombi
The oldest of the three, around since 2016. It is the only one that can request music through Lidarr, and it has an app in the store. Since the community moved over to the Seerrs it has become quieter.
Nexview
Starts a step earlier, with finding, and ends a step later: quotas in gigabytes and count, checks, library reconciliation. Young and small, but thorough in those places.
Coming from elsewhere?
What changes when you switch.
Coming from Seerr?
You know requesting already, and it works the same in Nexview. What differs is before and after. Before comes the question of what to watch today: suggestions per person, ratings on the title and, if nothing helps, an assistant that asks a few questions. After comes the operator side that Seerr does not have in that form: checks that say what is stuck, quotas in gigabytes and a reconciliation between procurement and your media server. You would give up a large community and a lot of maturity. The move itself is a path in the setup assistant: Nexview reads your running Seerr and takes over services, accounts and images. How the move works.
Coming from Ombi?
Two things Ombi can do that Nexview cannot: request music through Lidarr, and a proper app in the store. For music there is nexbeat; if you need the app in the store, stay with Ombi. Otherwise it is worth a look: suggestions per person, child accounts with a view of their own, sign-in through OpenID Connect, encrypted backups. The interface decides anyway whether your people use the thing or keep asking you in the chat.
The features
Side by side, grouped by audience.
The last group names where Nexview comes off worse. It belongs here. Partly means there is something along those lines, but not the same thing.
For your people
| Feature | Seerr | Ombi | Nexview |
|---|---|---|---|
| Curated suggestions per person | Partly | Partly | Yes |
| Ratings from IMDb, Rotten Tomatoes and Metacritic on the title | Partly | No | Yes |
| Movies and series kept apart instead of mixed | No | No | Yes |
| Guided pick for tonight: a few questions instead of a search | No | No | Yes |
| Child accounts with a view of their own | No | Partly Roles only | Yes |
| Release calendar with your own titles | No | No | Yes |
| People as favourites, feeding the suggestions | No | No | Yes |
| Watched markers per person | No | No | Yes |
| Bilingual, film titles and descriptions too | Partly | Partly | Yes |
| Messages to your phone | Many services | Many services | Seven channels, Apprise among them |
| Web push per person, without the operator | Yes | No Only third-party services and the Ombi app | Yes With the same ticks as e-mail |
| Report a problem / ticket centre | Yes | Yes | Yes |
| The media server's watchlist in the catalogue | Yes | Yes | Yes |
For you as the operator
| Feature | Seerr | Ombi | Nexview |
|---|---|---|---|
| Requests to Radarr and Sonarr | Yes | Yes | Yes |
| Procuring without Radarr and Sonarr, through nexcrate | No | No | Yes With a guided switch |
| Approvals and quotas per user | Yes | Yes | Yes |
| Invitation link that also creates the account on the media server | No That is what Wizarr is for | No Only importing shared Plex users | Yes For Jellyfin and Emby, for Plex the share |
| Rules that decide requests automatically | Partly Only profile and folder, no decision | Partly Per role only, nothing on the title | Yes By rating, genre, year, age rating and what is already there |
| Quotas by disk space, in addition to the count | No Count only | No Count only | Yes Both apply at once |
| Dashboard for the operator: what is stuck right now | No | No | Yes Checks in the background |
| Stuck downloads with a reason and fitting buttons | Partly Shows progress, no reasons | No | Yes With nexcrate or with Radarr and Sonarr |
| The title says what it is waiting for | No | No | Yes With nexcrate, per version |
| Who is watching what, across all media servers | No | No | Yes With the conversion state |
| Where procurement, media server and requests disagree | No | No | Yes |
| Quality profiles | Choose | Choose | Build, distribute, keep current, with Radarr and Sonarr. With nexcrate they live there. |
| Shows what nobody has watched for a long time | No | No | Yes With a deletion period |
| Statistics on requests, users and library | Partly | Yes | Yes Six tabs |
Your server
| Feature | Seerr | Ombi | Nexview |
|---|---|---|---|
| Media server | Plex, Jellyfin, Emby | Plex, Jellyfin, Emby | All three, even at once |
| Sign-in through the media server | Yes | Yes | Yes |
| Taking over existing accounts from the server | Plex only | Plex only | All three servers |
| Moving from a running Seerr installation | Not applicable | No | Yes During setup: services, accounts, images |
| Sign-in through outside providers (OpenID Connect) | No According to the documentation | Partly | Yes Several side by side, authentik in one step, Entra ID |
| 4K through a second instance | Yes | Yes | Yes Or as a version in nexcrate |
| Backup to download | No | Yes | Yes Encrypted ZIP |
| Restoring in the setup assistant | No | No | Yes |
| API token per account, with that account's rights | One global key | One global key | Yes Per person, read-only too |
| Home Assistant integration | Yes One global key | Yes One global key | Yes Per person, with their own figures and messages |
| Deciding requests from inside Home Assistant | No Only requesting and searching | No Only requesting | Yes Approve, decline, defer |
| Sign out everywhere, on all devices | No | No | Yes |
| Running under a sub-path behind the reverse proxy | No | Yes | Yes |
| Promised interface with a version promise | Yes | No | Yes Under /api/v1 |
| Self-hosted, open source, free | Yes | Yes | Yes |
To be honest
| Feature | Seerr | Ombi | Nexview |
|---|---|---|---|
| Requesting music (through Lidarr) | No | Yes | No |
| Own app for iPhone and Android | Installable as a web app | Yes | No As a web app on the home screen, push included |
| Voting on requests | No | Yes | No |
| How long it has existed | 2020 | 2016 | 2026 |
| Size of the community | Large | Large | Small |
The details on Seerr and Ombi come from their documentation, not from a test. If something is no longer right, let us know. A table that makes the others look worse than they are helps nobody.
Procuring
Seerr and Ombi talk to Radarr and Sonarr, Nexview also to nexcrate.
Seerr and Ombi pass requests on to Radarr and Sonarr. Nexview can do that too, with a second instance for 4K if you like. Beside it there is a second way: nexcrate fetches movies and series in one app, with several versions per title such as Full-HD and 4K. Nexview talks to it over a single connection, shows on the title what it is waiting for, and brings deleted files back from the recycle bin.
To be honest
Where Nexview trails.
Ombi can request music through Lidarr, Nexview cannot. For that there is nexbeat, the sister app for music: find artists and albums and request them from Lidarr or nexcrate with one click.
Nexview runs in the browser, on the phone too. For web push on iPhone and iPad you put it on the home screen.
Requests cannot be voted up or down. People with the role for it decide, or rules do.
Nexview is newer and has a smaller community than Seerr and Ombi. Whoever looks for answers online finds more for those two.