Appearance

Private beta guide ​

This guide is the single source for Private beta availability, participation, and release safety.

Current availability ​

Private beta

Private beta participation is reviewed, browser-first, and limited to approved households using a current approved release. Public server images, installers, and automated setup artifacts are Unavailable while release review is in progress.

What the private beta proves ​

An approved household should be able to run a verified standalone OmniLux server, mount a lawful library read-only, browse it in the local web interface, and reach first local playback without another media server or paid plan.

OmniLux browser player showing a Continue Watching prompt for a movie.
OmniLux in actionReturn to an unfinished title from the Continue Watching prompt. View full size

A good fit ​

  • You can run Docker on a NAS, mini PC, or always-on Linux host.
  • You manage a lawful household media library.
  • You are comfortable beginning in a modern browser.
  • You can keep OmniLux application storage separate from source media.
  • You are willing to report task outcomes without sharing titles, paths, playback position, raw IP addresses, or account contents.

Running Plex, Jellyfin, or Emby is not required. If you use one today, it can remain online while you compare.

Request and approval ​

  1. Review the current availability, fit, privacy, and participation boundaries on this page.
  2. Use Apply for private beta at the end of the guide.
  3. Sign in to the account app and explicitly confirm the request.
  4. Wait for account review and a separate current release notice.

Account approval and release approval are separate. An approved account does not authorize an old image, mutable tag, cached installer, or source reconstruction.

Release and storage safety ​

When a release is approved for a household, its notice names the exact immutable image digest and preparation guide to use. If no approved digest exists, stop safely.

The Private beta install contract requires:

  • one approved exact image digest;
  • source media mounted read-only;
  • separate writable app data, plugin, cache, and transcode paths;
  • a successful readiness check before setup;
  • local admin, scan, and first playback before account-linked features; and
  • a documented rollback and removal path.

Product boundary ​

Private beta ​

  • Standalone self-hosted server
  • Browser setup and local browser playback
  • Read-only library scan
  • Account-linked features only when the approved release notice names them

Planned ​

  • Guided migration from Plex, Jellyfin, or Emby
  • Native phone and TV apps
  • Broader household sharing
  • OmniLux-managed relay
  • Trusted extensions and additional media experiences

Unavailable ​

  • Public server installers or public download artifacts
  • Paid checkout during the Private beta
  • Any release not named by a current approved notice

Ready to apply? ​

If this release shape fits your household, submit the reviewed request. Applying does not install anything or authorize an old artifact.

Apply for private beta