Back to Insights
Blog

Hybrid Broadcast Demands Stronger Partnerships

Tom Erik HagenVP of Strategic Alliances9 min read
Hybrid broadcast

Hybrid broadcast now spans IP, hardware, software, and cloud — which is why partnerships, not single vendors, decide what works.

Key takeaways
Key terms

The media industry used to make technology investments around relatively well-defined, static infrastructure. They purchased equipment, installed it in their facilities, and built workflows around the capabilities of those systems. Manufacturers were responsible for their products, while systems integrators brought everything together.

Hybrid broadcast production has changed that relationship. Today’s workflows extend across a wider range of specifications, IP transport, dedicated hardware, elastic software, and cloud infrastructure. Broadcasters increasingly expect these technologies to operate as one environment, even when the individual components come from different suppliers.

What customers are buying has changed. Instead of simply purchasing equipment, broadcasters are investing in operational outcomes, and they expect their technology partners to help deliver them. For manufacturers, this makes collaboration an essential part of how we develop technology and support our customers.

Specialisation makes the whole stronger

No manufacturer can realistically excel at every element of an increasingly complex workflow in today’s hybrid broadcast landscape. Trying to develop every capability internally risks spreading engineering resources too thin while slowing the introduction of technologies customers need.

At Appear, we approach partnerships by first understanding where our expertise delivers the greatest value towards the customer’s desired outcome. Our core competencies remain mission-critical contribution and distribution, with particular emphasis on density, resilience, and performance. Those are capabilities we develop and control ourselves.

For adjacent technologies, we look for partners whose expertise complements our own. This allows each company to concentrate on what it does best while jointly delivering more complete workflows. Working with established specialists can also accelerate time to market, expand the applications our technology supports, and give customers access to proven capabilities without waiting for or relying on one manufacturer to build everything.

Our work with companies such as Grass Valley demonstrates how collaboration can support broader production requirements as our VX portfolio evolves. The objective is to focus on and establish relationships that deliver practical operational benefits.

What Appear builds vs. what partners provide

Core competencies (built and controlled by Appear)

  • Mission-critical contribution and distribution
  • Particular emphasis on density, resilience, and performance

Adjacent technologies (delivered with partners)

  • Capabilities that complement Appear’s own, such as the work with Grass Valley as the VX portfolio evolves
  • Faster time to market, a wider range of supported applications, and proven capabilities without waiting on one manufacturer to build everything

Interoperability must come first

Partnerships only create value when the underlying technologies work together reliably.

Media technology is evolving fast, as it always has. Legacy, traditional transport streams and SDI are mature, while ST 2110 is still advancing through a period of interoperability development.

Initiatives such as the Dynamic Media Facility (DMF) and Media eXchange Layer (MXL) promise to extend that flexibility into increasingly software-defined environments and are therefore fundamental to the hybrid broadcast evolution. However, interoperability requires sustained engineering investment, testing, and collaboration between manufacturers.

Appear has always placed considerable emphasis on open standards and interoperability. We deliberately avoid proprietary architectures that restrict customers to one manufacturer’s technology. Open APIs and standards-based interfaces allow broadcasters to select the capabilities that best serve their operations.

This philosophy also shapes our partnership strategy. We look for companies that share a commitment to openness, interoperability, and customer support. As newer standards mature, manufacturers must work together to resolve implementation challenges before those challenges become problems for customers.

Flexibility extends beyond technology

Technical interoperability represents only part of the hybrid broadcast challenge. Commercial models must also work together. Consider a broadcaster supporting a major sporting event. Its permanent contribution infrastructure may represent a capital investment, while additional processing capacity is purchased through temporary software licences or consumption-based cloud services.

This combination makes operational sense. Broadcasters can own the infrastructure supporting their baseline requirements while renting additional capacity during peak demand.

However, combining capital expenditure, subscriptions, and consumption-based pricing across multiple vendors introduces financial complexity. One supplier might bill monthly, another hourly, and another through perpetual licensing. For procurement and financial operations teams, these differences can make costs difficult to predict and manage.

Successful partnerships must therefore address commercial alignment alongside technical integration. Manufacturers need sufficient licensing and deployment flexibility to accommodate different customer requirements without introducing unnecessary purchasing complexity. That flexibility is increasingly important as broadcasters balance permanent infrastructure with temporary resources across different event tiers.

Commercial models across a hybrid broadcast deployment

Commercial model Example Best suited to
Capital expenditure Permanent contribution infrastructure, owned outright Baseline requirements that run all the time
Subscription / software licensing Temporary software licences for additional processing capacity Planned peaks, such as a major sporting event
Consumption-based Cloud services billed by usage Unpredictable or occasional demand across event tiers

Common misconceptions about technology partnerships

Myth: a single manufacturer can, or should, build every capability internally.
Fact: trying to develop everything in-house risks spreading engineering resources too thin and slows the introduction of technologies customers actually need. Specialisation, backed by partnerships, delivers more complete workflows.

Myth: technical interoperability alone solves the hybrid integration challenge.
Fact: commercial models — capital expenditure, subscriptions, consumption-based pricing — must also align across vendors, or costs become difficult for procurement and finance teams to predict and manage.

Myth: the lowest purchase price is the best measure of value.
Fact: the initial purchase price tells only part of the story. Integration effort, testing, operational support, and the risk of delays all influence the real total cost of ownership.

Reducing risk before going on air

Perhaps the greatest customer benefit of effective partnerships is the ability to reduce integration risk. When broadcasters assemble technologies from multiple manufacturers independently, they often assume responsibility for proving interoperability, troubleshooting problems, and coordinating support. Those activities consume engineering resources and can delay deployment.

Much of that responsibility moves upstream when manufacturers collaborate earlier in the process. Joint testing, validated integrations, and clearly established support relationships can reduce the time and uncertainty involved in bringing a workflow into operation.

This also changes how customers should evaluate total cost of ownership. The initial purchase price tells only part of the story. Integration effort, testing, operational support, and the risk of delays all influence the real cost of deploying and maintaining a system.

Systems integrators remain essential, particularly for large-scale broadcast production operations. Strong manufacturer partnerships make their work easier by providing tested technology relationships rather than leaving every integration to be developed from scratch.

Importantly, partnerships should also preserve customer choice. A broadcaster must retain the freedom to replace individual components as its requirements evolve, rather than becoming dependent on a closed combination of suppliers.

Partnerships built around the customer

The most successful partnerships begin with a shared philosophy rather than a commercial agreement. We look for manufacturers that value open interfaces, maintain a strong support culture, and accept joint responsibility for helping customers succeed. Technical compatibility matters, but so does the willingness to work together when something goes wrong.

That commitment becomes especially important in live production, where troubleshooting cannot become an exercise in determining which supplier owns the problem. Hybrid broadcast workflows will continue to evolve as IP, software-defined processing, and cloud technologies mature. No single manufacturer will define that evolution alone.

The companies that succeed will be those that combine specialist expertise, open technology, and commercial flexibility around the needs of their customers. Ultimately, the value of a partnership is measured by how confidently broadcasters can bring their workflows on air and keep them running reliably.

Rules of thumb for evaluating technology partnerships

  1. Specialise in what you do best, and partner for the rest rather than building every capability in-house.
  2. Insist on open APIs and standards-based interfaces — avoid proprietary architectures that lock customers to one manufacturer.
  3. Align commercial models — capex, subscription, consumption-based — as deliberately as technical integration.
  4. Push joint testing and validated integrations upstream, before deployment, not into troubleshooting once you’re on air.
  5. Preserve customer choice — a partnership should never harden into a closed combination of suppliers.

Solution brief
One REMI workflow, every event

How to deliver low-latency, resilient contribution across managed and unmanaged networks—while reducing on-site infrastructure.

Download the brief
Remote Production solution brief cover
About the author
Tom Erik HagenVP of Strategic Alliances

Tom Erik Hagen bringins more than two decades of experience in developing broadcast and live production technology. His career at Appear spans hardware design, software development, R&D leadership and product management, giving him a broad understanding of how to take products from concept to market. With expertise in professional video encoding and decoding, Tom Erik combines engineering knowledge with a strong customer focus, helping shape integrated solutions and technology partnerships that support efficient, scalable live production.