By Ian Wagdin, VP technology & innovation at Appear.

Ask ten media executives what their companies do and you’ll hear the same familiar labels: broadcaster, streamer, platform, rights holder. But look more closely and the way they operate tells a different story. The industry now behaves far beyond those historical identities; at its core, it has become a media business.

Convergence is accelerating – if a streamer can spin up pop-up channels for a tournament in a matter of weeks, the broadcaster working on an 18-month transformation plan is already on the back foot. And if a league can stand up its own production hub and direct-to-consumer app, the host broadcaster is no longer the default partner. Meanwhile, platforms that combine advertising reach with deep audience data continue to challenge wholesale rights models.

The organisations that will lead are the ones shifting fastest, from fixed pipelines and annual capex cycles to orchestrated services that scale on demand.

Hybrid stacks make identity obsolete

Beneath the surface, most media organisations are now assembling remarkably similar technical architectures, even if many continue to draw rigid distinctions between their ‘broadcast’ and ‘digital’ teams – a separation that is already putting them behind the curve.

Live events increasingly travel through IP gateways and contribution paths, while origin, packaging and DRM workflows run in clustered services. Distribution stretches across CDNs, social platforms and affiliates, with data threaded through every stage. In this landscape, hybrid architectures are the operational default. Latency-critical functions will always sit close to the lenses, yet tasks such as highlight creation, audio sweetening, compliance and localisation are far better suited to elastic compute.

Open standards for timing, identity, metadata and control are what will make it possible for live and file-based, synchronous and asynchronous processes to coexist within a single fabric. That unified approach is what enables a replay system to drive both a director’s view and an automated clipping service simultaneously, or to generate multiple derivative outputs without losing sync, context or rights integrity.

Ultimately, the only meaningful distinction that remains is between deterministic live services and everything else that can be executed as jobs across a compute grid.

Derivative feeds as the real product

In this environment, the main program feed is the base ingredient. Once an event is modelled as time aligned video, audio and data, everything else becomes a derivative:

• Language and graphics variations for different regions
• Betting and watch-along feeds with altered delays
• Vertical highlights and social cuts optimised for mobile
• Clean and dirty feeds for partners and rights holders
• Tactical views and data overlays for teams and analysts.

The challenge is not whether these derivates can be created, but whether they can be produced consistently at scale and with governance around rights, brand and safety. That’s where open timing and metadata models matter. Without them, every new derivative is a bespoke integration; with them, derivatives become policies executed by orchestrated services.

From fixed pipelines to orchestrated services

Traditional broadcast is defined by fixed chains: a control room with set inputs and outputs, a MAM with a fixed set of transcode nodes, scaling achieved by adding hardware. Video companies operate differently – production and distribution are treated as modular, event-driven services.

Are extra ISO records needed for a tournament weekend, an additional language feed, or a betting-specific output with a different delay budget? The goal isn’t to own that capacity permanently, it’s to orchestrate it for a defined window and to then release it afterwards.

This shift demands new engineering practice for orchestration and observability, not just stability. Production teams must accept that the ‘gallery’ is now a logical construct spanning buildings and cloud regions.

Governance, observability and the unglamorous essentials

As workflows become composed on demand, informal safety nets disappear. Knowing that a specific studio router is unreliable is irrelevant if the live signal is being switched in a cloud region thousands of kilometres away. Media companies need governance that looks much closer to modern software operations:

• End to end observability that covers contribution, processing, distribution and entitlement
• Clear runbooks and incident response ownership across internal teams and external partners
• Self-healing systems that invisibly fix any issues but report them for later analysis
• Formal change management for workflows that are assembled dynamically, not wired once and forgotten
• Security policies that treat video, control and data planes as one problem.

This is not optional hygiene; it is the difference between a slick multi-platform service and a headline about a blackout.

Openness or islands

Many industry solutions still encourage proprietary islands: a glass cockpit that only speaks to its own stack, a control layer that hides proprietary behaviour behind standard protocols, or an interface that claims openness while limiting real interchangeability. These approaches only work when a single organisation controls the entire chain. In reality, where broadcasters, streamers, rights holders and platforms must interoperate every week, they simply create friction.

Sport and live events are inherently messy. Production duties shift between partners, archive and fast-turn editing often live in different environments, and no single technology stack can cover everything end to end.

Open standards, well-documented APIs and reference implementations are not ideology, they are how the industry avoids spending budgets on integration, glue code and preventable outages.

In 2026, identity is marketing, agility is strategy.

So, what does all this mean for the next two years?

• Be clear about what you are. If you take live signals, transform them, add data, distribute them across screens and monetise attention, you’re a media company.
• Design for capabilities not historic labels. A public service broadcaster, a global streamer and a national league all need the same core capabilities: hybrid live and compute, orchestrated services, deep observability, secure distribution and data-fluent operations.
• Build for spin-up and spin-down. The advantage will go to organisations that can launch new workflows in weeks, adapt them mid-season and retire them without technical debt.
• Treat openness as a commercial flexibility, not a compliance exercise. The more systems which can interoperate, the more options you retain as rights, partners and models evolve.

The old categories are fading as the media industry evolves. What matters most today is the ability to turn live events into programmable, data-rich products that can be created, adapted and monetised at will.

In 2026, the winners won’t be broadcasters, streamers or rights holders – they will be media companies built to move.