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 work and open standards
For Ericsson's subtitling service, which produces more than 100,000 hours of live captioning a year for broadcasters, we built a container-based speech recognition pipeline which generates English and Spanish subtitles automatically and costs nothing to run when idle. It also cut the service's licence costs by 60%.
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:
Our own TAMS implementationRun 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
Media partners
The companies we work alongside to build media workflows.
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.
Free two-hour workshop
- No obligation
- Remote, or on site in London
- Run by our senior engineers
After an introductory call, if we can help, we will arrange a free two-hour workshop with our engineers. With no slides and no sales pitch, we look at your setup as it stands today, pick out the problems costing you most, and talk through the options for each.
Where you are today
You walk us through your platform, your teams, and the constraints you work within.
What is costing you most
We dig into the one or two problems which take the most time, money, or risk.
Options and next steps
We talk through the trade-offs of each option, including the ones which do not involve us.
Afterwards, we send you a short written summary of what we found and the options we discussed. Where it makes sense for us to help, it includes a proposed scope and a rough cost, so you have something concrete to take to whoever holds the budget.
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
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 arrange a free two-hour workshop.
Book an introductory callCall us on +44(0)2036080110 (UK business hours), or send us a message.