What is ResolveLabs Tunnel?
A secure, lightweight reverse proxy that exposes your localhost to the internet, with no session limits and URLs that persist across restarts.
1 min read
ResolveLabs Tunnel is a secure, lightweight reverse proxy that instantly exposes services running on your localhost to the public internet. Built for modern development teams, it removes the need to configure firewalls, routers, DNS or VPNs.
Unlike other solutions on the market, ResolveLabs focuses on developer resilience: zero arbitrary session limits and URLs that don't change on every restart, so you and your team can test webhooks and integrate APIs without interruptions.
Why use it
- Speed. Install, log in once and get a public HTTPS URL in under a minute. The account is free.
- Resilience. Sessions don't expire and tunnels reconnect automatically after network drops.
- Persistent URLs. Reserve a subdomain in your free account and webhook settings never go stale.
- Security. Traffic is intercepted at our Edge before it reaches your machine. Add Basic Auth or an IP allowlist with one flag.
- Visibility. Every request is listed in your terminal with its headers and body. Inspect it, and replay it against your app in one command.
How it works
When you run rl-tunnel, the CLI opens an outbound, encrypted connection from your machine to a ResolveLabs Edge server. The Edge gives you a public URL and relays every request it receives through that connection to the port you chose. Because the connection is outbound, nothing is opened on your network.
What it does
| Capability | Details |
|---|---|
| HTTP/HTTPS tunnels | Public HTTPS URL with a valid TLS certificate for any local web service. |
| Persistent subdomains | Reserve my-app.t.resolvelabs.com.br in your dashboard and use it with --subdomain. |
| TCP tunnels | Expose PostgreSQL, Redis, SSH or any TCP service with rl-tunnel tcp (free account). |
| Traffic inspector | Live log with an ID per request, rl-tunnel inspect for the full exchange and rl-tunnel replay to resend it. |
| Access control | Basic Auth and IP allowlist, enforced at the Edge. |
| Config file | Describe several tunnels in rl-tunnel.yml and start them with rl-tunnel start --all. |
| CI and servers | Create access tokens in the dashboard and use them with RL_TUNNEL_TOKEN. |
Where to go next
- Quickstart: from zero to the internet in 30 seconds.
- Accounts and tokens: sign up, log in from the CLI, tokens for CI.
- Use cases: webhooks, QA, mobile testing and more.
- Security: control exactly who can reach your tunnel.