ZeroVTT Gateway

Docs

What the gateway does, when the app uses it, and what to check when a session won't connect.

What the gateway does

The gateway relays session state between participants. It receives messages from each player and forwards them to the others, keeping scene changes, token positions and dice results in sync.

It does not store your campaign. Session state lives in memory for the duration of the session and is discarded when the last participant leaves.

When it is used

ZeroVTT opens a direct connection between browsers first. A table that connects directly never sends anything through the gateway.

The app switches to the gateway when the direct connection fails: strict NAT, a mobile network, a corporate firewall, or a browser that blocks peer-to-peer traffic. The switch is automatic and doesn't interrupt the session.

You can force a region in Settings, under Connection. The app remembers the choice per campaign.

Connection details

The gateway listens on TCP port 443 and speaks HTTPS with WebSocket upgrades. Nothing needs to be configured on the client side, and no extra port has to be opened.

Region Location Status
eu-centralFrankfurt, DEOperational
us-eastAshburn, USOperational
ap-southeastSingapore, SGOperational
sa-eastSão Paulo, BROperational

Hostnames for each region are assigned by the app and change with the routing table, so there is nothing stable to bookmark.

If a session won't connect

Changelog

2.14.32026-11-18

Reduced memory held per session and shortened the replay buffer window to 90 seconds.

2.14.22026-10-27

Faster region selection on mobile networks. Fixed a reconnect loop after a laptop woke from sleep.

2.14.12026-10-09

Added sa-east. Health endpoint now reports the deployed version.

2.14.02026-09-15

Moved the relay to a new connection handler. Sessions survive a gateway restart for up to 30 seconds.