Riedel Communications
Riedel competes across three segments: distributed fiber routing, SDI-to-IP gateways, and IP-native orchestration. The differentiator is the fiber backbone — truly distributed systems without frame size limitations.
Growth Opportunities
Riedel's distributed architecture is a competitive advantage in multisite and touring scenarios, but represents a positioning challenge in RFPs expecting centralized, single-frame SDI routers. Control ecosystem maturity (SDNsquare + hi human interface) and audio channel-level routing are near-term focus areas.
Product Comparison Matrix
Select a Riedel product and scenario filters to see how it compares against competitors across 10 key dimensions.
⬤ Sales Strategy vs. Incumbent
SDI Routing Landscape
Head-to-Head: Riedel vs. Centralized SDI Routers
Hybrid SDI/IP Routing
Head-to-Head: Riedel HorizoN vs. Competing Gateways
IP-Native & ST 2110 Routing
Head-to-Head: Riedel vs. IP-Native Platforms
Control & Orchestration: The Ecosystem Strategy
Breaking vendor lock-in through vendor-agnostic orchestration and intuitive human interfaces.
The Historical Integrator Hurdle
MediorNet's distributed fiber architecture has always been technically superior for multi-site, scalable routing — but hardware specs alone don't win RFPs. Incumbent vendors like Evertz (MAGNUM-OS), Grass Valley (GV Orbit), and EVS (Cerebrum) maintain their grip on facilities not through better signal paths, but through proprietary control ecosystems that operators depend on daily. Integrators historically hesitated to spec Riedel as a core router replacement because it meant forcing clients into massive operator retraining, expensive third-party API middleware, or — worst case — running two completely separate control surfaces. The switching cost wasn't the router. It was the control layer.
The Missing Links — Acquired
SDNsquare
Acquired to solve the single hardest problem in ST 2110 deployments: real-time IP network orchestration. SDNsquare handles bandwidth reservation, PTP domain management, multicast flow control, and spine-leaf network awareness — abstracting the raw complexity of IP video infrastructure into a managed, predictable routing fabric.
For integrators, this eliminates the "you need a network PhD" objection. SDNsquare takes the IT headache out of IP video and gives broadcast engineers the deterministic behavior they expect from baseband — but over standard IT switches.
hi (human interface)
A browser-based, auto-discovering, platform-independent control layer already field-proven with MediorNet at UEFA Euro 2024 (WDR remote production) — before the acquisition closed. hi controls 3rd-party routers, multiviewers, and any compliant device on the network — Riedel, Evertz, Grass Valley, Lawo — presenting operators with a unified, drag-and-drop canvas. No proprietary clients, no per-seat licenses, no Windows dependencies. This is a massive RFP differentiator today, not a future roadmap item.
Control Layer — Competitive Landscape
| Capability | Riedel hi | Evertz MAGNUM-OS | EVS Cerebrum | Lawo VSM |
|---|---|---|---|---|
| Vendor-Agnostic | Yes — open platform | Evertz-centric | Multi-vendor | Multi-vendor |
| Browser-Based UI | Yes — zero install | Windows client | Windows client | Web-based |
| Auto-Discovery | NMOS + NDI + Dante + AMPP | Evertz devices only | Manual config | NMOS |
| Per-Seat Licensing | No | Yes | Yes | Yes |
| Dedicated Hardware Panels | hiPush + hiDot + SmartPanels | Evertz panels | Third-party panels | Lawo ruby / sapphire |
| Proven Scale | 300+ installs · UEFA Euro 2024 | Large broadcast | Large broadcast | Large broadcast |
Riedel no longer has to win a hardware bake-off to get into a facility. By deploying hi as a vendor-agnostic control upgrade over a client's existing third-party infrastructure, Riedel captures the operator experience. Once the control layer is unified and operators are working in hi daily, expanding the facility with Riedel HorizoN or MicroN nodes becomes the path of least resistance.
"Control drives the hardware refresh. Win the operator's screen, and the routing infrastructure follows."
Verticals & Use Cases
Sources & References
All claims sourced from manufacturer datasheets, product pages, and published specifications.Riedel Competitive Intelligence Platform
Why this exists
The question came up: what does the routing landscape actually look like for Riedel? Not as a slide deck or a PDF, but as something you can interact with — filter by vertical, select an incumbent, compare dimensions side by side, and see where the real opportunities are.
I built this to give that question a proper answer. Thirteen vendors, ten scoring dimensions, eight verticals, incumbent migration paths — all in one place, all backed by published specs and datasheets.
The goal is simple: create a shared starting point for a healthy conversation about what comes next. Not to prescribe a conclusion, but to make sure we're all looking at the same data when we get there.