Live video gateway

Hardware vs software video gateway

The choice between a hardware video gateway and a software video gateway is one of the most consequential infrastructure decisions a broadcast facility makes. It affects capital expenditure, operational flexibility, channel scalability, and the total cost of ownership of the broadcast signal chain for years.

Both approaches convert video signals between protocols and formats in real time, and both serve the same fundamental function in the broadcast workflow. The differences are in architecture: how they are built, how they scale, what they cost, and what they can do beyond basic conversion.

This guide sets out the practical operational differences between hardware and software video gateways in plain terms, so broadcast engineers and technical decision-makers can make an informed choice based on their specific requirements.

What is a hardware video gateway

A hardware video gateway is a dedicated physical appliance, typically a rack-mounted server or compact encoder/decoder unit, purpose-built to perform specific protocol conversions on fixed hardware.

Hardware gateways are designed around a fixed set of inputs and outputs. An SDI to SRT hardware encoder accepts SDI input and outputs SRT. An NDI to SDI decoder accepts NDI and outputs SDI. The conversion path is defined by the hardware design. It can be configured within limits, but it is fundamentally fixed by the physical architecture.

Hardware gateway characteristics:

Fixed channel count

Hardware gateways handle a defined number of channels, determined by the hardware design and licence. Expanding beyond this channel count requires purchasing additional hardware units.

Dedicated physical infrastructure

Each hardware gateway occupies rack space, consumes power, requires cooling, and needs physical maintenance. A facility with 20 conversion paths needs 20 hardware units, or multi-channel appliances with their own fixed channel ceilings.

Purpose-specific design

Hardware gateways are optimised for their specific conversion task. An SDI to SRT encoder is purpose-built for that conversion and is not easily repurposed for a different conversion path.

Certified hardware reliability

Dedicated hardware provides a defined, tested, and certified performance envelope. For facilities requiring hardware certification for specific broadcast standards, such as ATSC 3.0, specific SDI formats, or precision timing, hardware appliances provide certified compliance.

Enterprise control protocols

Professional hardware gateways typically include enterprise control interfaces, such as REST API, SNMP, and NMOS, enabling integration with broadcast management and monitoring systems.

What is a software video gateway

A software video gateway runs on standard server hardware, optionally GPU-accelerated, and performs protocol conversions through software processing rather than dedicated hardware circuits.

Software gateways are configured in software, which allows flexible combinations of inputs and outputs, multiple simultaneous destinations, and different graphics or processing set-ups. The conversion paths are defined by software configuration rather than hardware design.

Software gateway characteristics:

Flexible channel count

Software gateways scale through additional instances on existing server hardware. Adding channels means running more instances, up to the server's capacity, rather than purchasing additional appliances.

Shared server infrastructure

Multiple software gateway instances run on a single server, sharing GPU and CPU resources. One server can take the place of several hardware appliances across multiple conversion paths.

Reconfigurable conversion paths

Software configuration changes the conversion path without hardware changes. An instance converting NDI to SRT today can be reconfigured to convert ST2110 to RTMP tomorrow, without purchasing new hardware.

GPU-accelerated processing

Software gateways running on GPU hardware process the full video pipeline, including decoding, conversion, encoding, and graphics overlay, on NVIDIA, Intel, or AMD GPU hardware. This gives higher channel density per server than CPU-based approaches.

Additional capabilities included

Software gateways can include capabilities that would require separate hardware in a hardware-only approach, such as live graphics engines, screen capture, ISO recording, and simultaneous output to multiple destinations.

Direct comparison: hardware vs software video gateway

CapabilityHardware gatewaySoftware gateway
Channel countFixed per applianceScales via instances
Expansion costNew hardware per channelAdditional instances on existing server
Conversion flexibilityFixed by hardware designConfigurable input and output combinations
Live graphicsSeparate CG hardware requiredBuilt-in HTML graphics engine
ISO recordingSeparate recorder requiredBuilt-in per-source recording
Multi-destination outputLimited by hardware outputsMultiple, within server capacity
GPU accelerationFixed hardware processingFull GPU pipeline: NVIDIA, Intel, AMD
Enterprise controlREST API, SNMP, NMOS typically includedDepends on platform
Hardware certificationCertified per standardSoftware validation
Physical footprintOne unit per conversion pathMultiple instances on one server
Power consumptionPer unitShared GPU server
MaintenanceHardware replacement cycleSoftware updates
Deployment speedHardware procurement lead timeSoftware installation

When hardware gateways are the right choice

Hardware video gateways are the appropriate choice in specific operational contexts:

Enterprise control protocol requirements

Facilities requiring REST API, SNMP, or NMOS integration with broadcast management and monitoring systems may need hardware gateways that include these interfaces as standard.

Hardware certification requirements

Some broadcast standards and facility specifications require certified hardware for specific signal standards, such as ATSC 3.0 A3SA certification, specific SDI format compliance, or precision timing certification. Hardware appliances provide certified hardware compliance that software running on general-purpose servers does not.

Fixed unchanging conversion requirements

Facilities with permanent, unchanging conversion requirements, such as one SDI input to one NDI output for the long term, may find dedicated hardware appliances simpler to operate than software instances.

Physical signal path requirements

Some broadcast workflows require a physical hardware device in the signal path for reliability or insurance reasons. Hardware provides a tangible, replaceable unit with defined performance characteristics.

When software gateways are the right choice

Software video gateways suit many modern broadcast operations, particularly in these situations:

Flexible and changing conversion requirements

Broadcast operations where conversion requirements change, such as new protocols, sources, destinations, or channels, benefit from software flexibility. Reconfiguring a software instance takes minutes, while purchasing new hardware takes weeks and budget approval.

Multi-channel operations requiring scale

Teleports, broadcast facilities, and OB companies handling multiple simultaneous conversion paths benefit significantly from software scalability. Multiple instances on one GPU server can replace multiple hardware appliances, reducing rack space, power consumption, and capital expenditure.

Operations requiring live graphics without separate CG systems

Software gateways with built-in graphics engines, like BridgeWIZ, add live tickers, lower thirds, logos, and custom HTML graphics to any video signal during conversion. Hardware gateways typically require separate CG hardware for this capability.

Operations requiring ISO recording alongside conversion

Software gateways that include built-in ISO recording, like BridgeWIZ, record each source to an independent file at the same time as the live outputs. Hardware gateways typically require separate recorders.

ST2110 mixed-protocol environments

Facilities handling ST2110 alongside NDI, SRT, RTMP, and SDI simultaneously benefit from software gateways that handle these protocols natively in one platform, rather than separate hardware appliances per protocol.

Budget-conscious operations

Software gateways on standard server hardware can have significantly lower total cost of ownership than hardware appliances at scale. One GPU server running multiple BridgeWIZ instances can take the place of several dedicated hardware units at a lower overall cost.

How BridgeWIZ fits this comparison

BridgeWIZ is a software video gateway that runs on standard server hardware with NVIDIA, Intel, or AMD GPU acceleration. It suits broadcast operations that need:

  • Flexible conversion from multiple input protocols to multiple output protocols simultaneously
  • Multi-channel scalability without hardware procurement at every expansion point
  • Live broadcast graphics without a separate CG system
  • ISO recording alongside live streaming and protocol conversion
  • ST2110, NDI, SRT, RTMP, SDI, and UDP in the same platform
  • Multi-instance deployment for teleports, broadcast facilities, OB companies, and TV stations

BridgeWIZ does not include enterprise control protocols (REST API, SNMP, NMOS) in the current version. Facilities with hard requirements for these interfaces should evaluate whether hardware gateways with these interfaces meet their other requirements, or whether API integration can be addressed in a future BridgeWIZ release.

The total cost of ownership difference

The cost comparison between hardware and software video gateways becomes most significant at scale.

A facility requiring 10 simultaneous protocol conversion paths needs either 10 hardware appliances or one GPU server running 10 software instances. Each appliance has its own licence, power supply, rack unit, and maintenance cycle.

The hardware approach carries proportional cost at every expansion point. The software approach carries a much lower incremental cost per additional instance on the same server, limited ultimately by GPU server capacity rather than per-unit hardware cost.

For broadcast operations planning to scale, with more channels, protocols, and destinations, the software gateway model can deliver significantly lower total cost of ownership over a three- to five-year operational horizon.

FAQs

What is the main difference between a hardware and software video gateway?

A hardware video gateway performs fixed conversions on dedicated physical appliances with fixed channel counts. A software video gateway runs on standard server hardware and handles flexible conversion configurations, with multiple instances on one server taking the place of several hardware appliances. Software gateways offer greater flexibility and scalability. Hardware gateways offer certified hardware compliance and enterprise control protocols.

When should a broadcast facility choose a hardware video gateway?

Hardware gateways are appropriate when enterprise control protocols (REST API, SNMP, NMOS) are mandatory, when hardware certification for specific broadcast standards is required, or when fixed, unchanging conversion requirements make dedicated appliances simpler to operate than software instances.

When should a broadcast facility choose a software video gateway?

Software gateways are appropriate for operations with flexible and changing conversion requirements, multi-channel operations requiring scale without proportional hardware cost, operations needing live graphics and ISO recording alongside conversion, and ST2110 mixed-protocol environments requiring multiple protocols in one platform.

Does BridgeWIZ include REST API or SNMP control?

Not in the current version. Facilities with hard requirements for REST API, SNMP, or NMOS integration should factor this into their evaluation. BridgeWIZ provides a clear, intuitive interface for configuration and operation, but does not include these enterprise control interfaces in the current release.

How does GPU acceleration affect the hardware vs software comparison?

GPU acceleration significantly improves the software gateway's performance compared with CPU-based software approaches. It increases channel density per server, reduces CPU overhead, and lets the full video processing pipeline run on GPU hardware. With NVIDIA, Intel, and AMD GPU acceleration, one BridgeWIZ server can handle the workload of multiple hardware appliances at a lower total cost.

Get started

See BridgeWIZ working with your sources

Book a demo and our broadcast engineers will demonstrate BridgeWIZ using your sources, destinations, and channel requirements.