Experimental · for LAN parties

A relay you bring to the party.

gawk-relay runs on one machine on the venue's network, so everyone there streams and watches over the LAN instead of the venue's internet line. You don't need it to broadcast or watch: the browser and the native apps work without it.

When it helps

Two ways to run it

Standalone

Start it with no options. Its page opens at http://127.0.0.1:4480 on that machine and shows the join link and a QR code; guests on the network use those. Only people on the LAN can watch.

Paired with a gawk server

An operator of that deployment's admin portal creates the relay there and gets a one-time pairing string to paste into the relay's page. Then people outside can watch party streams (each crosses the venue's uplink once, only while someone outside watches, within a budget the operator sets), a home stream crosses the downlink once however many guests watch it, outsiders get one party-wall link, and guests who open the usual site at the venue are moved to the local relay by themselves.

Before the party

Download

gawk-relay

Experimental

Latest release

Windows x86-64
Or as a container
$ docker run --network host -v gawk-relay:/data ghcr.io/tuhis/gawk-relay

Host networking, so guests reach it on the machine's own LAN address. Keys, certificates and the pairing live in the volume.

The Windows and Linux binaries aren't signed, so the checksum is the only integrity check you get; each release also ships a SHA256SUMS file. The design, and what is still unmeasured, is in docs/76.