Webhook testing
Receive Stripe, GitHub or Slack webhooks on your machine and debug them live. A stable URL means you register the endpoint once.
ssh -t -R 80:localhost:3000 [email protected]
tunnelize.it turns a local app into a public HTTPS link over plain SSH. Keep the same address across reconnects, or ask visitors for a password. Nothing to install, no sign-up.
// how it works
SSH can forward a port in reverse. tunnelize.it sits on the other end: it gives that connection a public HTTPS address and passes each request down the tunnel to your machine.
happy-tiger-a1b2c3d4.tunnelize.it
HTTPS to the public URL
TLS certificate, phishing warning and rate limits happen here
SSH tunnel you opened outbound · localhost:3000
No router ports, no firewall rules, no background daemon. Close the terminal and the tunnel closes. Use the Stable tab to get the same URL back next time.
// built for
Webhooks, demos, phones and OAuth callbacks — one SSH command, with an optional stable address or visitor password.
Receive Stripe, GitHub or Slack webhooks on your machine and debug them live. A stable URL means you register the endpoint once.
ssh -t -R 80:localhost:3000 [email protected]
Send a client or teammate a live link to what you’re building, hot reload included. Add a password when the link shouldn’t be open to everyone.
ssh -t -R 80:localhost:5173 [email protected]
Open your dev build on a real device over mobile data. tunnelize.it can print a QR code in the terminal to scan.
ssh -t -R 80:localhost:8080 proxy.tunnelize.it
Give OAuth providers and CI jobs a real HTTPS redirect URL that hits your local environment — and keep it the same so you configure it only once.
ssh -t -R 80:localhost:4000 [email protected]
// compare
Every tool here is good at something. tunnelize.it is for when you want a URL right now, with nothing to install — plus free stable URLs and visitor passwords.
| Feature | tunnelize.it | ngrok | Cloudflare quick tunnel |
|---|---|---|---|
| Nothing to install | Yes — plain SSH | Needs its agent | Needs cloudflared |
| No account needed | Yes | No | Yes |
| Same URL every time | Free, no account | With an account | Account + own domain |
| Visitor password | Built in | Paid / config | No |
| Price | Free | Free tier + paid | Free |
// faq
Short answers for the first time you run the command.
ssh -t -R 80:localhost:3000 proxy.tunnelize.it gives the web server on port 3000 of your machine a public HTTPS URL, such as https://happy-tiger-a1b2c3d4.tunnelize.it, for as long as the SSH session is open.[email protected] and your SSH key gives you the same URL on every connection. Any key works; there is nothing to register. Without a key, static@ is refused. Only someone with your private key can claim that URL.[email protected]. Visitors must pass HTTP basic auth; the username is always tunnelizer and a short pronounceable password is printed in your terminal banner for that connection.static@ get a new random URL each time.curl and other non-browser clients go straight to your app; browser-like clients can skip it by sending the tunnelize-skip-browser-warning header..tunnelize.it to the allowed hosts in your dev server’s config.