Static-IP Relay is for the harder cases: SSH, VPN, RDP, cameras, game servers, or other TCP services that need a predictable public endpoint even when your home connection has no usable public IPv4.
TCP services that need a predictable address.
Service opens in a browser? Public Tunnel →
The local client connects outward first, so the service can be reached even when inbound IPv4 access is unavailable.
Pick by what kind of service you need to reach.
Use Public Tunnel for browser-based services when you mainly need a secure web path.
Public Tunnels →Use Static-IP Relay when your service is not just a web page, or when another system needs a stable endpoint to connect to repeatedly.
Get started →If you are still diagnosing the network path, start with what CGNAT is or why port forwarding may fail.
Understand why some home connections cannot receive direct inbound traffic at all.
Read guide → GuideCheck the common failure points before deciding the router is the whole story.
Read guide → GuideNo. It gives you a stable DNSExit relay endpoint that outside clients can reach even when your home connection has no usable public IPv4.
SSH, VPN, RDP, cameras, game servers, and other TCP services that need a predictable address are the best first candidates.
Usually not. If the service opens in a browser, Public Tunnel is typically the simpler place to start.
That is the point. The local client connects outward first, so the service can be reached even when inbound IPv4 access is unavailable.
Tell us which protocols matter most so we can shape the first relay workflows around real use.