# How it connects

You scan once. After that, Pane finds the fastest way from your phone to your computer by itself, wherever you are. You never open a port on your router or sign in to anything.

<RelayDiagram />

## Three ways in

1. **Same Wi-Fi.** Your phone connects straight to the computer. In the Pane app this works even when the internet is down. A browser needs the internet to look up your computer's address.
2. **A direct path, on different networks.** The Pane app and desktop Pane try this. Both devices keep a small outgoing connection to Pane's servers. The servers tell each one the other's public address, and both send to each other at the same moment. That opens a path through both home routers. It's called hole punching, and it's the same trick Tailscale uses.
3. **The nearest relay.** Some networks block direct paths, like strict office or hotel Wi-Fi. A browser on another network always uses a relay. Your computer picks whichever of Pane's four relays answers it fastest: **us** (Iowa), **eu** (Belgium), **asia** (Singapore) or **west** (Oregon). A relay is a server that passes your encrypted connection along without opening it.

Pane keeps timing the direct path and the relay and uses whichever is faster. You don't pick.

## How fast is it?

We measured it on November 15, 2026:

| Path | Round trip |
|---|---|
| Direct path, a Windows PC in San Francisco to a Mac in Seattle | **37 ms** |
| A computer in Seattle, out to the **west** relay and back to itself | **29 ms** |

Both are the round trip for one request on an open connection. The second is the relay's detour alone, so a phone near that computer would wait about that long through the relay.

## Each computer gets its own address

When you turn on phone access, your computer gets its own address, `https://<id>.runpane.net`, and its own certificate (the file that proves a website is who it says it is). The `<id>` comes from your computer's key. The private key is created on your computer and never leaves it.

The encryption ends at your computer, so the relay only ever handles sealed traffic. It reads only the outside of the envelope: which computer the connection is for.

<a id="who-sees-what"></a>

Who can see what along the way: [Security, in plain words](/docs/remote-security#who-can-see-what).

## When the connection drops

Walk out of Wi-Fi range or switch to cellular, and the app reconnects by itself, usually within seconds. A sleeping computer can't answer. See [When something goes wrong](/docs/phone#when-something-goes-wrong).

## Want your own relay?

You don't need one. But if you'd rather your traffic pass through a machine you control, you can [run your own relay](/docs/self-hosted-relay) in about five minutes. Everything works the same.

## Related

- [Use Pane on your phone](/docs/phone)
- [Your computers](/docs/your-computers)
- [Tailscale and Remote VMs](/docs/remote-daemon), if you'd rather use your tailnet
