What it does
The part of WebLinked that makes sense on a server. Point it at a dashboard, a scoreboard or a clock and it becomes an NDI source on the network, with no GPU, no display and no desktop session involved.
libndi is deliberately not baked into the image — it is not ours to redistribute — so the container resolves whatever NDI runtime you supply at run time.
- Renders real pages headless at 1080p50 with zero dropped ticks
- Runs WebLinked's full test suite inside the image
- No display server, no graphics card, no desktop session
- NDI runtime supplied at run time rather than bundled
Where it stands
In development. The image has been built and run, and WebLinked's 89-test suite passes inside it — the first time that suite has run on Linux at all. The NDI output has never been received from this image, because libndi is not in it. Everything below the NDI line is verified; the NDI line itself is not. It is designed to run inside a Tailscale tailnet or another network you trust end to end: the control API has no authentication until you set a token, and its script endpoint runs arbitrary JavaScript in the rendered page, so an unauthenticated port here is remote code execution on your network. Do not expose it to the public internet.