Phaze makes connections to cloud infrastructure to confirm identity, permissions, and authentication. The Phaze peer-to-peer negotiation and machine status updates also route through the Phaze infrastructure. The remote desktop connection data does not flow through the Phaze backend. That connection is peer-to-peer or routes through the on-prem relay installed inside your network.
Backend traffic to Phaze infrastructure
Name | URL | Purpose |
Phaze API | Authentication, permissions, device management, organization details | |
Phaze Websocket | wss://ws.phaze.app | Machine status and connection brokering |
Peer-to-peer traffic and ports
These are the default ports for the Phaze peer-to-peer traffic. Thes can be changed in the administration panel.
Ports | Protocol | Purpose |
31000 | UDP | Phaze host port |
31001 | UDP | Phaze client port |
41000 | UDP | Phaze relay port (optional) |
Network traffic for the Phaze Relay
If you're using the Phaze Relays, you will need to allow the Phaze Relay to communicate with the Phaze backend. For more details on the Phaze Relay setup, please review this article.
Ports | Protocol | URL | Purpose |
443 | Outbound TCP | wss://relay.phaze.app | Communicate with Phaze backend |
41000 | Inbound UDP | n/a | Port forwarding to the Phaze Relay |