Stoatworks Labs

Services

The bits you can't download

Some problems aren't solved by an app — they're solved by someone building the pipeline, running it through the event, and handing it over at the end. Two things we do that way. Both are built on tools we wrote and give away, so nothing here is a black box you can't inspect.

01

Managed event content

Nextcloud + our plugins, run for you

Every conference has the same problem: two hundred presenters, four hundred versions of the same deck, and a runner with a memory stick. We run the content pipeline instead — a private Nextcloud with our own apps on top, configured for your rooms and your schedule.

Built on

  1. 01

    Collect

    A folder and an upload-only drop link per session, generated in bulk from your running order — CSV, typed in the browser, or live-synced from a Google Sheet. Presenters get emailed their own link. One expiry date covers the whole batch.

  2. 02

    Normalise

    Keynote, PowerPoint, Google Slides and ODP all convert to PDF with the presenter notes preserved as a sidecar, so the notes still exist after the conversion that usually eats them.

  3. 03

    Distribute

    Per-theatre accounts scoped to their own folder plus the shared roots — holding slides, fonts, schedules — and nothing else. Room teams see their content and only their content.

  4. 04

    Go on site

    Once the drop links expire, the whole tree mirrors to a second Nextcloud you take to the venue, so the show runs off a local server that does not care about the site WiFi.

  5. 05

    Hand over

    Sessions stay in a tracked list you can edit, close early, or remove — and the same session data scaffolds a DaVinci Resolve project for post.

More to comeFuller detail — engagement models, hosting options, what we run versus what you run, and pricing — is being written and will land here.

02

DIT & ISO offload

Recordings off the switcher and into the edit, while the session runs

A multi-room event generates recordings faster than anyone can carry them. We build the ingest so nobody has to: ISO streams pulled off each switcher continuously, landing in the edit suite and the archive at the same time, ready to cut before the session has finished.

Built on

  1. 01

    Pull, do not copy

    The ATEM exposes its drive over FTP and will serve a file that is still being written. We pull only the bytes past the last known offset, using FTP’s own resume mechanism — the same thing curl -C does. A whole-file re-copy every ten minutes cannot keep up and falls permanently behind inside twenty minutes.

  2. 02

    Nothing on the show laptops

    The ingest is one container on the central server, reaching each room over the event’s private mesh. No agent to install on a machine that is running a session, no software on the critical path.

  3. 03

    Two destinations at once

    Each pull dual-writes to the edit suite’s NAS and to Nextcloud, so editors work on local storage while the archive copy builds itself.

  4. 04

    The other recorders too

    vMix machines are pulled the same way over SMB, so program records and ISOs arrive on the same clock and in the same tree.

  5. 05

    Sized before it is built

    Four to six active ISOs plus program is 50–80 GB for a three-hour session. We do that arithmetic against your actual uplink first, and design to it — rather than finding out on day one.

More to comeThe full workflow — chain of custody, proxy generation, naming conventions, and what we hand over at wrap — is being written and will land here.

Talk to us

Got an event with this shape?

Tell us the room count, the recording setup and the uplink you're stuck with, and we'll tell you honestly whether this helps — or whether you just need one of the free tools and an afternoon.

Start a conversation