If you would like your session included on this list then please let us know in the TAMS Slack.

On this page

• Awards
• Talks
• Demonstrations

Awards

IBC Innovation Awards 2026

The Reuters and TVU Networks’ project, “Capacity that follows the live news story”, has been named a finalist in the IBC Innovation Awards 2026 in the Content Distribution category.

https://www.tvunetworks.com/story/reuters-and-tvu-networks-introduce-scalable-live-workflows-for-on-demand-news/

Talks

Friday 11th

15:00: Stop Copying Media: TAMS for Open, AI-Ready Media Workflows (Content Everywhere Stage 2)

Why does every workflow still need its own copy of the media? In this session, Oracle Cloud Infrastructure and Norsk explore how TAMS enables a more open model: store media once, make it accessible across workflows, and give broadcasters more choice in the tools and partners they use. The result is less duplication, faster access, and more flexibility across clipping, replay, publishing, archive, analytics, and emerging AI-enabled media operations. Rather than locking media into closed silos, TAMS points to a practical cloud foundation for simpler operations, greater customer choice, and faster innovation. Discover why time-addressable media is emerging as a smarter foundation for the next generation of media workflows.

Saturday 12th

13:30: How synchronisation & alignment of media works in DMF and TAMS, and how they work together (EBU - 10.D21)

Ask-me-anything session on sync and timing in TAMS, JT-DMF and across the supply chain, with BBC R&D’s Robert Wadge

15:00: How Yahoo Studios Built Cloud-Native Media Workflows with TAMS on AWS (AWS - 5.C90)

Liam Mulvey and Dan Brantigan from Yahoo Studios demonstrate the end to end workflow they have built on TAMS to take content from their studios through to their website.

15:30: Capacity that follows the story (TVU Networks - 5.B86)

Reuters News Agency joins TVU Networks, InSync Technology Ltd and Kinetiq, alongside a representative from the TAMS community, for a live conversation about a different approach to live news infrastructure: Capacity follows the story.

We’ll go behind a new approach Reuters and TVU Networks are developing for live news distribution — exploring how workflows, processing and services can be dynamically assembled around the needs of each event, with capacity able to scale as demand changes.

https://hubs.li/Q04wd8Dd0

16:00: Smart Stories - The New Knowledge Architecture for Content Production (Future Tech Stage)

Every newsroom runs on integration. Decades of it teaching our systems to talk to each other. None of it taught them what the story means. As those systems become intelligent, that context, currently lost at every handoff, becomes foundational. Join us for this exclusive, world-premiere of our IBC Accelerators’ new 2026 Incubator “Smart Stories”, as this multi-award-winning, truly global team reveals the fast-track R&D that built SOM, the Story Object Model: an open standard that makes the story a first-class object systems subscribe to. Its state, its sources, its assets. The integration layer for the agentic era.

IBC website

16:00: TAMOSS at the EBU Open Source Meetup (EBU - 10.D21)

The EBU Open Source Meetup will again be held during IBC at the EBU’s stand (10.D21) and is a great place to learn about some of the latest updates from your favourite open source media projects, as well as learn about new initiatives.

The format is a series of short (5m) pitches on open source projects for media and broadcasting, spanning audio and video, software and hardware.

This year’s programme includes TAMOSS - Kubernetes-native implementation of the BBC’s Time-addressable Media Store API; a common foundation for building fast-turnaround media workflows.

https://tech.ebu.ch/events/2026/open-source-meetup-ebu-ibc-2026

Sunday 13th

15:15: Trust, Provenance and Authenticity (Conference Room 2)

This panel session will have two presentations followed by a panel discussion with a range of experts working in the field. The first is a presentation from an international project on the first standardised framework for implementing C2PA for media provenance across newsrooms of varying sizes and operational contexts. The second is from Reuters News and Media Ltd on the four open standards that collectively address the issues around trusted news content: the EBU Dynamic Media Facility, the Media eXchange Layer (MXL), the Time-Addressable Media Store (TAMS) API, and the Coalition for Content Provenance and Authenticity (C2PA) specification.

https://show.ibc.org/ibc2026/trust-provenance-and-authenticity-1

11:30: TAMS and how it fits with DMF (EBU - 10.D21)

Ask-me-anything session on how TAMS fits with the Dynamic Media Facility initiative, with TAMS TSC chair Sam Mesterton-Gibbons

13:00: Live TAMOSS build

In this 30-minute slot we will install the TAMOSS operator on a real Kubernetes cluster and bring up a store. We will then connect the store to CuttingRoom Reporter and CuttingRoom Editor, using Backblaze as the S3 storage behind it. The deployment is configured against external PostgreSQL, S3 storage and an OIDC provider, making the underlying deployment Kubernetes-stateless.

The session is aimed at anyone who wants to see a complete install before attempting one on their own infrastructure.

https://livewyer.io/blog/livewyer-brings-open-source-tams-to-ibc-2026-with-tamoss/

Monday 14th

12:00: Open Media Architectures (AWS - 5.C90)

The media industry is shifting from monolithic, proprietary systems toward open, modular architectures that decouple content storage, processing, and distribution into interoperable layers. This approach enables organisations to compose best-of-breed tools, accelerate innovation, and integrate AI natively across production workflows — from ingest through to delivery.

This is being driven by open-source initiatives including TAMS (Time Addressable Media Store) which reimagines cloud storage as a real-time media platform, and MXL (Media eXchange Layer) providing standardised transport between media services. Together they illustrate how open architectures reduce vendor lock-in, lower integration costs, and empower media organisations to evolve at the pace of technology rather than procurement cycles.

With John Biltcliffe (AWS), Chris Swan (AWS) and Sam Mesterton-Gibbons (BBC R&D)

Demonstrations

2wcom Systems GmbH (8.D81) - New

We will show our IP-4c Audio over IP codec with TAMS integration

https://www.2wcom.com/

3adesign / Phrame - New

3adesign is showcasing Phrame, a cloud-native media platform with native support for TAMS. Phrame delivers compliance recording, monitoring and browser-based media workflows as ready-to-deploy solutions, with every recording, review and playback pointing directly at time-addressable media in place: no duplicate files, no proprietary silos. Broadcasters get continuous compliance recording and monitoring running alongside live production, with instant browser access to any point on the timeline. On the live side, Phrame’s services exchange frames over a shared-memory frame bus built on MXL and VDI, alongside NDI and SMPTE 2110 for standards I/O. So, whether media is moving between production services or landing in the TAMS store, Phrame relies on open, vendor-neutral interconnects rather than proprietary ones. Come and see how a genuinely TAMS-first platform simplifies compliance and monitoring without creating another media silo.

https://phrame.cloud/

AWS (5.C90)

This year, rather than a standalone TAMS demo pod, TAMS serves as a foundational layer underpinning several demonstrations across the AWS booth — reflecting its growing role as core infrastructure for modern media workflows. In Re-inventing Linear Contribution & Distribution on AWS, TAMS powers both ingest and fast-turnaround workflows feeding directly into linear channel playout, demonstrating how cloud-native media storage can streamline traditional broadcast chains. The Adopting MXL for Live Cloud Production demo showcases TAMS playback and recording as part of a wider, gallery-based live production environment built on the MXL standard, illustrating how TAMS and MXL work together as complementary technologies for cloud-based production. And in Smart Stories: The Agentic Production Ecosystem, developed through the IBC Accelerator programme, TAMS acts as the media store alongside the SOM bus as the story context layer, enabling next-generation news workflows that include AI-driven understanding of TAMS content, AI-assisted story writing, and automated publishing to multiple endpoints.

Beyond the demos, TAMS also features in the AWS booth theatre programme, with a session from Yahoo on Saturday and an Open Media Architectures session on Monday lunchtime exploring the broader ecosystem around TAMS. Visitors looking to get hands-on will also find Logic Media and Merapar on the AWS booth — both systems integrators with live TAMS demonstrations and real-world experience building with TAMS, ready to help customers looking to adopt it in their own environments.

https://aws.amazon.com/events/ibc-2026/

BCNEXXT

Vipe from BCNEXXT now supports TAMS.

TAMS aligns directly with BCNEXXT’s principals of openness, agility, scalability and performance and by switching to utilizing native TAMS on object storage, BCNEXXT expects to rapidly develop new functionality such as a comprehensive ‘lines’ recording and subsequent content management functionality for Vipe, becoming a major enabler for BNCEXXT’s ‘record once and use many times’ philosophy.

https://www.bcnexxt.com/

Broadcast Bionics (8.F40) - New

MOR> Multi Object Recorder is built for radio and podcast workflows, synchronising free-running cameras to PTP-locked audio and capturing every source as a reusable media object. Rather than creating only a finished programme, it writes synchronised video, audio and metadata directly into a TAMS store for immediate search, AI inference, editing and repurposing.

Creator Node connects a RØDECaster directly into professional AoIP infrastructure, carrying multichannel audio and GPIO between the desktop production environment and the wider broadcast network. At the same time, it enables multitrack recording straight from the RØDECaster into a TAMS store, preserving individual microphones, programme audio and other sources for immediate reuse, search, AI processing and repurposing.

https://www.bionics.co.uk

CuttingRoom (1.D20) - Updated

CuttingRoom works natively with TAMS, with no duplication of files. Add as many TAMS stores you need, and access them all directly from the award winning CuttingRoom Cloud Editor. TAMS sources can grow both in the source player and on your timeline, so you can edit the way you prefer. In addition you can record to TAMS natively from the field using the CuttingRoom Reporter iPhone app. CuttingRoom has often been used to verify new TAMS implementations, as we were among the first to support it. CuttingRoom is known for the many out-of-the-box integrations with MAM/PAMs (like Avid, Iconik, Mimir and many more), cloud storages (like AWS S3, StoreJ, Backblaze and many more) and has a pluggable AI assistant, ShortCut, that customers can train to their specific needs. All our tools are up to date with TAMS 8.2

https://www.cuttingroom.com/

GV (9.A01) - New

“This is not another TAMS connector demonstration. Grass Valley will showcase a fully integrated content supply chain that brings TAMS media registration directly into the production workflow, from ingest and edit through to rendering and distribution.

The Elastic Recorder workload (scalable distibuted ingest) ingests and registers media into TAMS, Framelight X provides the editorial experience with Search, Discovery and remote browser/Premiere Edit, before FLARE rendering handles final rendition and output.

Framelight X abstracts the underlying storage environment, allowing editors to work seamlessly with traditional local or remote storage alongside time-addressable media in TAMS all as a combined content and editing workflow. This enables organisations to adopt TAMS without disrupting established creative processes or creating another workflow for users to manage.”

https://www.grassvalley.com/products/ampp/framelight-x/

Hiscale (1.F17) - New

New at IBC: Hiscale FLICS Live Ingest can now record live streams directly into TAMS.

FLICS captures IP-based sources including SRT, NDI, HLS, MPEG-TS and RTMP, and makes the incoming content available through TAMS while it’s still being recorded. This means other applications and workflows can start accessing and working with the content straight away.

A simple way to connect live ingest with open, TAMS-based media workflows.

https://www.hiscale.com

LiveU (7.C24) - New

LiveU is demonstrating its development of TAMS as part of the LiveU EcoSystem, enabling continued interoperability and industry openess, in conjunction with the SOM IBC Accelerator for both Live and File based workflows.

https://www.liveu.tv/

LiveWyer - New

Live TAMOSS recordings and interviews to a publicly available TAMS Store

On each of the three days we will be walking the halls recording interviews with exhibitors and visitors. Each interview is captured on CuttingRoom Reporter and uploaded directly into a public TAMOSS store that we run for the show. There is no memory card to offload and no file to copy between systems. As soon as an interview is in the store, anyone with the link can browse it and play it back, or pull it into an edit or QC tool over the TAMS API.

Come and find us if you would like to be interviewed. If you would rather watch, ask us for the link to the store and you can follow the interviews as they are added over the three days.

https://livewyer.io/blog/livewyer-brings-open-source-tams-to-ibc-2026-with-tamoss/

LOGIC media solutions GmbH (5.C90) - Updated

LOGIC will be present at IBC 2026 as a co-exhibitor at the AWS booth 5.C90, showcasing an end-to-end reference architecture for a modern highlight platform built on TAMS.

Acting as the integrator, LOGIC demonstrates how the full solution package comes together across ingest, event processing, AI-assisted analysis, orchestration, editorial approval, rendering, and delivery preparation.

The showcase highlights how audio, video, and metadata streams can be brought into a scalable cloud-based workflow that supports faster and more efficient highlight production without losing operational control.

Particular emphasis is placed on the modular architecture approach, where clearly separated solution packages are combined into one integrated platform while remaining flexible for future extension. The concept illustrates how existing media and production environments can be enhanced step by step with automation, governance, and scalable processing capabilities.

https://logic.tv

Matrox Video (7.B15) - Updated

Matrox ORIGIN is a development framework for rapidly building media applications using a REST-based API. It’s an open and extensible system that allows developers to build their own media processing functions with a laser focus on their specific concerns, as control state is managed by the framework. It includes a large number of media processing functions, including clip players, mixers, SRT, and much more.

For IBC 2026, we made some improvements to our TAMS reader and writer, now supporting “Play while Record” workflows; this allows for quick-turnaround capture and replay within ORIGIN.

There is demonstration of the Matrox TAMS playback and record features on the Matrox (7.B15) and AWS (5.C90) booths.

https://video.matrox.com/en/product/broadcast-developer/origin-framework/

Mavis (10.A41) - Updated

“Mavis Camera is a powerful professional camera app for iPhone, designed to connect a wide range of acquisition sources directly into TAMS-based workflows.

In this demo, we extend our existing camera-to-cloud technology with native TAMS support across multiple video sources. Content can be captured using the iPhone’s built-in cameras, received over NDI, or brought in from professional HDMI and SDI cameras using devices such as the Atomos Ninja Phone and Accsoon SeeMo range.

The result demonstrates how Mavis can bridge traditional production hardware with cloud-native workflows, bringing everything from an iPhone camera to a professional SDI source directly into TAMS, all through a device you already have in your pocket.”

https://mavis.cloud/

Mimir (7.A53) - Updated

Here is how Mimir is transforming cloud broadcast workflows with TAMS (Time Addressable Media Store): Instead of making file copies or duplicating proxies, Mimir sits as the intelligence and discovery layer on top of TAMS.

Here is what we’re showcasing: ⚡ Edit-by-Reference: Search, view, and process live MPEG-TS segments directly in object storage. without duplicate files. 🤝 Cross-Tenant Federation: Discover and share media across organizational tenants with unified credentials and rights auditing. 🛠️ Tooling Integration: Works seamlessly alongside craft editors like Adobe Premiere and CuttingRoom.

Validated in the AWS reference architecture for fast-turnaround workflows, Mimir brings intelligence, rights, and story-centric search to the TAMS ecosystem.

https://onemimir.com/news/mimir-at-ibc-2026

Norsk (5.A53) - New

The concept behind TAMS is simple: record media once, index it against a timeline, and make it accessible to any application instantly without making duplicate copies. Rather than locking media into closed silos, TAMS points to a practical cloud foundation for simpler operations, greater customer choice, and faster innovation. And the use cases are almost endless: clipping for reuse across platforms, making assets available for VoD in multiple services, capturing video quality issues for forensic review … the list goes on. Norsk and Oracle Cloud Infrastructure will be demonstrating real-world TAMS applications in Norsk Studio — just drag a TAMS box onto a workflow and access your recordings via a straightforward player UI with seamless scrubbing. Come see the demo at the Norsk stand, 5.A53, or Oracle and Norsk’s joint presentation at 15:00 on the Content Everywhere Stage 2 (5.G72) in Hall 5.

https://norsk.video/norsk-tams/

Reuters Imagen (5.D44) - Updated

Live-to-Social Highlight Engine: On demand recording of live video streams into TAMS, with AI continuously analyzing the feed in real time to detect standout moments — big plays, crowd reactions, key talking points — and automatically clips them into ready-to-post highlights for social media. On stand demo, come a play e-sports, which are being streamed to the cloud using TVU to go through the above flow.

https://imagen.io

Techex (2.B45) - Updated

Techex’s tx darwin TAMS integration provides the ingest and routing layer into a TAMS store that downstream editing and archive tools can reach the instant they exist.

With Techex tx darwin’s video and audio conformance leading synchronization of multiple feeds on output to a TAMS store, tx darwin lets broadcasters adopt vendor-agnostic, cloud-native production without re-plumbing their existing contribution workflows. This now includes Timecode-aware media segmentation and delivery from MXL workflows.

https://techex.tv/tams

TVU (5.B86) - Updated

TVU Networks is demonstrating TAMS in production at Reuters scale as part of Scalable Live — a cloud-native live news workflow where TVU MediaMesh writes live feeds directly into Reuters’ TAMS store for immediate AI indexing, enrichment, and journalist access. This is an end-to-end Reuters production workflow running live at IBC, where capacity follows the story rather than a fixed channel count. See it in action at Hall 5, stand B.86, or join the Scalable Live session on September 12 at 3:30 PM.

https://www.tvunetworks.com/story/reuters-and-tvu-networks-introduce-scalable-live-workflows-for-on-demand-news/

Zixi (5.A76) - New

“ZEN Master, powered by Broadcaster v19, writes live streams directly into a TAMS (Time Addressable Media Store) as time-stamped segments that can be reached at any point on the timeline. Any Zixi input, including SRT, RIST, Zixi protocol, and HLS, becomes content addressed by time rather than by file. Teams can work with the stream while it is still being written, take only the interval they need, and build clips or edits by reference with no rendering and no file transfers. Broadcaster handles protocol reliability, timing, and packaging ahead of the store, so TAMS receives a clean, continuously timestamped record of the event.

The store becomes a landing point for the feeds Zixi already carries. A venue contributing over SRT or Zixi protocol lands in TAMS within seconds, so a producer can pull a replay or highlight by timestamp while the event is on air. A RIST hand-off from a partner network becomes a time-indexed record for compliance, rights review, or late-joining editors. An HLS source can be normalized by Broadcaster and stored once, then re-cut for social, syndication, or on-demand without a second transcode.The live demo shows this end to end: pick a TAMS environment and flow, watch segments appear as Broadcaster writes them, or query the store by time range, then play the results in the browser or download them stitched into a single clip.”

https://www.zixi.com

The new TAMS identity is built from the specification itself. The mark is four media segments across two timeline tracks, staggered so the negative space reads as a T. There are no curves, no gradients and no illustration — just simple shapes on a grid, which means it stays legible stamped at 16 pixels, printed in a single ink, or stitched into fabric.

The palette is a broadcast-gallery navy with one amber accent, rationed so it always signals emphasis. Typography is Geist for headings and body, IBM Plex Mono for anything machine-adjacent: endpoints, IDs, timeranges. Both typefaces are under the SIL Open Font License.

Everything is open. The logo kit ships as SVG with outlined type, no fonts required. Alongside, there are transparent PNGs, in horizontal, stacked and mark-only lockups, duotone and single-colour. There’s a brand guidelines document covering usage, and a drop-in GitHub Pages theme that the TAMS website uses.

No request form, no licence fee. If you need a format that isn’t in the kit, open an issue and it’ll be added for everyone.

Guidelines and assets: TAMS Brand Guidelines.

Fragmented MP4 and Initialisation Segment Support

One of the most requested features lands in 8.2: native support for media formats that use initialisation segments, including fragmented MP4 (fMP4), CMAF, and MPEG-DASH.

TAMS has historically modelled media as independently-decodable objects — a natural fit for formats like MXF or TS-wrapped essence. But many modern delivery and production workflows use container formats where a decoder must first read an initialisation segment before it can process media segments. Until now, these formats didn’t fit neatly into the TAMS data model.

The new approach (detailed in ADR0045) models init segments as object-level properties. Each Media Object can reference an init Object, which is uploaded, stored, and has URLs generated exactly like any other object in TAMS. This means:

• Multiple init segments per Flow are supported — essential for multi-period manifests and C2PA-signed content
• Edit-by-reference works unchanged — init segments follow the media objects they’re associated with
• Existing implementations are unaffected — the init_segments boolean on the Flow signals when this feature is in use
• Existing object patterns are reused — no new storage mechanisms required

AppNote 0024 provides detailed implementation guidance, including notes on reference counting for garbage collection, the relationship between init and media objects, and terminology alignment with CMAF.

Flow Profiles

Creating Flows with the correct technical metadata can be repetitive and error-prone, particularly in environments with strict house formats. Version 8.2 introduces the Profile resource — a reusable template of technical parameters that can be referenced when creating a Flow.

Profiles serve two purposes:

1. Simplified creation — rather than specifying codec, resolution, bitrate, and other parameters individually, reference a Profile and the metadata is populated automatically
2. Discovery and matching — Flow listings can be filtered by Profile, making it straightforward to find all content in a given format, or to match compatible Flows in edit-by-reference workflows

This is documented in AppNote 0020.

Better Content Discovery and Ordering

Building a content browser on TAMS requires two things: finding the right content, and presenting it in a predictable order. Previously, both of these had to be handled client-side — clients fetched all Sources, manually discarded those that were collected by another Source to find the “top-level” content, and then applied their own sorting logic. This broke pagination, scaled poorly, and pushed complexity into every UI implementation.

Version 8.2 solves both problems at the API level.

Filtering by collected_by

The new collected_by_ids query parameter on Source and Flow listings (ADR0049, PR #183) moves content-tree filtering into the API:

• ?source_collected_by_ids= (empty value) — returns only uncollected Sources, i.e. the top of the content tree
• ?source_collected_by_ids=<uuid> — returns Sources collected by that specific Source
• ?source_collected_by_ids=<uuid1>,<uuid2> — returns Sources collected by any of the listed Sources

Because the filtering happens server-side, pagination now works correctly — requesting 25 results returns 25 matching items, not 25 items of which an unknown number will be discarded.

Defined ordering of resource listings

Alongside filtering, this release brings explicit and client-controllable sorting to resource listings across two changes:

• Segments (PR #223) — The default ordering of the segments listing (by timerange) has always been implied by the specification text. This is now explicit, and the existing reverse_order parameter is formally documented against it.
• Sources, Flows, and other resources (PR #224) — Defines the default sorting of all other resource listings and provides a means for clients to specify the sort order where appropriate.

Together, these changes mean a content browser can request “the first 25 uncollected Sources, sorted by creation date” in a single paginated call — no client-side filtering, no ambiguous ordering, and predictable page boundaries.

Rethinking Collection Roles: Editorial Purpose as a First-Class Concept

The role field in multi-essence collections has been a source of inconsistency across implementations. Some used it for editorial purpose (“programme”, “commentary”), others for media type (“video”, “audio”), and many for an ad-hoc combination of both. This made it difficult to build interoperable clients that could reliably identify what a piece of content is and what it’s for.

Version 8.2 addresses this with a two-part change:

Role becomes optional, collections become ordered

ADR0056 concludes that most of what role was being used for are properties of the Source or Flow itself, not its position in a collection. The field is now optional — a human-readable label only — and collections are ordered lists where position conveys priority and default selection.

Editorial purpose moves to a tag on the Source/Flow

ADR0053 introduces the editorial_purpose tag, stored directly on the Source or Flow. This means editorial purpose is captured regardless of whether the content is part of a collection, and can be queried independently.

AppNote 0025 defines recommended values, drawing on SMPTE ST 377-41 for audio terminology:

Architectures for Media Transformation

As TAMS grows beyond single-format ingest, the question of “how do I transcode content?” needs a clear answer. AppNote 0022 provides architectural guidance — not normative specification — describing potential patterns for media transformation:

Tag-based transcode triggering

Set an experimental transcode_trigger tag on a Flow, and a watching service can automatically trigger a transformation when new content arrives. The AppNote describes error handling, status signalling, and how this integrates with webhooks.

Transform on Request (Just-in-Time)

A more experimental pattern where Virtual Objects represent content that doesn’t physically exist until it’s requested. When a client requests a get_url for a Virtual Object, the transformation is triggered on-demand. This enables just-in-time transcoding without pre-populating every possible format.

Flow Status Elevated to Core Metadata

The flow_status tag has been widely adopted by implementations to signal the lifecycle state of a Flow — whether it is actively being written to, complete, or in some other state. Until now it has been an experimental tag, meaning its behaviour was not guaranteed by the specification.

Version 8.2 promotes this to a first-class status attribute on the Flow resource itself. This reflects its importance in real-world deployments where clients and automation need a reliable, standardised way to determine whether a Flow is still receiving content or is ready for downstream processing. Moving it into the core specification means implementations can depend on consistent behaviour across TAMS services.

Fine-Grained Authorisation on Storage Backends

As TAMS deployments grow more complex — multiple teams, multiple storage tiers, regulatory boundaries — the ability to control access at the storage backend level becomes essential.

ADR0055 adds read-only tags to Storage Backends, extending the authorisation proxy patterns described in AppNote 0016. Tags are set at deploy time and can be used to:

• Allocate costs by team or department
• Designate read-only archive storage
• Enforce geographic or regulatory data residency
• Restrict access to sensitive content storage

The approach follows existing patterns — if you’ve already implemented fine-grained auth on Sources and Flows using AppNote 0016, the same mechanisms now work for Storage Backends.

Pre-signed URL Control

Different deployment architectures need different approaches to authenticating object storage access. Some environments use pre-signed URLs for direct client-to-storage uploads; others use a reverse proxy that attaches credentials.

Version 8.2 (ADR0054) makes this explicit:

• Clients can request pre-signed or non-pre-signed put_urls via a presigned parameter
• Responses signal whether returned URLs are pre-signed
• Additional documentation clarifies the authentication methods available for both put_urls and get_urls

This change is fully backwards-compatible — existing implementations that don’t specify a preference continue to work as before.

Other Improvements

• include_object_timerange on webhooks — Aligns webhook behaviour with the HTTP API and fixes an inconsistency where object_timerange was sometimes omitted even when requested

Bug Fixes

• Missing return codes have been added to the webhooks specification.
• Tag endpoints that should permit lists now correctly do so.
• The generation field is now described more clearly.
• Example code in the README has been corrected to match the adjacent diagram.

Implementation Notes

⚠️ This release significantly re-factors the schemas in the TAMS specification. Implementations relying on schema structures for automatic code generation should carefully review the changes before upgrading.

Key actions for implementers:

1. Review schema changes if your build pipeline auto-generates code from the OpenAPI spec
2. Adopt Profiles if you have house formats or want simpler Flow creation
3. Implement collected_by_ids filtering for improved content discovery UIs
4. Plan for init segment support if you’re targeting fMP4/CMAF workflows
5. Review editorial purpose tags for multi-essence content labelling
6. Consider Storage Backend tags for fine-grained auth in multi-tenant deployments

Get Involved

TAMS is an open specification developed collaboratively. The full 8.2 release is available on GitHub, including all ADRs, Application Notes, and the updated OpenAPI specification. Contributions, feedback, and implementations are welcome.

TAMS is a Kubernetes-shaped problem

Introduction

TAMS is designed to run anywhere.

That’s not me editorialising, it’s in the spec’s own principles: agnostic to clouds, codecs and containers, deployable on-premise and at the edge as happily as in a hyperscaler. It’s one of my favourite things about it. But there’s a long way between a spec that can run anywhere and software you can actually stand up on your own kit, and further still to something you’d trust in production.

TAMOSS is our first step down that road: an open-source, Kubernetes-native implementation of the TAMS API, built by LiveWyer and released under Apache 2.0. This post is about why TAMOSS is a big step toward enabling teams to have an instant TAMS test instance and towards a production TAMS implementation.

The reference implementation got us here

Most people’s first introduction to TAMS is through the AWS reference implementation. It’s a serverless design with the API Gateway in front of Lambda functions, DynamoDB for the index, S3 for the media, with SQS, EventBridge and Cognito around the edges. And it’s good. It teaches you the API, proves the model, and makes it clear in its README that it’s meant for development rather than production. Which is exactly what a reference should be. Without it, TAMOSS wouldn’t exist. It’s how we, and I suspect most people in this ecosystem, learned the shape of the API.

What a reference deliberately leaves open is everything that comes after “it works”. That is not for want of effort on AWS’s part. They have done a lot to get TAMS in front of teams, and the serverless design is how most people first deploy the API. The limit is in the architecture itself: it is built around AWS primitives, so it runs well but it runs in one place.

How do you run a store somewhere that isn’t AWS? On your own hardware, in a private cloud, at the edge, across the mix of places a real media operation actually lives? And how do you keep it running once it’s there?

That’s the part we picked up, and to us, it looked like a Kubernetes problem from day one.

Why Kubernetes?

Strip TAMS down and you get a stateless HTTP API in front of two pluggable stores, a database for the timeline index and an object store for the media, plus a lifecycle around it all that has to stay correct as things change.

Read that back slowly. It’s close to a textbook description of what Kubernetes operators exist to manage.

The API is stateless, so it wants to be a horizontally scalable Deployment behind a Service. The media plane is S3-compatible by design, which is about the most portable storage contract in computing: the same code runs against a hyperscaler bucket (a RustFS or MinIO cluster in your own racks, or Backblaze B2). The metadata plane is a database, and running one on Kubernetes (or pointing at a managed one) is well-trodden ground. And the bit that usually gets hand-rolled, the ongoing job of assembling all this into a healthy system and keeping it that way, is literally what an operator does. You declare the state you want, and a controller works to make reality match.

Storage backends are a good example. Since version 7 of the spec, a single TAMS store can span multiple object stores. Model a backend as a custom resource, and that stops being bespoke integration work: you declare it, the platform wires it in. The spec’s separation of concerns makes TAMS portable on paper. Kubernetes is what turns that into a store you can stand up on real infrastructure.

What we built

TAMOSS installs as an operator-driven product. The operator, written in Go with Kubebuilder and controller-runtime, watches two custom resources, Tamoss and StorageBackend, and reconciles them into a running system: API, async worker, web UI, schema migrations, the Secrets they all need, ingress routing, and whichever backends you’ve selected. You describe the store you want, the operator builds it and keeps it built.

There are three profiles, all on the same path:

• local-kind brings everything up on a Kind cluster on your laptop, bundled database, object storage, auth and ingress included, so you can poke at a real store within minutes.
• single-server targets one node or a small self-managed cluster.
• multi-server is the production-shaped, replicated topology.

Same path everywhere, so what you learn on your laptop is what you run in your data centre. Locally, it’s one command:

task kind:up PROFILE=local-kind

Every platform service is pluggable via the same declarative interface, which is how a single product reaches so many environments. Per service, TAMOSS provides it, or you bring your own:

apiVersion: tamoss.livewyer.io/v1alpha1
kind: Tamoss
metadata:
  name: newsroom
  namespace: tams
spec:
  backends:
    db:
      providedBy: external      # or bundled, or cnpg (CloudNativePG)
    s3:
      providedBy: external      # or bundled, or rustfs-operator
  auth:
    providedBy: external        # external OIDC, or authentik-blueprints

The design decision I’m most pleased with is actually invisible from the outside: the API knows nothing about Kubernetes.

All the Kubernetes-specific work lives in the operator. The application just reads its configuration and a credentials file from a mounted Secret; the operator is what turns custom resources into those files and keeps them current. That’s deliberate. It means the same store can run somewhere that isn’t Kubernetes at all, as long as something supplies the same files, and we never have to teach the API about whatever platform it happens to be sitting on.

And because the goal is to operate TAMS, not just run it, the operator does day-2 work too. It reports readiness through status conditions and Events, corrects drift when something (or someone) fiddles with the resources it manages, and puts an admission webhook in front of destructive deletes, so nobody removes a store without confirming it with an explicit annotation.

We’re early on this, and there’s plenty still to do. But the direction matters to us: production-readiness as something the platform helps with, rather than a pile of runbooks.

Building on open foundations

TAMS is where it is because the community has spent years making it an implementable open standard, with the application notes, decision records and governance to match. Even picking up the IABM Industry Partnership Award at IBC2025. The foundations are robust, and we are pleased to add to them with TAMOSS.

But to be clear, TAMOSS is just one independent implementation among what should be many. More implementations were always the point; it’s written into the spec’s principles, and the team behind TAMS has been glad to see another one arrive.

Where we’re looking next is the live plane. TAMS covers stored, time-addressable media. The EBU and NABA’s Dynamic Media Facility work includes MXL, the Media eXchange Layer, a shared-memory data plane for moving media between live functions, container-friendly from the start. TAMS for the stored side, MXL for the live side, both as cloud-native workloads, and you can start to see a broadcast facility built the way we build everything else.

TAMOSS is open source and available now at github.com/livewyer-ops/tamoss. If you run media infrastructure and have wanted a TAMS store you can own end to end, then bring it up on your laptop. Kick the tyres, and tell us where it breaks.

Blog first published on the LiveWyer website

Fast-turnaround workflows using TAMS

Live video intelligence with TAMS and agentic AI

As with previous trade shows, the main multi-vendor demonstration will be on the AWS booth. However with more and more products supporting TAMS then we wanted to provide a simple guide on where to find TAMS around the show.

AWS (W1701)

The AWS booth will once again host a multi-partner TAMS demo bringing together many of the latest developments in the TAMS eco-system in one place. The demo will include TAMS native camera to cloud, integrations between TAMS and the EBU Media Exchange Layer (MXL), new and updated editing capabilities, compliance recording capabilities plus generative AI for near live video understanding and agentic workflows.

CuttingRoom (N2172)

Edit directly from your TAMS store in the CuttingRoom Cloud Editor. Add growing TAMS recordings even directly to your timeline. Shoot directly to your TAMS store with the mobile news gathering app CuttingRoom Reporter, enabling editing while shooting.

https://www.cuttingroom.com

Konstrukt

Konstrukt’s Compliance Vault gives media companies a frame‑accurate, reliable, and readily available record of everything that goes to air or online, along with the ability to act on it quickly. Built as a cloud‑native workflow on TAMS, Compliance Vault lets media teams record once and reuse the same time‑indexed media across applications well beyond compliance. The record‑once model, combined with a serverless architecture, makes the solution’s economics attractive and cost‑optimized. Using Omakase Player (player.byomakase.org), the native TAMS player included in the open‑source TAMS reference implementation, Compliance Vault provides teams with a browser‑based application to efficiently review, edit, and export media.

LOGIC media solutions GmbH

LOGIC’s modular platform demonstrates how we build custom, cloud-native media workflows based on TAMS. Using a soccer highlight use case as a reference implementation, it shows how modules such as ingest, playback, edit-by-reference, event-driven highlight processing, and AI can be combined into tailored workflows for specific workflows and requirements rather than one-size-fits-all systems. The project is shortlisted for the IABM Impact Awards 2026 in the Transformational Project Award category.

https://logic.tv/

LucidLink (N2940)

LucidLink Connect revolutionises the creative workflow by seamlessly integrating TAMs Store with any NLE. Leveraging advanced file-streaming technology, it enables editors to access and edit growing files in real time, eliminating the need for local downloads or cumbersome transfers.

https://www.lucidlink.com/events/nab-2026

Matrox (N2451)

Matrox ORIGIN is SDK that allows developers to build media application using simple REST APIs. It provides a complete suite of media processing functions including TAMS readers and writers. In the demo, ORIGIN plays back flows from TAMS into ORIGIN Fabric which are also available in MXL, at the same time, ORIGIN/MXL flows are written into TAMS

https://video.matrox.com/en/products/broadcast-media/origin-series

Mavis (N2161)

Mavis Camera is designed to connect a wide range of acquisition sources into modern production workflows. In this demo, we extend our existing camera-to-cloud workflows by supporting TAMS from the internal iPhone camera and external HDMI and SDI sources through devices such as Atomos Ninja Phone and the Accsoon SeeMo range. This shows how Mavis can bridge traditional video hardware and cloud-native production, bringing signals from professional cameras and other external gear into the same real-time workflow.

https://mavis.cloud

Mimir (N2850)

Mimir is a cloud-native platform that simplifies how creative teams manage their media. It acts as a unified “brain” for your assets, allowing editors to find and use files instantly without worrying about where they are physically stored. Whether your high-res footage is on a local server, a NAS, or in the cloud (like AWS S3 or TAMS), Mimir handles the technical logistics so you can stay focused on the storytelling.

https://onemimir.com/news/see-mimir-at-nab-2026

Norsk (W3113)

Norsk’s TAMS (Time-Addressable Media Store) integration enables live content to become immediately queryable as it’s captured, eliminating the traditional boundary between live production and VOD workflows. TAMS, an open-source specification developed by BBC R&D and now adopted by AWS, Adobe, Sky, and others, stores segmented media in cloud object storage with HTTP API access indexed by timeline position. Norsk’s MediaStore component brings this capability natively into Norsk Studio workflows.

https://norsk.video

Reuters Imagen (W1624)

Reuters Imagen provides real-time activation of live content through multi‑cloud TAMS ingest. Automated enrichment against the content in TAMS ensures live assets are immediately discoverable, enriched, and available for downstream automation and use.

https://imagen.io

Techex (W2267)

tx darwrin provides comprehensive manipulation and syncrhonisation of transport streams ahead of writing to a TAMS store. tx darwin is a software platform which runs in the cloud or on-prem supporting compressed or uncompressed media workflows. Now, it’s possible to synchronise miltiple feeds on writing, write as multiple essences or a single combined stream and even perform video.and audio confromance ahead of a TAMS media store.

https://techex.tv

Zixi (W2057)

Zixi enables broadcasters to bridge live streaming workflows with TAMS-based VOD environments. At NAB, Zixi will demonstrate how live streams can be ingested and written as assets into a TAMS store, making live content immediately available for downstream clipping, archive, compliance, and monetization workflows. ZEN Master provides orchestration, monitoring, and per-stream or per-event control for flexible and reliable operations

https://zixi.com

This expansion of the initial TSC represents an important step towards establishing comprehensive open governance for TAMS. As announced in the 28th January 2026 blog post “Moving TAMS towards Open Governance,” the TAMS project is transitioning from BBC Research & Development ownership to community ownership under an open governance model. The move recognises that as more systems, solutions, and products are built on TAMS, the technology should be owned by the community rather than any single organisation.

The initial committee’s primary mandate will be to define the open source strategy for TAMS and select the appropriate governance organisation to oversee the project’s future development. “The formation of this initial TSC is a crucial phase in TAMS’s evolution,” said Sam Mesterton-Gibbons, Chair of the TAMS Technical Steering Committee. “Once the governance framework is established, a full TSC will be appointed to guide the long-term technical direction of the project.”

The two new TSC members bring valuable industry perspective to the committee:

“CuttingRoom has been involved with TAMS for the last two years, and we’ve seen how it can revolutionise media workflows,” said Glenn Pedersen of CuttingRoom. “Joining the initial TSC allows us to help ensure TAMS develops in a way that serves the entire industry.”

“Being part of the award-winning news demo at IBC 2025 showed me firsthand the transformative potential of TAMS,” said James Elliott of Elliott Media. “I’m excited to contribute to shaping its open source future and helping the industry realise the full benefits of this technology.”

Current TSC Members

The TSC purposefully brings together a balanced mix of technology vendors, broadcasters, and TAMS customers, alongside the BBC Research & Development team that has been instrumental in developing the TAMS specification.

The TAMS initial Technical Steering Committee is composed of the following members:

• Sam Mesterton-Gibbons (BBC) - Chair
• James Sandford (BBC)
• Richard Lynton-Evans (BBC)
• John Biltcliffe (AWS)
• Chris Swan (AWS)
• James Elliott (Elliott Media)
• Glenn Pedersen (CuttingRoom)

Following this transition period, once the governance framework is established, it is expected that the TSC will be rebalanced so that no organisation controls more than one vote. All those who applied to join the TSC in this round will be invited back at that point to be considered for the updated TSC, plus there will be the opportunity for new individuals to express their interest.

Please note: the in person option is now full however you can still sign up to attend TAMSCon virtually. Click here to sign up.

Day 1

Day 1 of TAMSCon will focus on the highest priority topics in the community today. With updates from key customers and partners to how TAMS will be governed going forward. In the afternoon there will be multiple talk tracks providing session from those that are new to TAMS to diving into some of the latest developments. For the non-technical there is a dedicated business track to understand the value that TAMS can bring

Day 2

Day 2 of TAMSCon is a hands-on day, with attendees free to move between practical activities and formal Breakout Sessions throughout. All tracks will be available to both virtual and in person attendees.

Deploy TAMS is ideal for those new to TAMS, offering the chance to deploy your own personal TAMS instance, use the API to create content, and explore the open-source TAMS Tools across a variety of workflows.

Partner Interop gives vendors the opportunity to test solutions end-to-end - from ingest and playback through to editing and export - as well as contribute ideas for a formal TAMS test suite.

TAMS Hackathon is for those with existing TAMS knowledge, development skills, or a willingness to vibe code. A content store will be provided - including sessions from Day 1 - giving you the chance to build something new and share it with the group.

Drop-in Expert Sessions are available throughout the day. Whether you have technical questions, want to explore the benefits of TAMS, or discuss how it fits your workflows, the TAMS experts will be on hand to help.

Download

The whole agenda can be downloaded here

Webinar available online

On Thursday 12th February 12th TVBEurope and techex hosted a webinar to explore what TAMS is, its global potential, and the agility it can deliver in near-live editing and production workflows. The webinar was chaired by Jenny Priestley (Content Director, TVBEurope) and will featured contributions from:

• Dave Mitchinson (Solutions Director, Techex)
• Kevin Morris (Product Manager, BBC)
• John Biltcliffe (Senior Solutions Architect, AWS)
• James Elliott (Managing Director, Elliott Media)
• Rebecca Light (Group Head of Content Mngmt & Quality Control - Content Technology & Innovation, Sky)

The webinar is now available online. Head to the website and register to be able to watch the whole session.

TVBEurope article

TVBEurope has also taken some of the key themes and discussion topics from the webinar and published them as a dedicated article. This can be viewed online at the TVBEurope website

Tuesday 10th and Wednesday 11th March

The first ever TAMSCon will bring together the whole TAMS community for the first time. We want to share with the community some of the progress over the last 12 months, as well as look forward to what is coming up in 2026. This session is for those that have been in the community since the start or may just be starting to look at TAMS. Session will be held principally in London at the AWS office in Holborn, but there will be option for virtual participation.

Day 1

The morning will be a set of presentations including:

• Updates from some key customers on where they are in their TAMS adoption journeys
• Quick fire sessions from a selection of new partners who have deployed TAMS support in their products
• An update on the TAMS Governance and a chance to ask questions about what it means

The afternoon will break out into a set of different tracks:

1. For those new to TAMS there will be a 101 stream focusing on what TAMS is and how it works
2. A focus on what TAMS means for business leaders and operational teams
3. Advanced technical sessions focusing on some of the proposed changes to the TAMS specification

The day will end with drinks and a chance to network

Day 2

The second day is a more informal session and is not mandatory to attend both days. The day will include 3 key workstreams:

1. For partners with TAMS capable products, there will be a chance to test interoperability between them and focus on ensuring consistency across the TAMS experience.

2. We will be running a hands-on workshop for those new to TAMS who would like to dive deeper and understand it better. This will include deploying a TAMS instance, creating content and then deploying the TAMS Tools to interact with the store.

3. A drop in TAMS Surgery will be avialable with experts on hand to answer questions, talk through workflows and help think about what TAMS could mean for your company.

Sign up

Sign up here