Remote access should not depend on which internet connection is active

When your router fails over from fiber or cable to LTE, 5G, fixed wireless, or another ISP, inbound access often breaks because the public IP and port-forwarding path changed. NeedPorts gives remote users one stable public endpoint while your host reconnects outbound over whichever internet path is available.

Get public forwarded ports Read the CGNAT guide

Why failover breaks inbound access

Most failover setups focus on outbound internet: can users browse, send traffic, and keep cloud sessions alive? Public inbound access is harder. Your old WAN IP, router forwarding rules, and DNS may no longer point to a reachable path after failover.

Without a stable endpoint

Remote users need a new IP, new DNS target, or a backup-specific port-forwarding setup that may not be possible.

With NeedPorts

Remote users keep using the same NeedPorts endpoint and assigned ports while the local tunnel client reconnects outbound.

Where this is useful

admin SSH access to a machine at home or a small office
dashboards and monitoring pages for remote equipment
self-hosted applications that need to stay reachable during ISP outages
support access into a site where the backup WAN is LTE/5G or CGNAT
game servers, APIs, Home Assistant, and lab services that need stable inbound ports

How to think about the architecture

Your router or firewall handles WAN failover.
The NeedPorts client runs on the machine that hosts the service or can reach it locally.
The client opens an outbound connection to NeedPorts over the active WAN.
Remote clients connect to the stable public NeedPorts endpoint instead of depending on the active ISP address.

What to verify before relying on it

The service works locally on the host or LAN.
The host can make outbound internet connections after failover.
Local firewall rules allow the service and the NeedPorts client.
Your failover router actually moves outbound traffic to the backup WAN when the primary WAN drops.

Plans start small

NeedPorts plans start at $5/month or $30/year for 25 dedicated ports. That is enough for many remote-access, self-hosting, and backup-connection use cases, with larger plans available when you need more services exposed or more throughput.

Get Started Back to Guides