NeedPorts helps when your service works locally, your machine can reach the internet, but the public internet cannot reach your machine because of CGNAT, blocked inbound ports, or provider network restrictions.
Instead of relying on your ISP, router, or hosting provider to accept inbound connections, your machine opens an outbound tunnel to NeedPorts. NeedPorts gives you a stable public endpoint and an assigned range of forwarded ports. Public traffic arrives at NeedPorts first, then travels through the outbound tunnel to your local service.
Examples: SSH, an inference API, a dashboard, Home Assistant, a game server, or a web app.
Outbound connections usually work even when inbound port forwarding is blocked by CGNAT or provider policy.
Users connect to your assigned public endpoint and dedicated forwarded ports.
The traffic reaches your machine without requiring router port forwarding, a residential public IPv4 address, or manual inbound firewall exposure at the edge.
127.0.0.1 unless that is intentional.Need stable inbound ports for Vast.ai or remote GPU workloads.
Why normal router rules fail behind carrier-grade NAT.
A practical troubleshooting checklist before choosing a fix.
Expose home servers, APIs, and dashboards from networks without public inbound reachability.
Choose a plan, install the client on the machine that needs inbound reachability, and use your assigned endpoint and ports for the service you control.
GPU host setup Self-hosted setup