Stoatworks Labs

Discipline

Networking & Infrastructure

The plumbing under a multi-room event: transport that crosses networks you don't own, and machines that boot the same way every time.

This is the least glamorous category on the site and the one that decides whether any of the rest of it works. A twelve-room event is a network problem wearing an AV badge: media has to cross it, control has to cross it, and neither is allowed to notice the other is there.

Most of that work doesn't come out as a download. It comes out as a topology you can copy, a board that fills a gap in the signal chain, or a job somebody does on site. Only the properly reusable software is listed as a project here, and the links further down go to the rest.

7 projects · 5 with builds to download · 4 to try in a browser

Booting, imaging and remote access

Getting an operating system onto a box that didn't ship with one, and getting back to it afterwards from somewhere else.

System Graft — The drivers the installer forgot, grafted into an initrd

System Graft

Field testing

Networking & Infrastructure / Application/ Python/ v0.2.3

Injects out-of-tree kernel modules into a SquashFS initrd and writes it to bootable removable media. You bring the image and the modules. Handy when an installer has never heard of your NIC or RAID card.

  • Linux
  • initrd
  • UEFI
  • Bootable USB

The BirdDog PLAY

A decoder taken further than its firmware goes: the patcher, the factory flasher, and the tailnet panel that lets a patched unit sign itself in.

bdts — Tailscale, signed in from the decoder's own web UI

bdts

In development

AV Systems · Networking & Infrastructure / Firmware/ Go

A firmware patch for the BirdDog PLAY that adds a Tailscale panel to the System page of the decoder's own web UI, so a unit joins a tailnet from a browser instead of over SSH. It's the other half of the PLAY Patcher, which installs Tailscale but bakes in no auth key on purpose, because a key in a file the browser hands you is a key in cleartext. That left every patched unit installed but not signed in. Settings go through Tailscale's set command rather than up, so changing one preference doesn't reset all the others behind your back, and the panel won't offer exit-node and subnet-route switches this kernel can't honour: there's no TUN device, so Tailscale runs in userspace networking. Reads are open; writes need a live birdUI session, because an open Tailscale API would let anyone on the LAN join the box to a tailnet of their own.

  • BirdDog
  • Tailscale
  • Firmware
  • Remote access
  • NDI

Transport and comms

Moving signal and talkback between rooms, buildings and networks that weren't designed for it.

SRT Router — A broadcast-style crosspoint for SRT

SRT Router

Field testing

AV Systems · Networking & Infrastructure / Application/ Rust/ v0.2.5

A crosspoint for SRT that works like a broadcast router: any number of inputs and outputs, each output switchable live to one source, all added and removed on the fly from a web UI. It's a straight relay with no transcoding, and NDI transport is included.

  • SRT
  • NDI
  • Crosspoint
  • Low latency

Running the fleet

The plumbing under the rest of it: how the web tools are packaged and served, how the tray apps launch them, and where the numbers about them come from.

gh-fleet-analytics — GitHub numbers, before GitHub forgets them

gh-fleet-analytics

Released

Networking & Infrastructure / Library & Protocol/ Python/ v0.1.2

Snapshots every repo an account owns into per-repo JSON committed to git, and draws a password-protected dashboard from it, because GitHub keeps traffic for 14 days and only reports stars and downloads as a running total.

  • GitHub API
  • Analytics
  • Cloudflare Workers
  • Self-hosted

Also infrastructure

Everything else in the category.

PLAY Patcher kit — The PLAY Patcher's parts, as one download

PLAY Patcher kit

Field testing

AV Systems · Networking & Infrastructure / Firmware/ Shell/ v0.3.0

Everything the PLAY Patcher puts into a firmware package, released as one zip: the installer scripts, the module binaries, a manifest saying where each file goes and which option needs it, and the licence notices. The page serves those files from its own origin, so nothing outside a browser could get at them until now. Tailscale and MediaMTX aren't in it, on purpose: whoever builds a package fetches them from their own publishers, the same as the page does.

  • BirdDog
  • NDI
  • Firmware
  • Tailscale
  • KVM
Stoatworks Burrow — One list for every plugin, tool and module

Stoatworks Burrow

Beta

Video FX · AV Systems · Audio · Networking & Infrastructure / Application/ Rust / TypeScript/ v0.5.0

An optional desktop app for all the Stoatworks software: plugins, tools, applications and Companion modules. It shows what you've got installed and what has an update, and installs each one in whichever formats you use, whether that's FFGL for Resolume, OpenFX for Resolve, After Effects, or VST3 and Audio Units for a DAW. It keeps itself up to date too. You don't need an account, and it doesn't send anything anywhere.

  • Resolume
  • DaVinci Resolve
  • After Effects
  • FFGL
  • OpenFX
  • Plugin manager
  • Tauri
  • macOS
  • Windows
  • Companion

Two problems that keep coming back

The first is that a feed has to reach several places at once, over a network you don't control, and the destinations change during the event. Doing that with a stack of point-to-point encoders means reconfiguring endpoints live, which is exactly when you least want to. A crosspoint (any number of inputs, any number of outputs, each output switchable to any source at runtime, relayed rather than transcoded so switching costs nothing) is the mental model everyone already has from a video router, applied to stream transport.

The second is that a machine has to boot the same way every time, on hardware whose vendor image has never heard of your NIC or your RAID card. Patching an initrd by hand with unsquashfs and mksquashfs quietly produces a broken image, because a non-root round trip loses ownership and drops setuid bits and nothing tells you until it fails to boot in the truck.

Why so little of this is downloadable

Because infrastructure is mostly specific. The valuable output of a large multi-room build is the topology, the addressing plan and the decisions about what shares a VLAN with what, and those are documents, published anonymised as a reference rather than dressed up as an application nobody could run.

The other half is hardware. A PoE DMX node, or a pair of radio-mic antennas sent down one Cat cable, is the right answer to a physical-layer problem, and pretending otherwise by writing software around it helps nobody. Those live on the hardware page.

The whole catalogue

This is one discipline of several

The full index carries every project at once, searchable and filterable by discipline, type and how finished it is, including the disciplines that don't have a page of their own yet.