Law Enforcement, from a Report to a Route

From a report to a route, in one tool. Police work with the cameras a city already has, most of which nobody is watching: IREX makes that estate searchable, alerts officers to what matters, and records the reason for every look.

In Production

Southern California, Peru, Kazakhstan

In Southern California, including Oceanside and El Cajon, police departments run IREX for traffic congestion and incidents, weapons in public spaces, registered-offender and loitering monitoring near sensitive locations, and real-time suspect matching through integration with local law-enforcement databases.

In Peru, the National Police and municipal forces including Lima and Miraflores use IREX as the backbone of public-safety operations, unifying thousands of cameras into a centralized command infrastructure. Key modules are facial recognition, traffic analytics with two-wheeler detection critical to the region, and weapon detection, with national and local agencies collaborating in real time through shared dashboards and secure messaging.

In Kazakhstan, the full analytics module catalog runs inside the national smart-city program as the central intelligence layer for public safety and law enforcement.

Capability

What Officers and Analysts Use

Watchlist Monitoring

Suspects, registered offenders, and missing persons matched in real time across every connected camera, with a Case ID on every search.

See Ethical Facial Recognition

Weapon Detection

A firearm shown in a public space, and the gunshot, scream or breaking glass that goes with it, routed to officers in seconds with the frame attached.

See Weapon & Gunshot Detection

Vehicle Intelligence

Plates plus make, model, color and type, checked against stolen, uninsured and unregistered databases in real time.

See License Plate Recognition

Investigations

Search the archive by map, filter or plain language, then follow the subject camera to camera in both directions in time.

See Ask IREX & Video Search

Field Coordination

Encrypted messaging, evidence upload, and natural-language queries from the phone an officer already carries.

See Sover Communications

Accountability

Case ID before every privacy-sensitive action, non-erasable logging, and daily signed exports open to oversight bodies.

See Ethical AI & Case ID

The Bargain

Why Communities Accept This Deployment

  • The platform recognizes only pre-registered people and vehicles. It cannot identify or track random individuals in public spaces.
  • Every high-risk action requires a recorded lawful basis: a case file, a court order, a missing-person report.
  • The audit trail is open: append-only, tamper-evident, exported daily, with read access designed for supervisors and independent oversight bodies.
  • Bias is measured and disclosed. IREX participates in the NIST Face Recognition Vendor Test and ran a company study in 2024 to estimate bias in suspect recognition.
  • Compliance auditing runs over analytics usage itself, so misuse surfaces in the data rather than in a complaint.

FAQ

Can we integrate our records and watchlist databases?

Yes. Integration endpoints for wanted-persons, stolen-vehicle, vehicle-registration and civil-registry systems are agreed during the design phase, with the customer providing timely access. That integration is what makes real-time suspect and vehicle matching possible.

Is IREX CJIS compliant?

IREX supports all 13 CJIS policy areas, and that is an alignment and compliance-support claim rather than a third-party certification. Encryption, role-based access, and daily signed audit exports are built in.

Will this survive a public-records or oversight challenge?

It is designed for exactly that. Every query, view and alert carries operator identity, timestamp and Case ID in an append-only log, and read access for supervisors and independent oversight bodies is a design goal rather than an afterthought.

Do we have to replace our cameras?

No. Reusing the existing fleet is the standard deployment model: any camera that supports ONVIF or streams RTSP with H.264 or H.265 on a static IP can be connected, and each module then sets its own resolution and placement requirements, which a site survey confirms. Note that connection is not plug-and-play: a qualified network engineer configures each camera and router.

Who owns the data?

You do. Customers retain 100% ownership and control of their data, and IREX neither owns nor accesses customer video, events, logs, watchlists, or floor plans. On-premises deployment is the data-residency mechanism.

How do we start?

With a pilot: one site, three to five use cases, six to twelve weeks, and two or three measurable success criteria agreed in writing before it begins. Accuracy is benchmarked on your own cameras, and the measured numbers go into the contract.

Re-Run a Case You Already Closed

It is the fastest honest test: same footage, same question, and a stopwatch.