Multiplayer

Host a session, share a ticket

One person hosts a session and gets a ticket - a short string (or a peek://invite/… deep link) that carries everything needed to dial their machine. Anyone who pastes it joins, mirrors the host's canvas, and starts editing alongside them in real time. There's no account to make and nothing to install on their end.

Peer-to-peer, end to end

Sessions are built on iroh. Peek runs no central serverthat routes your edits - pages, nodes, cursors, and presence all flow directly between the people in the session. That's what makes it safe to look at real data together: there's no middle tier for Peek to read it from.

Each peer keeps its own pan, zoom, and active page, so you can wander off to inspect a different node without yanking everyone else's view along with you. Cursors are filtered per page, so you only see pointers from people looking at the same canvas.

One database, shared results

Queries always run against the host's connection. When a guest runs a query, the request goes to the host, executes there, and the rows stream back - so everyone sees the same results without the guest ever holding your credentials.

The host's schema is shared along with the canvas, so guests get full autocomplete and SQL intelligence even though they have no database connection of their own. The connection stays opaque to them - they only ever see its name.

End it cleanly

When the host ends a session, the shared document is torn down and the host's dialing address is rotated, so old tickets stop working- a previously shared link can't be used to reconnect later. Guests fall back to a local snapshot of where things were when the session closed.