Shared Tunnels

Shared tunnels send every incoming request to every teammate's machine at the same time. When Stripe, GitHub, Slack, or Twilio fires a webhook, nobody has to ask "hey, can you forward me that payload?" — everyone already got it.

The problem shared tunnels solve

Your team is integrating Stripe. Every test payment sends a webhook to one URL. But three people are working on the payment flow — and with a normal tunnel, only one of them receives it. Everyone else is stuck copy-pasting JSON out of Slack.

How it works

Create a shared tunnel. Everyone connects with the same token. Stripe sends the webhook once, and all three developers receive it on their local machines.

# Alice
localport http 4000 --token SHARED_TOKEN

# Bob (same token, different machine)
localport http 4000 --token SHARED_TOKEN

# Charlie (same token, yet another machine)
localport http 4000 --token SHARED_TOKEN

When Stripe sends a POST to https://abc123.tunnel.localport.dev/webhook, Alice, Bob, and Charlie all receive the exact same request body at the same time.

The active client

Webhook providers expect a response. One client is designated as "active" — their HTTP response is what gets sent back to the webhook provider. The first person to connect becomes active automatically.

You can change which client is active from the Localport dashboard at any time. This is useful when Bob needs to handle the Stripe response while Alice and Charlie just observe the payload.

Setting it up

1. In the dashboard, go to your team and click Shared Tunnels

2. Create a new shared tunnel

3. Share the token with your team (Slack, 1Password, however you share secrets)

4. Everyone runs localport http PORT --token SHARED_TOKEN

Use cases

• Webhook development — Stripe, GitHub, Slack, Twilio, Paddle — everyone sees the payload. Webhook guide
• QA and dev collaboration — QA engineer and developer see the same live traffic simultaneously
• Staging fanout — Route production-like webhook traffic to multiple staging environments
• Debugging — Reproduce webhook issues by having the whole team observe the same requests

Requirements

• Available on all plans
• Each connected client counts toward your team's client limit

Next steps

• Webhook Development — Step-by-step setup for Stripe, GitHub, Slack, and Twilio
• HTTP Tunnels — Standard HTTP tunneling for solo use