Broadcast facilities, built the cloud native way
Broadcasters and media organisations are moving production onto software-defined infrastructure and open standards, and most of the risk sits in the platform underneath. We were London's first Kubernetes consultancy, and we support the open standards making that move possible: TAMS for stored media, MXL for exchanging live media between functions, and the Dynamic Media Facility architecture which brings them together.
Talk to our engineersProblems we see in media organisations
Most platforms were never built for media workflows.
Media platform workshop
- Two hours
- Remote or on site in London
Work through a media workflow or infrastructure decision with our senior engineers. Compare practical options against your operational constraints and receive a written summary of the trade-offs and recommended next steps.
We cover the cost of this initial workshop. Any further work is scoped and agreed separately.
Book an introductory callWe use the call to understand your priorities and agree the workshop focus.
What we can cover
- Where TAMS, MXL, and DMF fit in your plans
- Running live and file-based media functions on Kubernetes
- On-prem, cloud, and OB deployment options
- The platform skills your team would need
What you leave with
- A view on which open standards suit your workflow today
- A sketch of a deployment which fits your sites and your cloud
- A list of first steps, whichever vendors and implementations you choose
How we help
Our media work builds on the same Kubernetes and cloud engineering we do everywhere else, applied to live and file-based production.
Media work and open standards
For Red Bee Media, we built an API-driven control plane for broadcast file delivery on AWS. It connected four existing systems without changing their software, replacing file drops and manual hand-offs with a managed workflow. We supported the service for three years before handing it to the in-house team.
LiveWyer is a supporter of the Dynamic Media Facility, alongside broadcasters and vendors. DMF builds facilities from open interfaces, so functions from different vendors work together and run on whichever platform and deployment model suits you.
We see TAMS handling the stored side of a facility and MXL the live side, with both running as cloud native workloads. Alongside TAMOSS, we have built an MXL capability which runs inside a Kubernetes cluster.
Further reading:
Run a TAMS store you own, anywhere
TAMOSS is the open-source, Kubernetes-native TAMS store we built and maintain. You install a Kubernetes operator, declare the store you want, and the operator builds it and keeps it that way.
The same product runs on a laptop, an OB truck, an on-prem server, or across cloud regions, with no proprietary extensions and no vendor lock-in.
- Open source Apache 2.0 licensed, on GitHub
- Kubernetes-native Driven by an operator, with day-two behaviour built in
- Two commands to start The full stack running on your laptop
- Scales without re-architecting From a single node to multi-region clusters
Start with an intro call
Book an introductory call with a senior engineer. Allow up to an hour over video. If we can help, we will agree the focus for your media platform workshop.
Book an introductory callCall us on +44(0)2036080110 (UK business hours), or send us a message.

