By Matt Zajicek, VP Product, Live Production
What does hybrid as an operating model actually mean for broadcasters?
The broadcast industry has long treated hybrid infrastructure as a necessary stop between traditional on-premises facilities and an eventual all-cloud future. Today, the conversation has shifted from “transition” to understanding where each workload belongs.
That’s an important distinction from the assumption that everything belongs in the cloud. Broadcasters have learned that no single deployment model delivers the best answer for every application. Instead, they’re building infrastructures that combine dedicated hardware, IP networking, private cloud, and public cloud according to the operational requirements of each workflow. Hybrid has evolved from a migration strategy into an operating model.
When should Tier-1 live production stay on-premises rather than move to the cloud?
The reason is straightforward: live production isn’t a single use case. A Tier-One sports production covering Formula One or Premier League football demands deterministic performance, ultra-low latency, and uncompromising picture quality. Those workflows continue to benefit from broadcast-grade hardware, uncompressed ST 2110 infrastructure inside the facility, and JPEG XS contribution from the venue.
Illustrative example: Tier-1 football on-premises, running ST 2110 and JPEG XS, to maintain frame-accurate, deterministic contribution from venue to facility.
At the same time, the same broadcaster may produce hundreds of regional sports events, studio programs, or lower-tier competitions where different economic realities apply. Those productions can benefit from software-based processing, cloud resources, and more flexible deployment models that reduce operational costs while maintaining professional production quality. The important point is that neither approach is universally better; they simply solve different problems.
Public cloud vs private cloud: which live production workloads fit where?
This shift has also changed how broadcasters think about investment. Rather than choosing between hardware and software, or between on-premises infrastructure and cloud services, engineering teams increasingly evaluate three variables: performance, cost, and adaptability. Those priorities determine where each workload should run today, and where it may move tomorrow.
Cloud remains an essential part of that equation, but experience has brought greater realism. Always-on production environments can become expensive when built entirely around consumption-based public cloud services. Conversely, short-term, high-profile events such as the Olympic Games or FIFA World Cup are ideal candidates for elastic cloud infrastructure, where temporary capacity can be deployed.
Illustrative example: a pop-up mega-event such as the Olympic Games, where elastic public cloud capacity is spun up for the duration and released once the event ends, avoiding idle hardware between cycles.
Private cloud has also emerged as an increasingly attractive option, offering many of the operational benefits of software-defined production while allowing broadcasters to maintain greater control over performance, costs, and infrastructure.
This flexibility is becoming the defining characteristic of modern broadcast architecture. The organisations best positioned for the future will possess the ability to move workloads between environments without rebuilding their workflows or changing operational practices. Hardware, software, private cloud, and public cloud each have an important role to play, and the balance between them will continue to evolve as standards mature and compute technologies advance.
A quick decision framework
| Scenario | Recommended environment | Why it works |
|---|---|---|
| Tier-1 sports (Formula One, Premier League) | On-premises, ST 2110 + JPEG XS | Deterministic latency, uncompromised picture quality |
| Studio and always-on programming | Private cloud or on-premises | Cost predictability, 24/7 uptime |
| Regional and lower-tier events | Software-based, private cloud | Flexibility, reduced operational cost |
| Mega-events (Olympic Games, FIFA World Cup) | Public cloud (burst capacity) | Temporary capacity, no idle capital expenditure |
On-premises, private cloud, and public cloud at a glance
On-premises hardware and ST 2110
- Performance: deterministic latency, broadcast-grade reliability, uncompressed quality
- Cost: high upfront capital expenditure, predictable operating cost, efficient for always-on production
- Adaptability: fixed capacity, limited elasticity, purpose-built
Private cloud
- Performance: software-defined flexibility, near-broadcast-grade reliability
- Cost: predictable, no public cloud consumption pricing, operator-controlled
- Adaptability: scalable within owned infrastructure, operationally familiar
Public cloud
- Performance: variable latency, well suited to non-deterministic workloads
- Cost: consumption-based, expensive for always-on use, efficient for short bursts
- Adaptability: highly elastic, ideal for temporary or unpredictable demand
How will MXL and DMF change where broadcasters run processing?
That same evolution is driving interest in newer initiatives such as the Media eXchange Layer (MXL) and the EBU’s Dynamic Media Facility (DMF). These emerging frameworks represent the next stage of software-defined media facilities. Instead of treating individual processing applications as isolated systems, they introduce shared media layers that allow multiple services to access the same media resources efficiently. As these standards mature, broadcasters will gain greater flexibility to deploy processing wherever it makes the most operational sense while maintaining interoperability across vendors and platforms.
Today, most processing applications operate as isolated systems, each with its own storage, interfaces, and media handling. MXL and DMF introduce a shared media layer instead, so multiple services can access the same media resources at once, cutting the duplication that comes with running separate copies of the same content. That shared, standardised interface is also what makes portability practical: a broadcaster could move a transcoding step from on-premises hardware to a cloud instance without rebuilding the surrounding workflow, because the interfaces either side of that step stay the same.
None of this removes the importance of hardware. In fact, hybrid production depends on hardware and software working together more effectively than ever before. At Appear, that philosophy shapes both the X and VX Platforms. The same operational framework supports high-density hardware processing for mission-critical contribution while extending workflows into software running on private or public cloud infrastructure. That consistency allows broadcasters to choose the deployment model that best fits each application without introducing unnecessary operational complexity.
Hybrid is not a compromise but a recognition that modern broadcast operations require multiple infrastructure models working together seamlessly, with every workload placed where it delivers the greatest operational value. And the real value of hybrid production is defined by the ability to orchestrate workflows across multiple environments while maintaining the performance, resilience, and operational visibility broadcasters expect from mission-critical live production.
The standards will continue to evolve, compute platforms will become more capable, and software-defined production will continue to expand. The goal, however, remains unchanged: giving broadcasters the flexibility to place every workload where it delivers the greatest value without sacrificing operational confidence.
Common misconceptions about hybrid production
Myth: the end goal is full cloud migration.
Fact: cloud is one tool among several. Always-on, latency-critical production can become cost-prohibitive in public cloud — the goal is workload-appropriate placement, not a single destination.
Myth: hardware and cloud are competing choices.
Fact: modern hybrid production depends on both working together. Hardware handles deterministic, mission-critical chains; cloud handles elasticity and flexibility.
Myth: private cloud is just a compromise.
Fact: private cloud delivers many of the operational benefits of software-defined production while giving broadcasters control over performance and cost that public cloud cannot guarantee.
Six rules of thumb for placing live workloads
- Keep always-on, latency-critical production chains on-premises or on private cloud.
- Burst non-critical or time-limited workloads to public cloud, and release that capacity once the event ends.
- Evaluate workload placement against three variables — performance requirement, cost model, and need for adaptability — rather than a default preference for cloud or hardware.
- Design workflows so processing can move between environments; lock-in to a single deployment model is the real risk.
- Treat hardware and software as partners, not alternatives — mission-critical hybrid production depends on both.
- As MXL and DMF mature, default to standards-based interfaces to preserve flexibility across vendors and platforms.
In our next article, we’ll explore one of the most important pieces of that puzzle: securing hybrid production environments. As media workflows span facilities, remote sites, and cloud infrastructure, security becomes a fundamental requirement for protecting live production.
Meet Appear at IBC2026
We’ll be in Amsterdam, ready to talk through where hybrid fits your workflows.