Remote access comparison

Public Tunnel vs port forwarding: which do you need?

Both can make a private service reachable from the internet, but they solve different network situations and put the public entry point in different places.

Port forwarding

Best when you control the router, have a usable public IP, and are comfortable exposing selected inbound ports directly to your network.

Public Tunnel

Best when you cannot open router ports, are behind restrictive networking, or only need to publish one local web service through an outbound connection.

Quick comparison

Public IP requiredUsually yesNo
Router access requiredYesNo
Best fitServices you intentionally expose from your own edgeOne local web app that needs a reachable public URL
CGNAT friendlyNoYes

How to choose

If port forwarding already works and your only headache is a changing IP address, Dynamic DNS may be all you need. If the router is locked down, the ISP uses CGNAT, or you want an outbound-only path for a local web app, Public Tunnel is the cleaner fit.

Still choosing?

Start with the service comparison, then start Remote Access if your network blocks the old-school path.

Explore by goal

Keep moving with the guide that matches the problem.

;