LiveWyer launches open-source Kubernetes implementation of BBC's TAMS API
LiveWyer has launched TAMOSS, an open-source, Kubernetes-native implementation of the Time-Addressable Media Store (TAMS) v8.0 API. This allows organizations to run a TAMS-compatible media store on their own infrastructure, aimed at preventing vendor lock-in. TAMOSS supports managed or external PostgreSQL, S3-compatible storage, OAuth2/OIDC authentication, and HTTP ingress.
Key Takeaways
- TAMOSS uses an operator-driven deployment model with local-kind, single-server, and multi-server profiles.
- The implementation supports S3-compatible storage, PostgreSQL databases, and OAuth2/OIDC authentication.
- Published under the Apache 2.0 license, the tool is a vendor-neutral alternative to centralized cloud media stores.
- Integrated day-2 controls provide automated drift correction and deletion protection for production media workloads.
Why It Matters
This release shifts TAMS from a cloud-locked specification to a portable infrastructure component. By providing a Kubernetes-native way to self-host the API, LiveWyer enables broadcasters to harmonize live and file-based workflows without committing to specific cloud provider ecosystems. This is a significant step for organizations pursuing multi-cloud or hybrid-cloud strategies, as it ensures that the foundational 'edit-by-reference' capabilities of TAMS remain accessible across varied compute environments. Watch for increased adoption by smaller production houses and regional broadcasters who have previously been deterred by the high egress and lock-in costs of major cloud-based TAMS implementations.
Additional Context
The Time-Addressable Media Store (TAMS) specification, originally developed by BBC Research & Development, has gained substantial industry momentum since earning the IABM Industry Partnership Award at IBC 2024. Per Amazon, September 2024, early reference implementations focused heavily on the Cloud Native Agile Production (CNAP) framework, which utilized serverless AWS technologies like Amazon S3 and MediaConvert to handle chunked media segments. While this provided high scalability, it essentially tied early TAMS adopters to a specific cloud architecture. In 2025 and 2026, the industry is increasingly prioritizing hybrid-cloud operations to manage costs and latency. Per CSI Magazine, December 2025, broadcasters are moving toward a pragmatic phase where workloads are split between public cloud, private infrastructure, and the edge. This transition has spurred a demand for open-source tools that can handle stateful media storage within standard container orchestrators. Major vendors including AWS, Reuters, and various broadcast technology providers have supported TAMS to enable faster "edit-by-reference" workflows, which eliminate the need for costly and time-consuming file transfers by referencing specific time-based segments directly. The launch of TAMOSS by LiveWyer, a London-based consultancy specialized in Kubernetes, reflects a broader trend toward "platform engineering" within the media sector. Per Medium, May 2026, many organizations are now focusing on Kubernetes-native storage solutions like Simplyblock and Longhorn to provide the high-throughput, low-latency performance required for live video. By mirroring the TAMS v8.0 specification—which recently added mandatory frame rate signaling and improved webhook management in October 2025—TAMOSS allows engineers to treat media storage as a declarative Kubernetes resource, aligning broadcast operations with modern GitOps and DevOps practices.
Read full article at tvbeurope.com
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source