PAGEKITE ALTERNATIVE
A dedicated public IPv6 instead of a relayed subdomain.
PageKite was one of the original "expose your localhost" tools — Python-based, HTTPS + arbitrary TCP through their pagekite.net relay. wayangi gives you a real, dedicated public IPv6 address instead — your DNS, your protocol, your traffic doesn't traverse a shared relay's subdomain.
wayangi vs PageKite at a glance
| What you get | PageKite | wayangi |
|---|---|---|
| Address | name.pagekite.me or your domain CNAME'd into theirs | Dedicated public IPv6 — point any AAAA |
| Runtime | Python 2/3 client (or compiled binary) | Single static Go binary, no dependencies |
| Protocols | HTTPS + raw TCP (configurable per port) | Any IP protocol — TCP, UDP, ICMP, QUIC |
| Bandwidth model | Pre-paid quota in GB | Unmetered (within fair use) |
| IPv6 native | No — HTTPS subdomain on shared relay | Yes — that's the whole product |
| Free tier | 1 month trial, then quota-limited | 3 mesh devices, no card, forever |
| Lowest paid | $3/mo (Basic) | $5/mo per public IPv6 |
Migration notes for current PageKite users
- If you use PageKite for HTTPS exposure: wayangi gives you an IPv6 address; run Caddy / nginx on your device to terminate HTTPS yourself. Or use Cloudflared if you specifically want a managed-HTTPS path.
- If you use PageKite for raw TCP forwarding: wayangi covers this directly — just bind your service to
::on the device, point a domain at the assigned IPv6. - If you use PageKite to share a single port temporarily: ngrok is a closer shape match than wayangi.