localtunnel alternatives that stay free, open source or self-hosted
localtunnel still works. On 10 November 2026 the public loca.lt server gave us a tunnel without an account, but its newest npm release, 2.0.2, dates from 18 September 2021, it pins axios 0.21.4, for which npm audit reports high-severity advisories, and every browser visitor first gets a reminder page asking for the tunnel host's public IP. Each alternative below keeps part of what made localtunnel easy: no account, open-source code, or a server you can run yourself.
Pick by what you liked about localtunnel:
- No account, open source, own server possible → bore (MIT):
bore local 8000 --to bore.pub. TCP only, so visitors getbore.pub:<port>instead of an HTTPS hostname. - No account and an HTTPS URL → a Cloudflare Quick Tunnel: random trycloudflare.com hostname, up to 200 in-flight requests, meant for testing.
- Your own server and domain → frp (Apache-2.0, v0.72.0 on 4 November 2026) for HTTP, HTTPS, TCP and UDP.
- A hosted free tier with more features → zrok (5 GB a day, no card) or ngrok Free (1 GB a month, account required).
Free tier limits
What each tunnel gives you for $0, and whether you can run the server
License and latest release, the free public server, the page visitors see first, published free limits, protocols, and self-hosting. localtunnel is the first row.
| Tool | License · latest release | Free public server | Visitor warning page | Published free limits | Protocols | Run your own server |
|---|---|---|---|---|---|---|
| localtunnel | MIT · npm 2.0.2, 18 Sep 2021 | loca.lt, no account; random subdomain while lt runs (--subdomain is a request, not a guarantee) |
Yes: browser visitors type the host's public IP, once per visitor IP every 7 days; a bypass-tunnel-reminder header or non-browser User-Agent skips it |
None published | HTTP(S) | ✓ localtunnel-server (MIT), needs wildcard DNS; last code commit 26 Mar 2019 |
| bore | MIT · v0.6.0, 9 Jun 2025 | bore.pub, no account; random port | No: plain TCP forwarding | None published | TCP | ✓ bore server, optional --secret |
| Cloudflare Quick Tunnel | cloudflared client Apache-2.0 · 2026.10.7, 30 Oct 2026 |
trycloudflare.com, no account; new hostname each run | None documented; optional email PIN gate with --allowed-mail |
200 in-flight requests per tunnel (then 429); no Server-Sent Events; no uptime guarantee | HTTP(S) | ✗ Named tunnels need a Cloudflare account |
| Pinggy Free | Hosted service; the client is your system ssh |
free.pinggy.io, no account for a basic tunnel; random subdomain, new after each restart | None documented | 60-minute tunnel timeout; unlimited data transfer | HTTP(S), TCP, TLS, UDP (UDP needs the Pinggy CLI) | ✗ |
| zrok | Apache-2.0 · v2.0.9, 31 Oct 2026 | zrok.io free account, no card | Yes, until you add a credit card | 5 GB per day; 25 environments; 50 shares | Public shares: HTTP(S). Private shares: TCP, UDP | ✓ Apache 2.0, no limits |
| frp | Apache-2.0 · v0.72.0, 4 Nov 2026 | None; you run frps on a public IP |
No (your server) | Whatever your server allows | TCP, UDP, HTTP, HTTPS | ✓ the only way to use it |
| ngrok Free | Hosted service | Account required; 1 assigned dev domain, same across restarts | Yes, on HTML browser traffic | 1 GB data out, 20,000 HTTP requests, 5,000 TCP connections per month; no timeout | HTTP(S); TCP after card verification | ✗ |
No prices in this table: every row is a free tier or free software. "None published" means the project publishes no number. Release dates come from npm and GitHub releases.
Sources, checked 2026-11-10: localtunnel README · localtunnel on npm · localtunnel-server · bore · Cloudflare Quick Tunnels · cloudflared releases · Pinggy · zrok pricing · zrok releases · frp · ngrok free plan limits
The shortlist
6 localtunnel alternatives, from closest to furthest
Ordered by how much of localtunnel's model (no account, open source, your own server if you want one) each keeps.
About 400 lines of Rust, with one binary for client and server. bore local 8000 --to bore.pub uses the public server; bore server runs your own. It is TCP only, so visitors get bore.pub:<port> with no HTTPS hostname, and the last release (v0.6.0) is from June 2025.
cloudflared prints a random trycloudflare.com URL that works until you stop the process, and --allowed-mail puts an email one-time PIN in front of it. Cloudflare says Quick Tunnels are for testing, with a 200 in-flight request cap and no SSE; a stable hostname needs a named tunnel on a Cloudflare account.
Apache-2.0 reverse proxy with over 110,000 GitHub stars; v0.72.0 shipped on 4 November 2026. TCP, UDP, HTTP and HTTPS on your own domains, as long as you run, patch and pay for the frps server on a public IP.
NetFoundry's hosted free tier gives 5 GB a day without a card, and the Apache 2.0 code self-hosts with no limits. Free accounts without a card show an interstitial page, and the v2 CLI is called zrok2, so older guides are out of date.
Runs over the ssh client most systems already have, with unlimited data on the free plan and UDP through its CLI. Free tunnels end after 60 minutes and come back on a new random URL, and there is no server to self-host.
A free account gets one dev domain that stays the same across restarts, no timeout, and request inspection with replay. The free plan caps data out at 1 GB and HTTP requests at 20,000 a month, and browser visitors get an interstitial page.
Quickstart
Replacing npx localtunnel --port 8000: public server or your own
Commands from each tool's README or docs, with only the port changed to 8000. The right column shows what running the server yourself takes.
| Tool | On the free public server | On a server you run |
|---|---|---|
| localtunnel | npx localtunnel --port 8000 |
Server: bin/server --port 1234 from localtunnel-server. Client: lt --host http://sub.example.tld:1234 --port 8000 |
| bore | bore local 8000 --to bore.pub |
Server: bore server. Client: bore local 8000 --to <your-server> |
| Cloudflare Quick Tunnel | cloudflared tunnel --url http://localhost:8000 |
Not available; the edge is Cloudflare's |
| Pinggy | ssh -p 443 -R0:localhost:8000 free.pinggy.io |
Not available |
| zrok | zrok2 enable <account_token>, then zrok2 share public 8000 |
Self-hosting guide in the zrok docs; no single command |
| frp | No public server | Server: ./frps -c ./frps.toml with vhostHTTPPort set. Client: ./frpc -c ./frpc.toml with type = "http", localPort = 8000 and customDomains |
| ngrok | ngrok config add-authtoken <TOKEN>, then ngrok http 8000 |
Not available |
After switching, update any webhook or OAuth callback that still points at a loca.lt URL. On the free public servers of localtunnel, bore, Cloudflare Quick Tunnels and Pinggy the address can change on every run, so that update repeats.
Sources, checked 2026-11-10: localtunnel-server README · bore README · Cloudflare Quick Tunnels · Pinggy · zrok get started · frp README · ngrok docs
Method
How we checked
On 10 November 2026 we requested a tunnel from the loca.lt API, opened the returned URL with a browser User-Agent to read the reminder page, and ran npm audit against localtunnel 2.0.2 in an empty project. Licenses, release dates and issue counts come from the npm registry and the GitHub API; free limits come from Cloudflare's Quick Tunnels doc, Pinggy's pricing block, zrok's pricing page and ngrok's free plan limits doc, fetched the same day. Where a project publishes no limit, the table says so; we did not run speed or load tests.
Common questions
localtunnel alternatives: common questions
Does anyone still maintain localtunnel?
Barely. The newest npm release is 2.0.2, from 18 September 2021. The GitHub repo had 151 open issues on 10 November 2026; its latest commits (July and August 2025) only edited the README, and the last code change, from August 2022, was never released to npm. Version 2.0.2 pins axios 0.21.4, and npm audit reports high-severity advisories for that axios version. The public loca.lt server is still online. It issued us a tunnel on 10 November 2026, and the project site names TheBoroer as the person running it.
Why does a loca.lt link ask for a password?
That is localtunnel's reminder page. A browser visitor has to type the public IP address of the machine running the tunnel before the site loads; the page says this is there to prevent abuse, because localtunnel has been misused for malware, C2 servers and phishing. The tunnel host can look up that IP at loca.lt/mytunnelpassword. Each visitor sees the page once per public IP every 7 days. Requests with a bypass-tunnel-reminder header (any value) or a non-browser User-Agent skip it, so most webhooks go straight through.
Does localtunnel support TCP or UDP?
No. localtunnel proxies HTTP and HTTPS web traffic only. For raw TCP, bore forwards a port to bore.pub or to your own bore server. frp forwards TCP and UDP through a server you run, Pinggy carries UDP through its CLI, and zrok supports TCP and UDP on private shares.
Can I self-host localtunnel?
Yes. localtunnel-server is MIT-licensed. You need DNS records for your domain and a wildcard under it, and a server that accepts TCP connections on ports above 1000; then you point the client at it with lt --host. The server repository's last code commit is from 26 March 2019. bore (bore server) and frp (frps) are self-hosted options with releases in 2025 and 2026.
Is localtunnel good enough for a quick webhook test?
When you need a public HTTPS URL for a few minutes, already have Node.js, and don't want an account; npx localtunnel --port 8000 does that. It suits webhook tests, because non-browser requests skip the reminder page. In a live demo the IP prompt gets in the way, and for anything long-lived the axios 0.21.4 dependency and the random subdomain are reasons to move.