07Phlix Hub
A reverse-tunnel relay and a cloud directory. It exists so your server can stay on your LAN and still answer from anywhere.
01What the Hub does
Sign in once. Reverse-tunnel relay handles NAT. Self-hostable, or use the public hub.
The relay solves NAT traversal: the server opens the tunnel outward, so no port forwarding and no third-party tunnel service is required. The hub also acts as a directory, which is what lets one sign-in reach several of your servers.
Nothing has to be exposed to the internet. The server keeps answering on its LAN address; the relay is what a phone or a Roku at a friend's house talks to instead.
02Self-host or use the public hub
Both are supported. The public hub is the shortest path; self-hosting keeps the directory and the relay on your own infrastructure.
- Source
- github.com/detain/phlix-hub
- Role
- Cloud directory + reverse-tunnel relay
- Licence
- MPL-2.0, same as phlix-server
03Hub mode in clients
The Roku and Windows clients list Hub mode among their capabilities. Any client can reach a server directly on the LAN.
-
01
HLS playback, Hub mode, skip intro/outro, SyncPlay.
-
02
Electron + React + TypeScript, system tray, media keys, Hub mode.
-
03
Capabilities and status for Roku, Samsung Tizen, Windows, Mobile and DLNA.