What detection rate do you claim?
None, and deliberately. IREX writing policy forbids "guaranteed detection" or "100%" wording and requires any accuracy claim to cite its basis. The wiki holds no published per-module figure, so the commitment we make is procedural: accuracy is benchmarked on your own cameras during the pilot, against criteria agreed in writing beforehand, and the measured numbers go into the contract.
Can it see a weapon before a shot is fired?
Yes, if the weapon is in view of a camera. That is the difference between visual detection and an acoustic gunshot sensor: the sensor starts the clock at the first shot, while GunTrack reports a weapon that is drawn or carried into view before one. The two are complementary, which is why AudioTrack runs alongside it for the weapon that is fired out of frame.
Why does the same frame get analyzed twice?
Because the two jobs need different things. Finding a candidate has to happen on every frame of every camera continuously, which is only affordable at the resolution the camera streams for analytics. Deciding whether that candidate is a firearm needs detail, not coverage, so the second pass re-reads only the region the first one isolated, at the highest resolution the camera can give. Version 4.38 updated both the detection and the classification models, and weapons further from the camera were where the improvement showed.
Can it tell a toy from a real gun?
It analyzes the context and the detail of the object rather than the outline alone, which is how benign objects such as umbrellas or toys are separated from genuine threats, and that separation is what the verification pass is for. It is not a screening machine and it does not adjudicate legality: it reports a weapon-shaped object where weapons are forbidden, and a person decides what it is. At a large public research university in the United States that is exactly what happened, and the item turned out to be a realistic replica. A detector that stayed silent on realistic replicas would be the worse product.
Can it detect a concealed weapon?
No. This is camera-based visual and acoustic detection, so it sees what a camera can see. Concealed-weapon screening is a different technology class and IREX does not claim it. What the platform can do where a weapon is out of view is detect the conditions around it: StreamVLM™ prompt detectors for people with hands raised or lying on the floor, and AudioTrack for a gunshot, a scream, or breaking glass.
Do we need gunshot sensors on poles?
No. AudioTrack runs on any camera that already has a microphone, so there is no acoustic array to procure, mount, power, or maintain, and no separate sensor network to run alongside the cameras. The audio arrives on the camera stream as AAC, G.711 mu-law, or PCM, and it is optional per channel, so you turn it on where sound is worth listening to and leave the rest of the estate as it is.
How far away can it hear a gunshot, and how often is it right?
IREX publishes no range, accuracy, or latency figure for acoustic detection, and we are not going to invent one for a website. The commitment is the same one the visual detector carries: we measure it on your own cameras during the pilot, against criteria agreed in writing beforehand, and the measured numbers go into the contract. Two things we can say now. Detection works from the microphone in the camera, so coverage follows your camera plan rather than a sensor grid. And it is not recommended in noisy outdoor locations such as underground stations and railway terminals, where constant ambient noise works against the threshold.
Can one camera run weapon detection and gunshot detection together?
Yes, and that is the normal configuration. Several video analytics modules and detectors run on the same camera at the same time, and AudioTrack is a detector, so GunTrack and AudioTrack on one channel is supported. The two then cover each other: a weapon fired out of frame is still a sound that was heard, and a weapon carried in silence is still an object that was seen.
Who gets the alert?
Whoever you nominate. Alerts route to real-time crime centers, 911 and dispatch workflows, and the Sover secure messenger on the phones staff and officers already carry, all with the triggering frame, the camera, the location, and a playback link attached. Each alarm monitor can have a Sover channel of its own with the authorized users in it, so an officer follows the channels that match their duties and mutes the rest.
Where is the detector in production?
In the reference deployments IREX publishes: Southern California law enforcement in Oceanside and El Cajon, where weapons in public spaces sit alongside traffic and watchlist analytics; Dublin Airport, at access points; the Peru National Police and the Lima and Miraflores command centers; and the Kazakhstan national smart-city program, which runs the full module catalog. In 2024 the Texas instance gained GPU nodes serving weapon detection across campuses, malls, and airports in Texas and California.
Does it work with our existing school cameras?
Often. Any camera that supports ONVIF or streams RTSP with H.264 or H.265 can be connected, but weapon detection needs a clear, higher-resolution view of the scene, so the camera requirements and placement both matter, which is what the site survey checks camera by camera.
Does weapon detection need a GPU?
GunTrack runs on CPU, but with limited performance, so IREX strongly recommends a GPU node for weapon detection. The GPU nodes added to the Texas instance in 2024 are what allowed larger networks and better reads at a distance, while CPU inference stays supported for customers whose data centers cannot take GPUs. Most other modules run at full performance on standard CPUs through the proprietary Synet inference framework, and IREX engineering sizes the CPU and GPU mix per deployment against camera count, module mix, and the servers you already own.
Does this run on its own or does someone have to watch it?
It runs on its own and alerts a person. Detections are signals for a human to verify: no response runs autonomously, and the verification and decision are logged against the same Case ID as the detection.