The Virtual Post House

A virtual post house is a software-based finishing facility that replaces the centralized brick-and-mortar post-production house with a distributed, cloud-native equivalent. It centralizes the operational layer of finishing — quality control, deliverables management, DCP validation, review and approval, and technical compliance — in software, so teams can finish work from anywhere without giving up the rigor of a traditional facility.

Where a traditional post house provides physical infrastructure — storage, projection rooms, color suites, QC bays — alongside the operational expertise to run a delivery pipeline, a virtual post house provides the software equivalent. The creative work still happens in industry-standard tools like DaVinci Resolve, Avid Media Composer, and Pro Tools. The virtual post house handles everything around them: spec management, automated QC, validation, approvals, packaging, and delivery tracking.

Bradford Lab is the virtual post house. In practice that means something simpler than the category name suggests: it is your library in the cloud, with the post services running on it.

It starts with your media. Every asset on a project, every version of it, in one place you can reach from anywhere — the suite, a laptop on location, a client's browser. Nothing to sync, no folder of files ending in FINAL, no wondering which cut the director actually saw.

What makes it a post house rather than storage is that everything that happens to your media stays on it. The QC report. The caption pass. The loudness measurement. The note somebody left at 01:04:22. The approval. The link you sent the distributor and whether they opened it. The job the render fleet ran at 3am. Not tracked in a spreadsheet beside your media — attached to the exact version it happened to.

Which is why you can ask what state a deliverable is in and get an answer, instead of asking three people and opening two spreadsheets. Here is what rides along with every version:

Post has always been half local and half distributed. Grading, conform, and mixing happen on a specific machine, with specific hardware and terabytes of media hanging off it. Review, approval, and delivery involve people nowhere near that machine. For thirty years the bridge between the two was an assistant moving files and sending emails.

Bradford Post Assistant is that bridge in software. It runs on your workstation, right next to DaVinci Resolve, and drives the application directly — project, timeline, color, and render operations, where the session actually lives. What makes it more than a plugin is that your library comes with it. From inside the app on your workstation you pick a project, an asset, and a specific version out of the cloud, and run work against it — including QC on the render fleet. No export, no upload, no hand-off. The same media, the same version, the same record.

So the library is not somewhere you put things when you are finished with them. It is where the work happens from, whether you are sitting in the suite or looking at a browser on the other side of the country. And the fleet that does the heavy processing can run on your own hardware if the title calls for it.

An agent cannot do much with a folder of files. Give it a versioned record and it can do real work: read what a file actually is, compare it against the spec it is meant to satisfy, run the check, write the result back where you will find it, and move the state forward. Agent-first post-production is not a question of which model is answering you. It is a question of whether there is anything solid to act on — and that is what your library is.

The work itself runs as durable workflows that survive restarts, dropped networks, and jobs measured in hours: probing a file, measuring loudness against the target you assigned, validating a Digital Cinema Package against its composition, building playback renditions, packaging a deliverable, running a QC profile. What runs and when is yours to govern — platform defaults out of the box, and profiles your organization's admins can override for the org, a client, or a single project.

Agents do not approve deliveries, sign off on color, or accept a mix on a client's behalf. Those have explicit human checkpoints. The division is simple: the workflows do the mechanical work, the assistant helps you understand and direct it, and the decisions that carry a name stay with the people whose names they are.

A library on its own is storage. What makes this a post house is that the platform knows what your media is — DCP structure, EBU R128 loudness, CEA-608 and CEA-708 captions, ISDCF naming, and the technical details that actually break deliveries. These are the services running on your library:

Full detail on capabilities and on the formats and standards the platform reads, validates, and delivers.

Bradford Lab is built by Bradford Operations, founded by Samuel Gursky. The team previously operated Irving Harvey, a physical post-production facility in New York that finished documentary and narrative work for twelve years (2012–2024). The product is not a guess about what a facility needs. It is the operational layer of that work, rebuilt as software, by the people the delivery deadlines belonged to.