{"id":113362,"date":"2026-09-03T07:23:57","date_gmt":"2026-09-03T14:23:57","guid":{"rendered":"https:\/\/www.backblaze.com\/blog\/?p=113362"},"modified":"2026-09-03T07:24:02","modified_gmt":"2026-09-03T14:24:02","slug":"four-platforms-one-timeline-bringing-tams-workflow-to-life-on-backblaze-b2","status":"publish","type":"post","link":"https:\/\/www.backblaze.com\/blog\/four-platforms-one-timeline-bringing-tams-workflow-to-life-on-backblaze-b2\/","title":{"rendered":"Four Platforms, One Timeline: Bringing TAMS Workflow to Life on Backblaze B2"},"content":{"rendered":"\n
\"An<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Broadcast production has spent decades organizing media around files, servers, and the physical limits of the facility. That model is familiar, and it works until a live event creates hours of footage across multiple cameras, editors are distributed, the archive is growing by petabytes, and every copy of every clip becomes another operational and financial problem.<\/p>\n\n\n\n

Time Addressable Media Store, or TAMS, offers a different model: Organize media by time, store it in object storage, and let interoperable tools access the same content through an open API. Pair that with affordable, high-performance storage, and the result is a practical path toward cloud-native production without forcing media teams into a single vendor\u2019s ecosystem.<\/p>\n\n\n\n

That is where a stack built on Backblaze B2, together with TAMS ecosystem partners LiveWyer, CuttingRoom, and Drastic Technologies, gets interesting.<\/p>\n\n\n\n

What is TAMS?<\/h2>\n\n\n\n

When a live event is producing hours of footage across multiple cameras, editors should not have to wait for files to close before they can start working. TAMS, or Time Addressable Media Store, addresses that problem by organizing media around the timeline rather than individual files.<\/p>\n\n\n\n

With TAMS, media is stored as timestamped segments that applications can access by time. A news editor can pull a quote from a press conference while it is still underway. A sports producer can create a highlight from a live game feed. A content team can reuse the same moment for social clips, a longer edit, distribution, and archive without creating a separate proprietary copy for every stage.<\/p>\n\n\n\n

TAMS gives ingest systems, browser-based editors, desktop NLEs, MAMs, and archive platforms a common way to work with the same media. The store can run on one cloud, ingest can come from another provider, and editors can use the tools they already know.<\/p>\n\n\n\n

The specification grew out of BBC Research & Development<\/a>\u2019s work on cloud-native media production and was published in 2023. Its purpose was practical: Give different companies a shared interface for building interoperable media workflows instead of recreating isolated storage silos in the cloud.<\/p>\n\n\n\n

TAMS is not a replacement for an NLE, MAM, ingest system, or archive. It is the layer that helps those systems work together. In this article, we are focusing on three Backblaze ecosystem partners that demonstrate that approach: LiveWyer, CuttingRoom, and Drastic Technologies.<\/p>\n\n\n\n

The solution stack<\/h2>\n\n\n\n

LiveWyer<\/a> provides TAMOSS, a Kubernetes-native implementation of the TAMS API. TAMOSS is the store management and API layer. It handles the TAMS structure while orchestrating the underlying media segments stored in Backblaze B2.<\/p>\n\n\n\n

CuttingRoom<\/a> brings an editorial-grade video editing experience into the browser. In a TAMS workflow, editors can begin working with media while a live event is still being captured. They can find a moment on the timeline, create a clip, and assemble a story without waiting for an entire file to close or moving the media into a separate editing silo. The CuttingRoom solution allows real-time collaboration, import and exports from and to market leading MAMs and with the optional ShortCut AI assistant editing, editors can do more in less time.<\/p>\n\n\n\n

Drastic Technologies<\/a>\u2019 NetX platform provides the TAMS-compliant readers and writers that handle both ends of the media flow: ingesting and writing media into TAMS, then reading it back for playback and use in professional applications such as Adobe Premiere and Avid. NetX is a key part of making TAMS flows usable across live ingest, playback, and established desktop production workflows including Adobe Premiere.<\/p>\n\n\n\n

With Backblaze B2 providing the S3-compatible storage foundation beneath the workflow.<\/p>\n\n\n\n

TAMOSS supplies the TAMS interface. CuttingRoom provides the browser-based editorial experience. Drastic NetX handles the critical ingest, writing, reading, and playback paths. B2 stores the media segments at a price that makes large-scale access practical.<\/p>\n\n\n\n

These companies are part of a growing ecosystem of roughly 14 technology providers with publicly identifiable TAMS implementations, products, readers, writers, or integrations. That broader ecosystem includes AWS, Konstrukt, LOGIC media solutions, LucidLink, Mimir, Reuters Imagen, Matrox Video, Mavis, Norsk, Techex, and Zixi, alongside LiveWyer, CuttingRoom, and Drastic Technologies.<\/p>\n\n\n\n

This is the broader idea behind an interoperable standard. No single company has to provide every part of the workflow, and customers do not have to replace every system they already own.<\/p>\n\n\n\n

Where TAMS fits<\/h2>\n\n\n\n

The use cases are not limited to national broadcasters.<\/p>\n\n\n\n

A news organization could ingest a live press conference, let an editor find a quote while the event is still happening, and publish a short clip before the full recording is finished.<\/p>\n\n\n\n

A sports production team could create proxy media for immediate clipping while retaining higher-resolution source material for finishing. This is particularly useful because some high-resolution MOV and MXF workflows are difficult to segment and read while they are still growing.<\/p>\n\n\n\n

A regional sports league or smaller event producer could avoid building a large on-premises storage environment and give remote editors access to the same media from wherever they are working.<\/p>\n\n\n\n

A corporate video team could record a town hall, create short internal clips, publish social content, and retain the full event in the archive using the same underlying media.<\/p>\n\n\n\n

The same approach could support houses of worship, education, government, live entertainment, and creator workflows. The common requirement is quick access to a growing body of media without multiplying copies and handoffs.<\/p>\n\n\n\n

What if the editor reviewing a live feed did not need to ask where the file was? What if the answer were simply a time range in a shared store?<\/p>\n\n\n\n

Why Backblaze B2 matters<\/h2>\n\n\n\n

Live video is a storage problem before it is almost anything else. A multi-camera sports event, a continuous news operation, or a large livestream can generate terabytes of content quickly.<\/p>\n\n\n\n

Backblaze B2<\/a> starts at $6.95 per terabyte per month, with free egress up to three times average monthly storage and no egress fees through many compute and CDN partners. That combination makes it easier to keep large live datasets available for editing, review, distribution, and archive.<\/p>\n\n\n\n

A TAMS workflow backed by B2 can look like this:<\/p>\n\n\n\n