docs.neptuneplayer.com
Warning: If this is a folder, all contents including subfolders and documents will be deleted.
Define path-based access rules for sections of your wiki, then assign users to groups in the Users tab. Rules are evaluated in order. First match wins.
Create and manage backups of your wiki data. Backups include all documents, images, and configuration files.
Neptune keeps the same native Home, Library, Search, playback, and Settings experience across media-server platforms.
The backend supplies the account, library, artwork, stream, and watch-state data behind those screens.
This invariant is the One Neptune architecture: parallel provider data adapters are acceptable; parallel provider interfaces are not.
Backend support is capability-based.
A server can support core browsing and playback even when an optional administration, plugin, sync, or download feature is unavailable.
Neptune hides or explains unsupported actions instead of sending commands intended for a different server platform.
Neptune is designed for Jellyfin, Emby, Plex, and additional media-server backends.
Availability can vary by release.
Jellyfin is Neptune's primary and most complete backend.
It supports normal server discovery and manual addresses, username/password authentication, and Quick Connect.
The optional Neptune Plugin Suite is built for Jellyfin.
Depending on which suite components are installed, it adds features such as:
The app still works without the suite; those server-assisted features simply remain unavailable.
Plex support remains planned.
Neptune already reserves a branded setup choice and the Ember theme, but those presentation pieces do not by themselves make Plex a usable backend.
The setup card remains unavailable until authentication, server selection, account storage, catalog, images, playback, reporting, and both Apple-platform integrations pass the same release checks as other backends.
Seerr is configured independently from the media backend.
The saved Seerr session is tied to the exact backend, media server, and user.
Switching providers cannot silently restore another account's Seerr session.
The Neptune Plugin Suite and its dashboard are currently Jellyfin extensions.
For Jellyfin users, Server Defaults can seed a new Neptune profile and MDM can manage synchronized settings.
Local user settings remain available on every supported backend.
Provider-side subscriptions are separate from Neptune Pro.
Neptune respects a server's feature or playback restrictions and does not use Neptune Pro to bypass them.
Servers and credentials are stored separately by backend, server, and user.
Accounts on two providers can safely use the same username or internal media ID without sharing data.
If a beta backend is disabled in a particular Neptune build, the app does not contact it or attempt a background restore.
The saved connection is retained rather than deleted, so it can be restored when support is enabled again.
| Symptom | What to check |
|---|---|
| A backend card says it is not ready | That provider is disabled in the installed Neptune build |
| A feature disappears after switching servers | The new server, account policy, subscription, or companion may not advertise that capability |
Continue with Server Connection to add a server or Authentication for sign-in details.