New in 1.0.0
Nexview can now procure through nexcrate: one app instead of Radarr and Sonarr, several versions per title. An assistant walks you across, and every title says what it is waiting for.
All about nexcrate →
A media discovery dashboard for your own server: new releases from TMDB, marked with what is already in the library. Requests land straight in Radarr and Sonarr, or in nexcrate. Completely free: no price, no subscription, no paid extras. Every feature for everyone.
Free · open source · self-hosted · one Docker container
Coming from Seerr?
Since 0.29.0 the setup wizard reads your running Seerr installation: Radarr, Sonarr, the mail server, accounts with their pictures and quotas, the block list. You tick what comes along; it is written in one go.
How the move works →
A start page of their own for each person, ratings and trailers on the title, and the request button right beside them.
Take a look →
Twenty checks, quotas in item counts and gigabytes, six tabs of analytics. The part Seerr and Ombi do not have.
Take a look →
Wave through documentaries rated 7 and up, do not even start with poorly rated films. Whatever no rule matches takes the usual route.
Take a look →
Plex, Jellyfin and Emby keep running, all three at once if you like. Your files stay exactly where they are.
Take a look →
New in 1.0.0
One connection instead of four
Nexview can now procure through nexcrate: one app instead of Radarr and Sonarr, several versions per title. An assistant walks you across, and every title says what it is waiting for.
All about nexcrate →
Nexview downloads nothing itself. It passes wishes on to Radarr and Sonarr or to nexcrate, and they do the rest.
One container, one wizard. Every service can be skipped and added later.
Radarr and Sonarr are built for the person running the server, not for flatmates, parents or friends.
If you would rather not hand out that access, the wishes reach you by chat and you enter them by hand.
Nexview is the layer in between: everyone browses and requests, the connections stay with you.
Nexview sits in front of Radarr and Sonarr: it shows what is out there, takes requests and passes them on. Nothing more, and that is exactly the point.
Nexview passes it on, Radarr and Sonarr do the rest, the state follows along by itself.
The same software, two very different jobs, and both get answered without the other getting in the way.
One account per person, so everybody gets their own recommendations.
A child account for every child, its own view, its own categories, and wishing instead of requesting.
Everybody else simply requests; you approve if you like, or let it run straight through.
Roles: approvers may approve without ever touching your keys.
Quotas per person and period, counted separately for movies and shows.
A ticket centre instead of shouted requests, and messages on your phone the moment something waits.
The credentials for TMDB, Radarr, Sonarr and the media server are stored encrypted in the database, not in configuration files, not in plain text.
Not directly to TMDB, Radarr or Sonarr, everything goes through the Nexview backend, and your credentials never leave your server. The one exception is signing in with Plex: that deliberately goes straight to Plex, so your Plex password never reaches Nexview.
The proof that you are signed in lives in a cookie no script can read, no longer in the browser's storage. Repeated failed attempts are slowed down. The browser loads no foreign scripts. And sign out everywhere ends every session of your account on every device without changing your password, including the one you left open on somebody else's machine.
What is stored are users, settings and requests. Media files stay exactly where they were before.
More than half of the application is not there for the people who request things, it is there for the one person who keeps it running.
An admin dashboard with twenty checks running in the background. Every finding says what follows from it, and takes you exactly where you fix it.
The most valuable finding is the quietest: requests that have been “searching” for two weeks. In the interface that looks like work, not like a standstill.
Statistics & analysis in six tabs, right down to who is watching what right now and whether your server is transcoding for it.
Quality profiles from six everyday questions instead of forty decisions, and pushed to several instances.
Source reconciliation: where Radarr, the media server and Nexview's own books disagree. That is where the errors nobody looks for are hiding.
A tile for Homepage or Homarr, one call, ready-made snippets to copy.
Every feature page, ordered by who ever gets to see the thing.
If you know Seerr or Ombi, you know the requesting. Nexview starts one step earlier and stops one step later. Nine things that do not work there:
| Feature | Seerr | Ombi | Nexview |
|---|---|---|---|
| Rules that decide requests automatically | profile and folder only, never a decision | per role only, nothing about the title | yes, by rating, genre, year and what is already here |
| Quotas by disk space, on top of the item count | item count only | item count only | yes, both apply at once |
| An operator dashboard: what is stuck right now | no | no | yes, twenty checks |
| Guided picking for tonight: a few questions instead of a search | no | no | yes |
| Child accounts with a view of their own | no | roles only | yes |
| Where Radarr, the media server and requests disagree | no | no | yes |
| Sign-in through external providers (OpenID Connect) | pull request open | partly | yes, Authentik, Keycloak, Pocket ID, Google |
| Quality profiles | pick one | pick one | build, hand out, keep up to date |
| Shows what nobody has watched in a long time | no | no | yes, with a deletion window |
Every release gets a post: what arrived, and why it is built that way.
Anybody using Nexview spots sooner than any plan where something is missing or awkward. That is what the suggestion list on GitHub is for: whatever arrives there gets read and considered, and what makes sense and fits the whole gets built. No forum account, no chat sign-up; one sentence is enough.
Nexview organises what sits in your library. Where the files come from is your decision, and the better answer is rarely a torrent.
Movies exist because people make a living from them: camera, editing, sound, and somewhere a person who spent three weeks on four seconds. Buy a ticket, rent it, subscribe, that is what makes the next movie possible.
And go to the cinema. For the screen, for the sound no soundbar can manage, and for the two hours where the phone stays in your pocket.
Nobody ever met the love of their life on a file-sharing site. In a cinema, plenty have. So: get popcorn, sit at the back, and kiss.
Nothing. The source is licensed under the AGPL-3.0, and you run it yourself.
No. There is no sign-up with us, no account and no price, Nexview runs on your server.
Yes, in two ways. Everybody subscribes their own devices under Profile, Web Push and gets what concerns them there, even while Nexview is closed. In addition, an administrator points the installation at ntfy, Gotify, Telegram, Discord, a plain webhook, Apprise or an e-mail address as shared inboxes; each inbox picks what it wants to hear about. The in-app bell and your own e-mail address stay alongside.
No. Nexview runs perfectly well without a media server, the setup wizard does not even ask for one. Without Plex you lose exactly three things: signing in with a Plex account, the “In library” marker and the watched marker.
Yes, all three: Plex, Jellyfin and Emby. They can be connected at the same time, the watched state is then merged across them.
Yes. Nexview passes requests on; searching and downloading is done by Radarr for movies and Sonarr for series.
Yes. A single Docker container, typically on a Synology or a home server, there as a Container Manager project from the compose file.
Yes, on its own subdomain anyway, and also under a sub-path of a shared domain like yourdomain.com/nexview: one environment variable (NEXVIEW_URL_BASE) is enough, and both common proxy styles work. Copy-paste examples for nginx, Caddy, Traefik and Nginx Proxy Manager are in the README.
Without a TMDB key Nexview starts with sample data. You can add the keys later in the wizard.
No. Users only see their own requests, children get an account of their own with a view of their own, the block list limits requesting.
Where they were. Nexview stores users, settings and requests, no media.
Both, switchable, including the movie titles and descriptions themselves.