A Port Forwarding Alternative for 5G Home Internet

5G home internet is fast enough for a lot of homelabs. The catch is inbound access.

The problem

Many 5G ISPs use CGNAT, so classic router port forwarding simply has nowhere public to attach.

That is why Dynamic DNS often disappoints here. DNS can point to a name, but it cannot punch a route through an ISP NAT you do not control.

What people usually try

• Use cloud tunnels for HTTP-only apps.
• Use a mesh VPN for private access.
• Build a VPS gateway if you have time to maintain it.

There is no single correct answer. The right tool depends on whether you need private access, public access, web-only traffic, media streaming, game ports, or full control.

The simpler shape

PUBLIC-IP.CLOUD is the lightweight version of the VPS gateway idea: static public IPv4, dashboard port rules, and a WireGuard path home.

The cleaner model is boring on purpose: public IPv4 outside, WireGuard tunnel back home, and explicit port rules in the middle.

Where PUBLIC-IP.CLOUD fits

PUBLIC-IP.CLOUD gives your home server a static public IPv4 for $1.99/mo. New customers can use FREE-1MONTH for the first month free, and you can cancel anytime. You open only the ports you need from the dashboard. TCP port 25 is blocked by policy, and spam, scanning, malware, and attack traffic are not allowed.

It is not a VPS and not a privacy VPN. It is the public ingress layer many home servers are missing: one static public IPv4, explicit port rules, and a WireGuard path back to your homelab.

Good fit

• Starlink, 5G home internet, double NAT, and ISP CGNAT connections
• Home Assistant, NAS, Jellyfin, Plex, reverse proxies, and small web apps
• People who tried router port forwarding and Dynamic DNS but still cannot connect
• Anyone who would rent a cheap VPS only to forward traffic home

Quick setup

1. Create an account.
2. Add your WireGuard public key or use the starter config.
3. Open the public TCP/UDP ports you want.
4. Point your domain or clients at the assigned static public IPv4.

Bottom line

If building the gateway is the hobby, a VPS is still a good project. If the service is what you actually care about, managed static IPv4 ingress is the shorter route.