TAMOSS Time-Addressable Media Open Source Store

TAMOSS is an open source, Kubernetes-native implementation of the BBC Time-Addressable Media Store (TAMS) API, released by LiveWyer under the Apache 2.0 licence. It lets any organisation run a fully functional, TAMS-compatible media store on its own infrastructure, from a laptop to a production cluster, with no proprietary licensing and no vendor lock-in. In this demo, recorded live during the TAMS Community Call in June 2026, David O'Dwyer (Director, LiveWyer) walks through standing up a TAMS store from scratch on a local cluster, adding a second storage backend on the fly, and upgrading a running store between releases, all driven by a Kubernetes operator. This is an early release and very much hot off the press. LiveWyer is keen to work with as many people as possible to test it, iron out the kinks, and tune performance, so feedback and contributions are very welcome. What The Demo Covers A single-command local setup using kind (the local-kind profile), with the operator provisioning everything and outputting credentials at the end. The supporting platform built on established open source projects rather than reinventing them: cert-manager for TLS, Traefik for ingress, Authentik for auth, CloudNativePG (CNPG) for Postgres, and RustFS as the default S3-compatible store. TAMOSS deliberately does not try to own the lifecycle of these operationally complex services, it leans on the operators that already do that well. The TAMOSS operator and the custom resource model: deploy the operator once, then declare a TAMS store with a Tamoss custom resource and let the operator reconcile the API, worker, web UI, database, storage, and routing for that instance. Dynamic, declarative storage: registering a second backend (RustFS locally, and external S3-compatible storage such as Backblaze in LiveWyer's internal testing) via a StorageBackend custom resource, with credentials held in Kubernetes secrets and bucket provisioning and API registration handled automatically. No API restarts, all live. Operator-driven upgrades: the operator supports the current and previous major version, so you upgrade the operator without touching your stores, then patch each store individually. The demo shows an in-place upgrade from one release to the next, including the schema migration, with the existing data surviving the move. Chapters 0:00 Introduction (John Biltcliffe, AWS) 0:24 What we are demoing (David O'Dwyer, LiveWyer) 0:34 Spinning up a local Kubernetes cluster with kind 1:15 Installing the platform services (cert-manager, Traefik, Authentik, CNPG, RustFS) 2:28 Deploying the TAMOSS operator 2:49 Creating a TAMS store with a custom resource 3:43 Verifying the TAMS API 4:09 Registering a second storage backend (RustFS and Backblaze) 5:51 Live ingest with no restarts 6:18 Upgrading a TAMS store between releases 8:45 What is next and how to get involved Get Involved LiveWyer would love your help testing TAMOSS and shaping where it goes next. Pull down the public repo to try it yourself, and reach out via the TAMS Slack channel or the contact form. TAMOSS Repository: https://github.com/livewyer-ops/tamoss Announcement blog: https://livewyer.io/blog/livewyer-rel.... Contact LiveWyer: https://livewyer.io/tamoss-contact TAMS specification: https://timeaddressablemediastore.org BBC TAMS spec (GitHub): https://github.com/bbc/tams LiveWyer: https://livewyer.io Note: TAMOSS is an independent implementation of the BBC TAMS specification and is not affiliated with or endorsed by the BBC.