Through this site
Checking…
- Status
- -
- Rooms
- -
- Connections
- -
- Endpoint
- -
Fetched by the website's server, so it works even when the control server blocks cross-origin requests.
Status
Control server status.
The control server introduces remote peers and relays encrypted frames. It never holds messages, keys, or room secrets.
Direct from your browser
Checking…
- Status
- -
- Rooms
- -
- Connections
- -
- Endpoint
- -
Fetched by your browser straight from the control server's /health route.
What it does
A signpost, not a mailbox.
Peer discovery
Two clients on different networks need a place to swap connection details. The control server holds encrypted endpoint cards and never sees their contents.
Relay fallback
When hole punching fails, the server relays already-encrypted datagrams over a WebSocket. It cannot decrypt the traffic passing through.
Room coordination
Named rooms use the server to find members. Only opaque room IDs and HMAC-derived capabilities are stored; room secrets stay on your device.
No message storage
Chat, files, and keys travel peer to peer. The control server is signalling and relay only, with no access to any of it.