Get started
- Subscribe. Sign in to the dashboard with your email (no password: we send you a link) and pick a plan under Plan & billing. See pricing.
- Add your SSH key: run
ssh -t link@proxy.tunnl.ggand open the link it prints (below). This is what signs you in when you connect. - Reserve a subdomain under Subdomains, for example
myapp. - Connect:
ssh -t -R myapp:80:localhost:3000 pro@proxy.tunnl.gg
Your app on port 3000 is now at https://myapp.tunnl.gg, and stays there for as long as the SSH session is open: no 2-hour idle timeout and no 24-hour limit. Your tunnels may transfer 10 GB a day together, twice the free limit.
Add your SSH key
On the computer you connect from, run:
ssh -t link@proxy.tunnl.gg
It prints a one-time link. Open it in a browser where you're signed in to the dashboard (or sign in there), check the key's fingerprint and click Add key. Connecting with the key proves it's yours, so there's nothing to sign. The link works for 10 minutes; don't share it, since it adds the key to whichever account opens it.
If you don't have a key yet, create one with ssh-keygen -t ed25519.
Or paste it
You can also paste your public key into the dashboard under SSH keys. To print it:
cat ~/.ssh/id_ed25519.pub
Then prove the key is yours: the dashboard shows a short command that signs a one-time code with your private key, for example:
printf CODE | ssh-keygen -Y sign -n tunnl.gg -f ~/.ssh/id_ed25519
On Windows, in PowerShell:
"CODE" | ssh-keygen -Y sign -n tunnl.gg -f $HOME\.ssh\id_ed25519
Paste the signature it prints back into the dashboard. Your private key never leaves your machine. Verifying stops anyone else from adding your public key to their account.
Choose which subdomain opens
There are two ways to pick the subdomain a tunnel opens on:
- Name it in the command, before the port:
-R myapp:80:localhost:3000. Any of your keys can open any of your account's subdomains this way. - Link a key to a subdomain in the dashboard. Connecting with that key and no name,
ssh -t -R 80:localhost:3000 pro@proxy.tunnl.gg, then opens its subdomain. A key that isn't linked gets its stable URL instead.
A subdomain has one tunnel at a time. If you connect to a subdomain that's already open, for example from another laptop, the newest connection takes over.
Subdomain names use letters, digits and hyphens, with at least 3 characters. Names the service uses, names in the word-word-hex format of random and stable URLs, and names that contain a well-known brand or a phishing term can't be reserved.
Passwords, IP allowlists and CORS
Pro tunnels accept every option of the ssh command. Add them after the host:
ssh -t -R myapp:80:localhost:3000 pro@proxy.tunnl.gg auth=demo:s3cret allow=203.0.113.7
| Option | What it does |
|---|---|
host=localhost:3000 | Sends this Host header to your app, for dev servers that block unknown hosts |
auth=user:password | Visitors must sign in with this user name and password |
allow=203.0.113.7,198.51.100.0/24 | Only visitors from these IPs or networks get through |
cors=* or cors=https://app.example.com | Lets pages on other sites call your tunnel from a browser |
output=json | Prints the URL and each request as JSON lines, for scripts and AI agents |
To avoid typing them every time, save them on the subdomain in the dashboard (Subdomains, then the subdomain's settings). Saved settings apply whenever the subdomain opens, and saving changes them on an open tunnel straight away. An option in the command overrides the saved one for that connection. Passwords are stored only as a hash.
Only host= and output=json are available on the free plan.
Request inspector and traffic
The request inspector and replay are also available to verified free accounts. See free inspector setup. Pro adds traffic stats for reserved subdomains.
- Request inspector: the dashboard's Inspector shows each request to your open tunnels as it arrives: the request your app was sent, with headers and the start of the body, and what it answered. Replay sends one again, handy for webhooks. Each tunnel keeps its latest 50 requests, in memory only, until it closes.
- Traffic: requests, errors, data in and out, and response times for each of your subdomains, by the hour, for the last 90 days.
Teams
A Team account is Pro for several people, billed per seat from 3 seats:
- The owner invites members by email. An invite works for 7 days.
- Members share the team's 10 reserved subdomains and plan, each with their own SSH keys. The team can have 10 tunnels open and transfer 10 GB a day per seat.
- The owner reserves and releases subdomains and changes their settings; members open them.
- Removing a member removes their keys and closes their open tunnels. Everyone else's stay up.
- Someone with a free account who joins a team brings their keys with them. A member of another team, or an owner with a paid plan of their own, can't join.
If your subscription ends
When a subscription is canceled, Pro stays active until the end of the period you paid for. After that, or if a payment fails, open Pro tunnels close. Once the account returns to the free plan, verified keys can reconnect as pro@ with free limits and the inspector; free stable@ and random URLs also keep working. Your keys and reserved subdomains stay on your account, so subscribing again picks up where you left off.
Manage your plan, card and invoices from Plan & billing in the dashboard.