Appearance

Local Use and Optional Cloud ​

Your self-hosted OmniLux server remains useful when OmniLux Cloud is unavailable. Local ownership is the product promise; account-linked services are separate conveniences.

Available: local use ​

These local behaviors do not require a live OmniLux Cloud session:

  • local administrator access;
  • library browsing and search;
  • local media playback;
  • read-only library scans; and
  • direct access on your home network.

A user-managed VPN can extend that private network path without turning it into OmniLux-managed relay.

Private beta: account linking ​

An approved release may offer account linking after local playback. Account-linked actions such as a new server claim, an invitation, or an account change can pause when OmniLux Cloud is unavailable.

A cloud interruption must not delete the local administrator, rewrite source media, or remove the household library.

Planned: OmniLux-managed relay ​

OmniLux-managed relay is not generally available. When offered, it will require an eligible account, a linked and online server, available service capacity, and a supported client.

Direct LAN access and a user-managed VPN remain separate from relay and are not counted as relay usage.

Unavailable ​

  • A promise of unlimited or perpetual relay capacity
  • A cloud requirement for direct local playback
  • A public relay path inferred from a plan name or prototype

Lifetime Membership and Founding Member are unavailable for checkout during the private beta. If those offers are approved later, both carry the same lifetime Family-level OmniPass entitlement; Founding Member adds recognition and any separately stated perks. That account-level entitlement does not make relay unlimited.

If an account-linked feature stops working ​

  1. Open the server directly on the home network.
  2. Confirm local browsing and playback still work.
  3. Check the account-linked feature again after cloud service returns.
  4. Contact support with the visible error and approximate time if the problem continues.

Never send claim codes, relay tokens, private keys, raw databases, or unredacted environment files to support.