Hybrid is the destination, not the detour

By Dak Dillon May 18, 2026

Weekly insights on the technology, production and business decisions shaping media and broadcast. Free to access. Independent coverage. Unsubscribe anytime.

For several years, “hybrid” carried an implicit asterisk. It was the bridge between on-premises broadcast facilities and full cloud production, a way to manage the risk and economics of migration while the industry caught up.

Across our recent Industry Insights roundtable conversations on cloud production, that framing has largely disappeared. Vendors and broadcasters now describe hybrid not as a phase but as the destination.

“Hybrid isn’t a transitional state. For most broadcasters, it’s the end state. The economics and risk profile of a full cloud migration don’t work for everyone, and the reality is that organizations will run on-prem and cloud infrastructure in parallel for years,” said Golan Simani, director of cloud and technical operations at TAG Video Systems, in the Industry Insights roundtable on cloud production.

That position appeared in responses from companies with different product lines and customer bases.

A consensus, not a single voice

The agreement is notable because the participants compete in adjacent spaces and have different commercial incentives. Yet the language each used to describe hybrid landed in nearly the same place.

“Hybrid is no longer a transitional phase for most organizations; it is the operating reality. Broadcasters are connecting existing facilities, remote production, partner workflows and cloud resources in ways that let them evolve step by step instead of forcing a disruptive rebuild,” said Yaya Selva, CMO at Net Insight.

“Hybrid architectures are the reality for most professional media organizations today. They allow teams to modernize incrementally while leveraging existing investments while adopting cloud services where they make sense,” said Guillaume Aubuchon, VP of product management at Avid.

“Hybrid has really become the default model, because it balances the costs and strengths of both environments,” said John Mailhot, SVP of product management at Imagine Communications.

Advertisement

The repetition matters.

Earlier in the cloud production conversation, the industry’s center of gravity had drifted toward a cloud-first posture in which hybrid was a stop along the way. The current language describes parallel infrastructure as the long-term operating model rather than an interim accommodation.

The economic case

The most consistent argument for hybrid’s permanence is financial. Broadcasters that ran multi-year cloud experiments found that cost predictability did not always favor the cloud, particularly for high-utilization workflows.

“Relying heavily on public cloud workflows can introduce cost unpredictability and performance concerns, particularly in complex, multi-partner environments where data transfer and service layers quickly add up. This is further complicated by the need to support both legacy distribution and rapidly growing streaming platforms. As a result, many are re-evaluating their cloud strategies and moving toward hybrid approaches that combine public cloud with private infrastructure and data center resources,” said Rick Young, SVP and head of global products at LTN.

That re-evaluation has produced a more pragmatic split. Stable, always-on workloads tend to stay on owned infrastructure where the cost curve is predictable. Burst capacity, redundancy and short-term needs move to the cloud.

“Broadcasters keep core, high-utilization workflows on-prem for control and cost predictability, while using the cloud for overflow, resilience, and short-term needs. That combination gives them flexibility without forcing a full shift in either direction,” said Mailhot.

The argument is not against cloud. It is against any single architecture as a universal answer.

The latency case for staying close

The second argument for hybrid is technical. Live production carries timing and quality requirements that do not always translate to public cloud environments, particularly when signal paths cross multiple service boundaries.

“In simple terms, organizations are keeping the parts of the workflow that benefit from deterministic performance in dedicated infrastructure, while using software and cloud where agility, orchestration and elastic scale add the most value. They can modernize without having to rebuild everything at once,” said Ian Wagdin, VP of technology and innovation at Appear.

Mailhot framed the same principle as a workflow design rule.

“Most organizations are taking a hybrid approach, keeping latency-sensitive parts of the workflow closer to the operators, while using cloud in other parts of the pipeline,” said Mailhot.

The implication is that hybrid is not a fallback when cloud cannot meet performance requirements. It is the architecture that allows broadcasters to choose, function by function, where each piece of the workflow should run.

Advertisement

The legacy argument

A third pressure keeps hybrid in place: existing investment.

Most broadcasters carry SDI infrastructure, control rooms, routing and acquisition equipment that has years of useful life remaining.

“Hybrid architectures are the connective tissue that allow organizations to extend the value of their existing on-premises investments while unlocking the flexibility of cloud-based tools. In practice, they create a seamless bridge between physical infrastructure such as control rooms, routing, and acquisition systems and cloud environments used for processing, collaboration, and distribution,” said Ryan Durland, cloud engineering at Diversified.

That bridging role makes hybrid a practical answer to the question of how to modernize without writing down working hardware. Chris Pulis, CTO at Globecast, described hybrid as supporting phased deployment while preserving existing investments.

The same logic applies on the cost side. Capital that has already been depreciated tends to look cheaper than equivalent cloud capacity in steady-state operation.

“Hybrid workflows are more effective at addressing steady-state, always-on requirements, where depreciable capital investment provides a predictable cost of ownership and generally lowering operating costs,” said Ian McPherson, head of business development at TMT Insights.

What it means for operations

The reframing of hybrid as a permanent state changes the work required to run broadcast operations. If the goal is no longer to migrate fully, the focus shifts to making mixed environments behave as one system.

“The real value comes when those different environments can be run as one operational system rather than as a patchwork of exceptions,” said Selva.

That places weight on orchestration, monitoring and the operational layer that sits above any individual deployment model. It also affects how vendors design products. Several participants described re-architecting their offerings so the same software runs across on-premises, hybrid and cloud environments with consistent operational interfaces.

For McPherson, the practical effect is that companies are making location-specific decisions rather than category-wide ones.

Advertisement

“Instead of viewing the cloud as the default for everything, companies are looking at creating hybrid models that optimize cost based on latency, availability, and criticality of data,” said McPherson.

What the shift does not say

The consensus on hybrid does not amount to skepticism about cloud. Many of the same participants who described hybrid as permanent also described cloud workflows as central to remote production, scaling, AI deployment and content distribution.

What has changed is the framing. Hybrid is no longer described as a compromise that broadcasters tolerate until cloud capabilities mature. It is described as the architecture that lets each function run in the environment that best suits it.

Whether that consensus holds five years from now depends on factors the roundtable participants identified separately: cost trajectories for cloud services, advances in low-latency processing, the maturity of orchestration tools and the willingness of broadcasters to retire depreciated infrastructure. For now, the language has settled.

Hybrid is not the way to the cloud. It is where the industry has chosen to live.