Introducing the Time-Addressable Media Open Source Store (TAMOSS)
TAMOSS is an open-source, Kubernetes-native implementation of the BBC TAMS API. One product, one deployment model, with the flexibility to run it based on your unique scenario.
A single laptop, a server, a full hybrid cloud setup, or at an enterprise scale across regions. Complete flexibility, all without vendor lock-in.
Media platforms shouldn't decide where your content lives.
Content stores bundle storage with their tools, their cloud, and their pricing model. It works until you hit those use cases where it doesn't.
Your platform only runs where your vendor lets it.
The storage and tools with Avid, Adobe, Frame.io all come bundled together. The cloud and terms are theirs.
Outside broadcast needs infrastructure that travels.
Cloud-only stores impact productivity when production is on the road, the connection is patchy, or the venue dictates where the kit lives.
Switching cloud means migrating petabytes.
Proprietary stores make exits expensive. The longer you stay, the more complex it gets when the business needs to move.
An open API specification, now openly deployable.
TAMS (Time-Addressable Media Store) is an open API specification, originally developed by the BBC. It defines how media is chunked into time-stamped segments and how those segments are stored, retrieved, and reassembled.
The TAMS API deliberately doesn't define how the store is deployed. That's where TAMOSS comes in.
TAMOSS (Time-Addressable Media Open Source Store) is the production-ready, deployable platform. We package the TAMS API with Kubernetes as a thin orchestration layer, plus the ingest, monitoring dashboard, authentication, and player you need to run a TAMS store in production. The same product runs on a laptop, a single server, or a multi-region cluster. You choose the profile to match the workload. The product underneath is the same.
The same product, sized to your workload.
Kubernetes has a reputation for being heavy, but TAMOSS is the counter-example. A single declarative deployment that scales from a laptop to a data centre, without the need for re-architecting.
Deployment 01
Local
A single node. Runs on your laptop with Kind in just two commands, and you have the full stack.
Best for: remote editing, development, demos
Hardware: Your laptop
Deployment 02
Single server
One dedicated machine. Choose between on-prem, a VM or in your chosen cloud.
Best for: single productions, OB trucks, small facilities
Hardware: one server, on-prem, cloud or virtual
Deployment 03
Multi-server cluster
Replicas, redundancy, and scale. The same TAMOSS, configured for large production load.
Best for: facility-wide and multi-site operations
Hardware: any conformant Kubernetes
Built for media, built by platform engineers.
Tool choice flexibility
Vendor-neutral store
Any application that speaks the TAMS API can read from it and write to it. Whether that is your editor, your transcoder, your playout system, or your archive.
Camera-to-cloud ingest
Ingest content from cameras and devices in the field, without committing to one vendor's ecosystem.
One pattern, every workflow
News, sport, and post-production workflows can run on the same underlying infrastructure.
A cost shape you control
Pay for the storage and compute you actually use, not for a per-seat licence on the store itself.
Production-grade deployment
BBC TAMS v8.0, no extensions
No proprietary API surface. Only Kubernetes-native conventions (/healthz, /readyz) plus runtime concerns the spec leaves open.
Modern stack, no surprises
FastAPI backend. PostgreSQL for metadata. RustFS for S3-compatible object storage. Helm-deployable on EKS, GKE, AKS, or any conformant Kubernetes.
OpenTelemetry-ready
Conditional instrumentation. Bring your own collector, Prometheus, and Grafana, with no bundled observability stack to fight.
Durable async lifecycle
Workers for flow deletion, webhook delivery, and object cleanup. PostgreSQL-backed claim semantics with exponential-backoff retry. The operations work has already been done.
What's inside the stack.
Delve into the TAMOSS tech. Browse the runtime topology, the request flow, and the code structure beneath.
Kubernetes deployment topology
Application architecture & request flow
Code structure & data access layers
Open source, pilot, or partnership.
As TAMOSS is open-source, there are multiple deployment options depending on your needs. Start with the open-source product, or engage LiveWyer for additional deployment support.
Self-serve
Free · MIT License · Community support
Clone the repository. Deploy with Helm by following the step-by-step guide on GitHub. This is a completely free TAMOSS deployment, with free support available via the TAMOSS community Slack.
Best for: engineering teams evaluating TAMOSS, smaller deployments, and contributors.
LiveWyer Pilot
Fixed price · Fixed scope · Real workloads
We deploy, validate, and hand over a working TAMOSS using your chosen real-world workload on your chosen target. A fixed-price end-to-end Pilot with zero obligation for any further delivery efforts.
Best for: organisations validating TAMOSS against a specific workflow or production.
LiveWyer ProServe
Fixed price or T&M · Personalised scope
If your team needs support with implementation, LiveWyer have the delivery capability to help you succeed, integrating within your existing engineering team to supplement delivery and add immediate value.
Best for: organisations looking to build on the pilot implementation and need additional engineering support.
Delivery Partnership
Fixed price or T&M · Client delivery support
We collaborate with our partners and their customers to architect, build, validate solutions. If you have a customer who could benefit from an Open Source TAMS implementation, let's discuss how we can help.
Best for: Current and future partners with clients who need support with their TAMOSS implementations.
Pilot Partners
If you're considering TAMOSS for either a production workload, an outside broadcast, or a facility-wide deployment, we'd love to talk it through.
Get involved
Before the official launch of TAMOSS you can join the Cloud Native Agile Production workspace. Our Github repo will be live on launch and the TAMOSS Community channel is coming soon.
The questions worth meeting head-on.
Isn't Kubernetes expensive?
A common assumption, and one we'd rather meet head-on. The cost of Kubernetes scales with what you ask of it. A single-node TAMOSS deployment is cheap to run, and a local deployment is completely free. If you are scaling to a multi-region cluster, the costs are driven by the multi-region cluster, and the thin Kubernetes orchestration remains cheap. In other words, the supervisor doesn't impose costs; they depend on the workload, the same way they would with any other infrastructure.
How does this compare to running TAMS on AWS?
The simple answer is TAMOSS is complementary, not competitive. AWS provides a serverless TAMS implementation. TAMOSS provides a Kubernetes-native version. If your workload is happy on AWS, run it there. If you need on-prem, hybrid, multi-cloud, or portable infrastructure, that's where TAMOSS earns its place.
Is this only viable for large deployments?
No. The open-source product runs on everything from a laptop to a full multi-region cloud deployment. If you need support with a larger-scale deployment, LiveWyer have professional services and a pilot offering as a great first validation step to build confidence.
What's the relationship with the BBC?
TAMS is an open API specification, stewarded by the BBC. TAMOSS is an independent open-source implementation by LiveWyer. We track the upstream API spec faithfully, with no proprietary extensions or API drift.
What license? Who maintains it?
TAMOSS is released under the Apache License, Version 2.0, with permissive use, modification, and redistribution, including in commercial products. LiveWyer maintains the project and welcomes community contributions through the GitHub repository, Slack engagement and regular meeting cadence.