Ubiquiti
Broad, inexpensive networking and wireless that belongs on the production side of the line, not in the show-critical control path.
What it is
Ubiquiti builds general-purpose networking: switches, gateways and access points managed from a central controller application that provisions every adopted device from one configuration. It is inexpensive relative to its capability, extremely widely deployed, and the wireless is genuinely good for the money, which is why it turns up on production sites constantly for offices, crew Wi-Fi, backhaul, IP cameras and building infrastructure. It is not built for show-critical control paths. There are no entertainment protocol profiles, no saved-state recall aimed at a touring crew, connector retention and power redundancy are not the norm across the range, and the support and firmware cadence follow a prosumer model rather than a show calendar. Multicast handling exists, but it is something you configure and verify deliberately rather than an assumed default.
How we work with it
The first job is drawing the line between show-critical traffic and everything else, and then putting this gear firmly on the right side of it. Where it carries production traffic we use it enthusiastically, because the price and the wireless are hard to beat. Where a client insists it also carry control data, we treat that as an engineering exception with conditions attached: verify multicast handling rather than assume it, confirm querier behavior against everything else on the segment, disable automatic firmware updates, freeze versions before load-in, and establish that no configuration push happens during show hours. We survey wireless in the actual room under actual RF conditions, not an empty venue, and we say plainly in writing what the residual risk is.
Strong value and a mature controller for offices, crew Wi-Fi, backhaul, cameras and general site connectivity.
Central provisioning is a strength for a fleet and a liability mid-show, since changes are applied by reprovisioning.
No entertainment protocol profiles; multicast for sACN or Art-Net must be configured and verified by hand.
Support and firmware cadence follow a prosumer model, and the range is not built around show hardware norms.
Right when
- The traffic is not show-critical: production office, crew Wi-Fi, IP cameras, signage, general site connectivity.
- You need wireless coverage across a large site at a price no entertainment-specific vendor is going to match.
- Someone will own the controller long-term, because the fleet management model pays off over months, not over one load-in.
Look elsewhere when
- It would carry sACN, Art-Net, PosiStageNet or any control path an audience depends on. Configuration changes are applied by reprovisioning the device, automatic firmware updates are a software setting rather than a physical lock-out, and the multicast behavior you need is something you have to build and prove rather than inherit. A network where any routine change is a fleet-wide event is the wrong place for a path that must not blink, and that is a fit problem, not a quality problem.
- Performer tracking, or any other latency- and determinism-sensitive path, over its wireless. Wi-Fi in a full venue is a contested medium sharing spectrum with comms, press, and several thousand phones, and no vendor's access point fixes that. If the data has to arrive on time every time, run it wired and use the wireless for things that can tolerate a retry.
Can we run sACN over UniFi if we configure it carefully?
Technically yes, at modest universe counts, with multicast handling verified under load and firmware frozen. The reason we still argue against it is not throughput. It is change management: the operating model assumes a controller pushing configuration to a fleet, and a network carrying cues needs changes to be rare, local and deliberate. If you accept it anyway, accept it in writing with the conditions attached.
Is this a criticism of the hardware?
No. It is a fit judgment. The same qualities that make this gear a good buy for a production office, a site-wide wireless fabric or a camera network are the ones that make it a poor fit for a control path: broad general-purpose defaults, centralized fleet provisioning, and a consumer-paced release cycle. Used where those qualities are strengths, it is often the correct and obvious choice.