Appearance

How the OmniLux System Works ​

OmniLux keeps the household media core on hardware you control. Optional account services and planned connection tools sit around that core rather than underneath it.

Your local media home ​

Three pieces create the direct household experience:

  1. Your media folders remain the source of the library and stay read-only during the private beta.
  2. Your OmniLux server scans those folders and stores its database, artwork, settings, cache, and transcodes separately.
  3. Your local browser connects directly to that server for browsing and playback.

A cloud session is not required for direct local playback.

Optional account services ​

An OmniLux account can add account-linked choices when an approved release makes them available, such as server status or household invitations. Linking an account happens after local setup and first playback.

The account does not become the owner of the source library, the local administrator, or the direct LAN connection.

Planned connections ​

Guided migration, OmniLux-managed relay, and native clients are planned. They remain separate from the local product foundation and are not generally available in the private beta.

Plex, Jellyfin, and Emby may become optional comparison or migration sources. OmniLux does not need one of them to run.

Data ownership ​

Any future workflow that intentionally changes source files will need a separate opt-in design, a preview, and explicit safety guidance. It is not part of the private beta.

What happens when another service is unavailable ​

  • Local browsing and playback continue without a live OmniLux cloud session.
  • A cloud outage does not rewrite or remove source media.
  • Loss of a planned remote service does not silently route traffic somewhere else.
  • A planned migration stops before cutover when it cannot complete safely.
  • An installation stops when no current approved release is available.