“Video wall controller” names two different things that are bought in two different ways. One is a dedicated hardware processor: a chassis with capture cards in and display cards out. The other is software on an ordinary server, where the GPU does the scaling and the layout is a configuration file. The decision matters more than the model choice inside each camp, because it sets what an upgrade costs three years from now.
Hardware controller vs software controller
| Hardware processor | Software on a server | |
|---|---|---|
| Layout change | Within the card’s output count | A setting |
| Adding displays | New card or a bigger chassis | More GPU outputs |
| HDMI / DP sources | Native, low latency | Needs capture cards |
| IP sources (RTSP, NDI, web) | Often an add-on licence | Native, scales with GPU |
| Spare parts | Vendor-specific, EOL risk | Commodity server parts |
| Entry cost | From roughly €5,000 | Licence plus a server you may own |
The honest case for hardware is latency-critical cabled work — a control desk where every source is a physical output a few metres away, and a frame of delay matters. The honest case for software is everything driven by IP: camera walls, dashboards, browser content, remote sources.
What 2x2, 3x3 and 4x4 actually require
A 2x2 wall needs four video outputs, a 3x3 needs nine, a 4x4 needs sixteen. With a hardware controller that number is a purchasing decision: the model you buy has a fixed output count, and outgrowing it means replacing the box. With a software controller the same server drives whatever its GPUs can output — there is no licence tier that caps the display count, only the hardware you put in the chassis and the resolution you drive.
This is where most budget surprises come from. A 2x2 quote and a 3x3 quote look similar on the software side and diverge sharply on the hardware side, because the second one crosses into a different chassis class.
Counting sources honestly
Count your sources by transport before you compare anything. Physical inputs — laptops at the desk, an operator console, a legacy DVR with only HDMI out — need capture, and capture costs the same whichever camp you are in. IP sources are where the two diverge: an RTSP camera, an NDI feed, a Grafana dashboard cost nothing to add on a software wall beyond decode headroom, while on many hardware platforms each stream class is a licensed option.
Writing it into a specification
Split the purchase into separate line items — software licence, server, panels — rather than one bundled box. The items usually fall under different procurement categories anyway, and separate lines keep the licence portable when the hardware is refreshed. Specify capability, not a model: number of outputs and their resolution, source types and counts, operator roles and audit requirements, operating system, and whether the deployment must run air-gapped.
Where Craft Wall sits
Craft Wall is the software half: a GPU-accelerated wall on commodity Linux, with a perpetual licence rather than a per-display subscription. Layouts, sources and operator roles are configuration; the display count is bounded by the GPUs and video outputs in the server you choose. See pricing for the licence and pre-built server options, or the five-year TCO comparison for how the two approaches diverge over time.