Appearance

Remote Access ​

OmniLux begins on the network you control. Prove local playback first, then use a private network you already manage if you need browser access away from home.

Private beta

Direct LAN access is the supported foundation. A user-managed VPN can extend that private path after local playback is stable. OmniLux-managed relay is not generally available.

Available: same-network browser access ​

On your home network, open the local OmniLux server address in a modern browser. This direct path does not require an OmniLux Cloud session or paid relay plan.

If the page does not open, confirm that the device is on the same network, the server is ready, and the local firewall allows the approved OmniLux port. Fix local access before adding a remote path.

Private beta: user-managed VPN ​

A VPN you already operate can place a remote device on a private network with the server.

  1. Confirm OmniLux works on the local network.
  2. Configure the VPN outside OmniLux using its own security guidance.
  3. Connect the remote device to that VPN.
  4. Open the same private OmniLux address in the browser.
  5. Disconnect the VPN and confirm the address is no longer publicly reachable.

OmniLux does not provision, manage, or audit that VPN. Do not expose the OmniLux runtime directly to the public internet.

Planned: OmniLux-managed relay ​

OmniLux-managed relay is planned as a separately gated convenience when a direct private path is unavailable. It is not generally available and must not be inferred from an account, plan name, prototype, or internal service.

When relay is offered, its release notice will state eligibility, capacity, session limits, and supported clients. Direct LAN and a user-managed VPN remain separate from relay entitlement.

Unavailable ​

  • Public router port-forwarding guidance
  • Direct public exposure of the OmniLux runtime
  • Automatic NAT traversal
  • A new OmniLux-managed mesh network
  • A generally available relay service