Guides
Five pages on getting a machine you own reachable from the internet. Each one answers the question fully, including when the answer is a free tool rather than us.
Start here
If something outside your network cannot reach a machine you own, the first thing to establish is why — the fix for an address that keeps changing is different from the fix for an address nothing can route to. These pages are ordered roughly the way the problem usually unfolds.
1 · Reach a home server behind CGNAT
Why carrier-grade NAT breaks inbound connections specifically, a thirty-second test to confirm you are behind it, and every option that works — starting with the two that are free. Read it.
2 · Static IP for a home server
“Static IP” means two different things and most people need the other one. Dynamic DNS, an ISP static address, IPv6, a VPS, or a leased address — what each actually gives you. Read it.
3 · An ngrok alternative that gives you a real IP
ngrok is the best tool there is for an afternoon and the wrong one for a year. What replaces it, including three replacements that cost nothing. Read it.
4 · Cloudflare Tunnel vs a dedicated IP
For a web service Cloudflare Tunnel beats buying an address on most axes that matter, and the page says so. Also the four specific places it stops fitting. Read it.
5 · Tailscale Funnel vs a public IP
Most people who think they need a public address need a private network instead. Where that stops being true. Read it.
What we sell, in one line
One public IPv4 address from our own 23.187.152.0/24, announced by BGP from AS396500
and routed to a machine you already own, from $10/month. It is inbound-only on the
base plan, outbound port 25 is blocked, failover between our two hubs takes minutes rather than
seconds, and we publish no availability figure because we have not been running long enough to have
measured one. It is not a VPN and we do not sell anonymity.
Plans and prices.