If your ISP uses carrier-grade NAT, normal router port forwarding often fails even when your local setup looks correct. NeedPorts gives your homelab or home server a stable public endpoint and dedicated forwarded ports so SSH, dashboards, APIs, and other services can be reached remotely.
Homelab remote access usually means one or more of these:
Your service listens locally, your router rule exists, and the machine is reachable from inside the LAN.
Your ISP NAT layer is still in front of your router, so inbound traffic never reaches your network edge in the first place.
If your goal is private overlay access only, a private networking tool may already be enough. But when you need a real public endpoint, predictable addressing, or more than one exposed service, NeedPorts is usually the better fit.
This is especially true when you want to reach your server from arbitrary networks, support multiple inbound services, or expose things like APIs and game servers that expect direct public reachability.
For self-hosted installs, NeedPorts includes a small helper called needports-selftest. After install, run it on one assigned port and test that public endpoint from another machine.
Works on Ubuntu and other Linux hosts, including Raspberry Pi and ARM64 systems.
needports-selftest 30450Plans start at $5/month or $30/year for 25 dedicated ports, which is enough for many homelab and remote-access use cases. Larger plans are available if you need more services exposed or more throughput.
If you want the broader context, read the CGNAT guide, the self-hosting guide, and the home-server-without-a-public-IP guide.