Nevion VideoIPath API enables custom driver development for broadcast equipment

This move signals a shift toward greater interoperability in media orchestration by allowing engineers to bypass vendor-specific development timelines for niche hardware. By opening the driver layer, Nevion addresses the bottleneck of multi-vendor broadcast integration that often slows the deployment of hybrid SDI-IP environments. Within the broader streaming ecosystem, this reflects a growing demand for vendor-agnostic control planes that can adapt to bespoke hardware configurations without waiting for official firmware updates. Watch for the IBC2026 Future Tech Ignite Stage demonstration at IBC 2026 to see how this API handles real-world multi-vendor synchronization.

Nevion's parent company Sony has been pushing VideoIPath as a central orchestration layer for hybrid broadcast-IP environments. In June 2026, Ericsson launched its AI in RAN commercial software subscription claiming up to 20% higher downlink throughput across more than 15 live deployments, signaling that network automation vendors are racing to open their platforms to third-party integration. While that announcement targets telecom RAN rather than media transport, it reflects the same architectural pressure driving Nevion's External Driver API: operators and broadcasters want to avoid being locked into a single vendor's device-support roadmap. The AMWA's BCP-008 work on multi-vendor orchestration interoperability, which Nevion has been contributing to, is expected to be demonstrated at IBC 2026 in September.

Nokia's parallel moves in the telecom orchestration space illustrate how vendors across adjacent verticals are converging on agentic, API-driven control planes. Nokia announced partnerships with AWS and Databricks to build a unified data and cloud control layer for autonomous networks, positioning its Autonomous Network Fabric as a substrate-agnostic orchestration layer that consumes data, applies models, and triggers actions across domains. The company reported that operators using its autonomous networks portfolio are achieving automation rates above 90 percent, service delivery times under four hours, and up to 85 percent reduction in slice rollout time. These figures underscore the commercial case for open orchestration APIs: when the control plane can integrate heterogeneous equipment without bespoke engineering, broadcasters lose 75% of production time to manual technical tasks, making operational costs drop measurably.

On the technical side, the divergence between Ericsson and Nokia on AI-RAN architecture highlights why open driver interfaces matter for multi-vendor environments. Ericsson and Nokia are diverging on how Layer 1 RAN functions are distributed between GPUs and CPUs, with Nokia running all L1 functions on Nvidia GPUs via CUDA while Ericsson confines only the FEC function to the GPU. This kind of hardware-level fragmentation is precisely the scenario Nevion's External Driver API is designed to address in the media domain: when equipment vendors adopt different processing architectures, the orchestration layer must abstract those differences through programmable interfaces rather than hard-coded integrations. , noting that uplink traffic could triple over the next five years driven by AI glasses, sensors, and real-time video, a trend that increases the complexity of media transport networks and the need for flexible orchestration. As industry focus shifts toward , these open APIs become critical for maintaining operational agility.