# Hanzo Tunnel — Hanzo AI

> Secure localhost tunnels for development and demos. Expose any local port to a public URL with end-to-end TLS in one command.

hanzo share

# Hanzo Tunnel

A public HTTPS URL for something running on your laptop. The port stays bound to localhost and the Hanzo fabric carries the traffic to it, so nothing is listening on whatever network the machine is sitting on.

[Start Tunneling](https://docs.hanzo.ai/docs/projects/hanzoai/tunnel)[View Source](https://github.com/hanzoai)

```
$ hanzo share 3000→ sharing 3000https://wispyfox7421.share.hanzo.ai → localhost:3000
```

## For the things that need a real URL

A webhook you have to receive. A build a client wants to click through. An OAuth callback that will not accept localhost.

### The port stays on localhost

Your service keeps listening on 127.0.0.1. The fabric reaches in and carries the traffic, so a café, a client&#x27;s office, or a conference floor sees nothing.

### A name you can keep

You get a random token by default. Pass --name and the subdomain is yours to reuse, so the callback URL you registered last week still works today.

### Your login is the account

No second signup, no config file to fill in. The first share provisions the account from the identity you already signed in with, then prints the URL.

### A shell is never open by hostname

hanzo link publishes the terminal you are in so the console can watch it, or drive it. That one is gated behind your org&#x27;s identity provider — knowing the URL is not enough, and if the gate cannot be applied the command refuses to publish.

### It ends when you do

The tunnel belongs to the command that started it. Close the terminal and the URL stops answering — a share cannot outlive the session that meant to make it.

### Four things to put behind it

proxy passes traffic through to a local port. web and static serve a directory as a site. drive hands over files. One flag picks which, and a port, a host:port, or a full URL all work as the target.

## One command, one URL

Install the CLI, sign in once, and name a port. It is the same sign-in that runs your agents and bills your usage, so there is nothing else to set up.

[Install the CLI](https://docs.hanzo.ai/docs/skills/hanzo-tunnel)[See Pricing](https://hanzo.ai/pricing)

## Get started with Tunnel

[Read the docs](https://docs.hanzo.ai/docs/projects/hanzoai/tunnel)[View on GitHub](https://github.com/hanzoai)

## Open source

License: Apache-2.0[hanzoai](https://github.com/hanzoai)

## Get Tunnel

Secure tunnels

[Deploy to Cloud](https://console.hanzo.ai/deploy)[Self-host](https://docs.hanzo.ai/docs/skills/hanzo-tunnel)
