IREX connects to the camera estate you already operate and gives every event a clear destination. The right path depends on who needs it, what must happen next, and how much data the workflow produces.
Start with the Decision
A camera event can reach a person, trigger an action in software, or become part of an analytical record. These are different jobs, so IREX provides three distinct paths instead of treating every integration as a single connection.
Use Sover when an authorized responder needs the alert in a secure conversation. Use the REST API and alarm-monitor webhooks when an individual event must call software or a device. Use Apache Superset when analysts need to query and understand the complete event stream.
The design phase maps each workflow to one of those paths, checks camera and network readiness, and records any custom work before a pilot begins. The public website explains the decision. The documentation carries the implementation detail.
Choose the Delivery Path
Choose by audience and volume. A workflow can use more than one path, but a high-volume monitor should not become a stream of individual webhook calls.
Enable messenger notifications on an alarm monitor and each alarm reaches its dedicated Sover group chat. The message includes the event snapshot, camera and event names, applicable details such as a plate, the location, and a playback link. This is the path for people who need to assess and coordinate a response.
See Sover Communications →Use the REST API to automate platform operations, including lists and alarm monitors. A monitor webhook calls a nominated HTTP endpoint for each matching event, with a selected method and, for POST, event frames in the payload. This fits lower-volume events that must trigger a discrete action or enter a customer-managed workflow.
Docs: Track a Vehicle by API ↗IREX continuously exports events to the platform event database, which Apache Superset queries with filters or standard SQL. Analysts can work across 35+ event fields, build dashboards and export them as PDF, image, or CSV. This is the path for the full stream, including monitors that fire thousands of times a day.
Docs: Apache Superset Integration ↗Bring Your Estate
IREX is camera-brand agnostic. Cameras connect through RTSP, and an ONVIF device such as an NVR can be registered so its connected streams are available for analytics. The deployment team selects the streams to process and validates each camera against the analytics module it will run.
Check Camera Compatibility →For a registered ONVIF device with archive access, IREX can play the archive stored on the camera or NVR. Video from another source can also be uploaded for analysis, then searched with the standard event filters. These paths preserve useful evidence without requiring every investigation to begin with a fixed camera.
See Video Management →Bring a camera inventory, network constraints, the workflows that need alerts, the systems that should receive an event, and the reporting questions analysts need answered. IREX then confirms the applicable protocol, camera capability, event volume, permissions, and pilot scope with the project team.
Plan a Pilot →Set the Boundary Early
Start with the recipient and volume. Choose Sover when a person needs to receive and coordinate around the alert. Choose the REST API and webhook when an individual event must call software or a device. Choose Apache Superset when the goal is analysis of the full event stream. The project team validates the choice against the workflow during design.
Yes. An alarm monitor can call a nominated HTTP endpoint as soon as an event matches its filter. The HTTP method is selectable and POST can include event frames. It is intended for individual event actions, not a monitor producing a high-volume stream.
An ONVIF NVR can be registered as a device so its connected camera streams are available to IREX. IREX can also play an accessible archive behind a registered ONVIF device. Confirm the camera and NVR inventory during design; IREX does not claim a fully implemented integration with named third-party VMS products.
The documented path is Apache Superset, which lets authorized users query the event database through filters or standard SQL and export charts and dashboards. Direct raw database connectivity for customers is not documented.
Keep Reading
Bring the camera inventory and the workflows that matter. We will map the right integration path, readiness checks, and success criteria before implementation starts.