Self-hosting

Each image is built by GitHub Actions from the tool's own repo on every push and published to GitHub's container registry under ghcr.io/stoatworks-labs. A static tool is nginx serving the built page on port 80, so running one is a single line:

docker run -d --name blend-calc --restart unless-stopped -p 8521:80 ghcr.io/stoatworks-labs/blend-calc:latest

Then it's at http://localhost:8521/. Every tool has its own default port, all listed below, so you can run the lot side by side without any of them arguing over 8080. Each repo also has a docker-compose.yml that does the same thing with docker compose up -d.

To update one, pull the image again and recreate the container:

docker pull ghcr.io/stoatworks-labs/blend-calc:latest
docker rm -f blend-calc
docker run -d --name blend-calc --restart unless-stopped -p 8521:80 ghcr.io/stoatworks-labs/blend-calc:latest

Or, with the compose file, docker compose pull && docker compose up -d.

RFutils is the odd one out

RFutils is a service rather than a static page, and it finds receivers with mDNS. Docker's bridge network doesn't pass multicast on, and it doesn't complain about it either: discovery just comes back empty, which looks a lot like a network with no receivers on it. So its container uses the host's network, listens on 8420 and keeps its settings in a folder you mount:

docker run -d --name rfutils --restart unless-stopped --network host -v "$PWD/config:/app/config" ghcr.io/stoatworks-labs/rfutils:latest

The templates live in stoatworks-unraid, which has been in the Community Applications feed since August 2026. Open theApps tab, search for the tool's image name (simple-rta, arraycad and so on, as in the table) and press Install. The template fills in the image and the port, and for RFutils host networking and its config folder, so there's nothing to type unless the port clashes with something you already run. Once it's up, the container's WebUI link opens it.

If the feed hasn't picked a template up yet, add it by hand: Docker,Add Container, then paste the template's raw URL. The table links to every template.

Burrow lists the same tools on its Self-hosted tab, if you'd rather find them there.

Every image here builds in CI, and every one in the table pulled anonymously from the registry when I checked on 29 October 2026. What I haven't done yet is install each one from its template on a real Unraid server, so treat the templates as untried until somebody has. If one misbehaves, theissue tracker on stoatworks-unraidis the place to say so.

The same repo has templates for a handful of services that aren't web tools, ATEM Overseer and srt-router among them. Their own pages and READMEs cover those.