NGROK ALTERNATIVE
A permanent public IPv6 instead of an ephemeral ngrok URL.
ngrok is brilliant for spinning up a quick HTTPS endpoint during development. wayangi is the opposite shape: a permanent, dedicated public IPv6 address tied to your device, with raw TCP/UDP, no random hostname rotation, no per-hour bandwidth caps.
wayangi vs ngrok at a glance
| What you get | ngrok | wayangi |
|---|---|---|
| Address type | Random *.ngrok-free.app (free) or reserved subdomain (paid) | Dedicated public IPv6 — point any AAAA record |
| Protocol | HTTP / HTTPS / TCP (paid) | Any IP protocol — TCP, UDP, ICMP, QUIC, custom |
| Persistence | Tunnel dies with the process unless paid plan | Address belongs to the device until you cancel |
| Bandwidth limit | 1 GB/mo on free, metered on paid | Unmetered (within fair use) |
| Pricing model | Per-user/mo, separate per-tunnel limits | Per-IPv6-address/mo, all tiers visible |
| Inbound-only safety | N/A (proxy) | Hub enforces inbound-only egress on customer IPs |
| Free tier | 1 tunnel, ephemeral URL, ngrok branding | 3 mesh devices, no card |
| Cheapest paid | $8/mo (Personal) | $5/mo per public IPv6 |
When ngrok is the better choice
- Sharing a localhost demo with a colleague for the next 20 minutes.
- Receiving a webhook from a third-party service while debugging locally.
- You want HTTPS termination + a CDN-shaped front door without setting up Caddy yourself.
- You're fine with the URL changing between sessions.
When wayangi is the better choice
- You're running a permanent home server, IoT board, game server, Mastodon node, or Matrix homeserver and want a stable address.
- You need raw TCP / UDP / arbitrary protocol — not just HTTP.
- You want to point your own domain at it (any DNS provider).
- You want predictable per-month per-IP pricing, not per-tunnel.