Static-IP Relay
Get a stable endpoint for home servers behind CGNAT.
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.
Good first uses
- SSH and admin access
- VPN endpoints
- Remote desktop
- Cameras, NVRs, and game servers
When Static-IP Relay is the better fit
Use Public Tunnel for browser-based services when you mainly need a secure web path. 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.
If you are still diagnosing the network path, start with what CGNAT is or why port forwarding may fail.
Common questions
Does this give me my own public IP?
No. It gives you a stable DNSExit relay endpoint that outside clients can reach even when your home connection has no usable public IPv4.
Which services fit best?
SSH, VPN, RDP, cameras, game servers, and other TCP services that need a predictable address are the best first candidates.
Should I use this for a normal web app?
Usually not. If the service opens in a browser, Public Tunnel is typically the simpler place to start.
Does it work behind CGNAT?
That is the point. The local client connects outward first, so the service can be reached even when inbound IPv4 access is unavailable.
Need a route through CGNAT?
Tell us which protocols matter most so we can shape the first relay workflows around real use.