Access anywhere. No port forwarding.
Sign in once. Reverse-tunnel relay handles NAT traversal. Use the public hub or self-host it.
NAT is your enemy
$ ping home
PING home.local (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=2.1 ms
$ ping home --remote
ping: cannot resolve host: NAT blocks direct access
Solution: use Phlix Hub relay.
Your media server sits behind your router's NAT. Your phone on 4G can't reach it. Neither can your friend at their house. Port forwarding is insecure and a hassle.
Reverse-tunnel relay
$ phlix hub --connect
Connecting to hub.phlix.io...
Authenticated as user@example.com
2 servers registered:
- Home NAS (online)
- Cabin Server (online)
Relay ready. Clients can now connect.
Phlix Hub opens an outbound tunnel from your server to a relay. Clients connect to the relay. No inbound ports needed.
Your server, your hub
Public Hub
Use hub.phlix.io for free. No setup required. Your credentials stay yours — the relay just forwards traffic.
Free to use
Self-Hosted
Run phlix-hub on your own VPS. Full control. You handle authentication and relay infrastructure.
Full control
Built secure
Encrypted tunnels
All relay traffic is encrypted. No plaintext streaming over the tunnel.
User auth
Hub authentication is separate from your media server. OAuth 2.0 + JWT.
No media storage
The relay only forwards binary stream data. Nothing is persisted on the hub.
Self-hostable
Audit the relay code yourself. Run it on infrastructure you control.
Open source relay
phlix-hub on GitHub
Cloud directory + reverse-tunnel relay. MIT licensed. Deploy on any VPS.
→