Skip to content

Tunnels for anything you run.

A persistent public URL for your web app, database or game server. HTTP, TCP and TLS.

One command, any protocol.

Pick the protocol that fits. The command stays the same.

HTTP & HTTPS

Web apps and APIs, with HTTPS built in.

  • Trusted certificates
  • Webhooks and OAuth
  • Client demos
https://myapp.eu.localport.dev
Learn more

TCP

Databases, SSH and game servers.

  • Any TCP service
  • Reserved port
  • Stable address
tcp://myapp.eu.localport.dev:47266
Learn more

TLS

Encrypted all the way to your service.

  • Passthrough
  • Your certificates
  • Never decrypted
tls://myapp.eu.localport.dev:47266
Learn more

Get your tunnel running in three steps.

  1. Create a tunnel in the dashboard.

    Give it a name and pick a region.

  2. Install the agent.

  3. Run the command the dashboard hands you.

    It already carries your tunnel's token.

Every plan starts with a trial. Cancel any time.

localport
$
  • macOS
  • Linux
  • Windows
  • Docker
  • Raspberry Pi

Turn on Fanout. Give your whole team one webhook URL.

Switch any HTTP tunnel to Fanout and every connected teammate receives each webhook live.

  1. Open the tunnel's settings and set Delivery to Fanout.
  2. Register its address with your webhook provider, once.
  3. Each teammate runs the connect command on their own port.
Same URL
The address stays when you switch
Signatures checked first
Webhooks are verified before delivery
One primary
One device answers, the rest listen
How Fanout works
POST /webhooks/payment
https://mywebhook.eu.localport.dev Disconnect all
alice-mac Disconnect
bob-pc Set Primary Disconnect
chad-linux Set Primary Disconnect
localport
Alice's terminal Webhook received
localport
Bob's terminal Webhook received
localport
Chad's terminal Webhook received

Private by default.

What you send is never logged.

Never logged

We forward your traffic and never store it.

  • No payload logging
  • No training on data
  • TLS passthrough
Security overview

Open-source agent

Read the code that runs on your machine.

  • Public on GitHub
  • Build from source
  • Signed releases
View on GitHub

Your region

Each tunnel stays where you put it.

  • Region per tunnel
  • Multi-region
  • EU account data
See regions

Control who gets in.

Checks that run on every connection. No code changes.

URLs that survive every restart.

Your address stays the same across restarts and network changes.

Common questions.

The docs go deeper, or talk to us.

Does my URL change when I restart?

No. Every tunnel keeps its address across restarts. You can also pick your own subdomain or use your own domain.

Does it work behind CGNAT, NAT or a firewall?

Yes. The agent makes one outbound connection on port 443, so it works anywhere your browser does, with no port forwarding and no router changes.

Which protocols can I tunnel?

HTTP and HTTPS for web apps and APIs, TCP for databases, SSH and game servers, and TLS passthrough for services that hold their own certificates.

What is Fanout?

Fanout delivers every request to every connected device, so each developer on a team gets the same webhook at the same time. Switch it on in any HTTP tunnel's settings and the address stays the same. It carries HTTP only.

Do you log my traffic?

No. We never log or store what passes through a tunnel, and we never train on it. With a TLS tunnel the traffic stays encrypted all the way to your service.

Can I use my own domain?

Yes. Point a domain at a tunnel with one CNAME record and HTTPS is set up for you, wildcards included.

Is the agent open source?

Yes. The agent that runs on your machine is open source under Apache 2.0 on GitHub, and every release is signed.

Put your first tunnel online.

Create a tunnel and run one command.