Share localhost on a public HTTPS address.
tund http 3000 gives your local port an HTTPS URL that stays the same every run, and records each request so you can inspect it and replay it.
$ tund http 3000
Two commands
The client connects out over HTTPS, so it works behind NAT, corporate firewalls and hotel Wi-Fi on macOS, Linux and Windows.
- 1
Install the client
curl -fsSL https://tund.io/install.sh | shOne binary, no admin rights, no network drivers.
- 2
Share a local port
tund http 3000The first run opens your browser to sign in or create an account. After that,
tund http 3000gives you the same URL every time.
Built for showing work and testing webhooks
A stable HTTPS address
Certificates are handled for you. Your account keeps its address between runs, so webhook settings and shared links keep working. Pin more names, or pass --random for a throwaway one.
https://brave-otter-4821.on.tund.io
Every request, recorded
Headers, bodies and timings appear in the inspector as they happen. Replay a request against your local server with one click, or copy it as cURL.
- POST/webhooks/stripe200
- POST/api/checkout422
- GET/api/orders?page=2500
Private when it needs to be
Ask visitors for a password, or make them sign in with Google, Entra ID, Keycloak or any OpenID Connect provider before a request reaches your machine. Public links also get abuse protection: browsers see a one-time warning before an unprotected tunnel.
tund http 3000 --password 'correct horse'
tund http 3000 --oidc company --oidc-allow @company.com
Your own domains
Point a domain, or a whole wildcard, at TUNd and serve tunnels from it. Certificates are issued automatically once DNS is in place.
tund http 3000 --domain api.example.com
Built for AI agents
tund mcp lets Claude Code, Cursor, Codex and other coding agents start a tunnel, send you the URL and read the captured requests while they debug. You decide which ports they may share and whether every tunnel needs a password.
claude mcp add tund -- tund mcp
Start the dev server and share it with me via tund.
Self-host it
The same server, dashboard and inspector run on a machine you control: one Docker Compose file with Postgres and a wildcard DNS record. Clients downloaded from your server connect to it automatically.
# on your server, with *.tunnels.example.com pointing at it
docker compose up -d
# a client installed from somewhere else
tund config set-server https://dashboard.tunnels.example.com
Get a URL for localhost:3000 now.