If you're running a security operation of any real size, you're almost certainly running a mix. Different camera brands from different years, an encoder or two keeping older analog units on the network, a couple of sensors that came in with a separate project. A system that grew the way most systems actually grow, one purchase at a time. And when a team starts looking at a new video management system, the first question is almost always the same: will all of this still work?
The Short Answer
With Nx Witness, it will. The platform works with more than 26,000 devices from more than 1,300 manufacturers, and anything that conforms to ONVIF (Open Network Video Interface Forum) Profile S or RTSP (Real Time Streaming Protocol) can connect whether the specific model is listed by name or not. That covers most IP cameras made in the last decade. The question is rarely whether a device will connect. It's how well it connects, and what features carry over.
What Does “Supported” Actually Mean?
A device on the Nx Witness supported list has been seen running on enough live systems to confirm it connects reliably, and the list records the capabilities those devices reported: PTZ controls, dual streams, motion detection, and any onboard analytics that expose metadata. That list currently covers more than 26,000 devices from more than 1,300 manufacturers, and it's generated automatically from real-world usage across active Nx Witness systems rather than assembled from a manual test lab. When a device shows up on enough live systems and behaves consistently, it lands on the list. Treat it as a strong starting point rather than a guarantee, and confirm any capability you're relying on with the manufacturer and test in Nx.
A device that isn't on the list isn't necessarily unsupported. Usually it's just too old, too new, or hasn't hit enough active systems yet to be picked up. Those cameras can still connect through ONVIF Profile S (streaming) or RTSP, the open standards most modern IP cameras conform to, with video streams and basic controls coming through in most cases. If nothing else works, the RTSP stream is almost always available as a fallback to pull video off the device.
The full searchable list lives at nxvms.com/ipvd.
Why Does a Mixed Fleet Matter?
Organizations rarely replace every camera at once. Budget cycles, building projects, and grant funding all move on different timelines, so a site ends up with cameras from three or four brands and two or three generations, all producing footage that needs to end up in the same place. A video management system that only works with one manufacturer's hardware forces a choice nobody wants to make: replace everything, or accept that half the fleet won't show up in the new interface.
Nx Witness takes that choice off the table. The cameras already in place stay in place, whatever gets added next year can be whatever fits the budget and the site, and the software running above them works across the entire mix.
What About Everything That Isn't a Camera?
The same approach applies to the rest of the stack. Nx Witness connects to access control panels, environmental sensors, panic buttons, I/O modules, and third-party analytics through documented APIs, event rules, and the SDK layer for anything that needs a deeper hook. A door alert can trigger a camera view. A vape sensor can pull up the hallway feed. A temperature sensor can bookmark video when it crosses a threshold. The video system becomes the layer that ties the rest of the safety and operations stack together instead of sitting apart from it.
Curious if your hardware is on the list? Check the full database at nxvms.com/ipvd, then get in touch to talk through how Nx Witness fits your deployment.

