If you run Home Assistant at home and normal router port forwarding does not work, your ISP may be using carrier-grade NAT. NeedPorts gives you a stable public endpoint so your Home Assistant instance can be reached remotely without relying on your ISP to provide a public IP.
Home Assistant itself may be working perfectly on your local network. The problem is usually at the network edge: your ISP connection is behind an upstream NAT layer, so inbound traffic never reaches your router even if your local forwarding rule looks correct.
Remote access to dashboards, automations, status pages, or device controls from outside the home.
Port forwarding looks correct on the router, but Home Assistant is still unreachable because the ISP NAT layer blocks unsolicited inbound traffic.
If your goal is strictly private remote access for yourself, private overlay networking may be enough. But when you need a stable public endpoint, want to avoid ISP dependency, or want a broader inbound-access solution for multiple services, NeedPorts is the cleaner fit.
After setup, you can use the self-hosted verification helper on one assigned port and confirm that the public endpoint is reachable from another machine. That gives you a fast sanity check before pointing real traffic at the service.
NeedPorts plans start at $5/month or $30/year for 25 dedicated ports, which is enough for many Home Assistant and self-hosted remote-access setups.
If you want the broader context, read the self-hosting guide, the homelab guide, and the home-server remote access guide.