Ividiyo takes input from the rest of the site rather than replacing it. Anything that can close a contact, post to a URL or publish on a topic can raise an alarm here and cue the camera that covers it.
Where the integration already exists it is a configuration step, and using it costs nothing further: there is no add-on licence and no fee per integrated device, which is the part most vendors charge for. Where it does not exist yet we scope and quote it with the rest of the project — usually a short piece of work rather than a research exercise, because the connection is nearly always an API, a webhook or a contact closure.
Cameras
Any ONVIF or RTSP camera, whatever the make. Autodiscovery, PTZ, presets and camera-side events come with them.
Network video recording
Multi-server recording with failover, tiered retention and a single console across every site.
Analytics
Detection, classification and tracking run on your own GPU. Third-party analytics feed in as events over the API.
Automatic number plate recognition
Plate reads from any camera, with watchlists, visitor management and searchable history.
Facial recognition
Enrolment, search and alerts, running on your hardware alongside the rest of the detection pipeline.
Perimeter monitoring
Electric fence, beams and gate sensors raise a zone alarm with the camera covering that stretch already open.
Alarm panels
Any panel that can close a contact or post to a URL raises an alarm here, with an SOP and escalation attached.
Input output devices
Dry contacts and relay modules in both directions: take a trigger in, drive an output on an event.
Audio communication
Two-way audio through the camera from the browser or the phone app, so an operator can challenge someone on site.
Keyboards
Uniview KB1100, USB joysticks through the browser, and keyboard shortcuts for operators who would rather not use a mouse.
Storage
Tiered storage pools across local disk, NAS and cloud mount points, with policy-driven movement between them.
Supported protocols
ONVIF, RTSP, RTSPS, WebRTC, HLS, MQTT, REST and outbound webhooks, plus plain dry contacts.
Access control
Door and reader events linked to the camera on that door, with access history searchable beside the footage.
Fire panel
Panel events cue the cameras covering the zone and open the evacuation views on the wall.
Intercoms
Call events bring up the entrance camera and let the operator answer and see at the same time.
Building management
Plant and services alarms arrive as events with the relevant camera attached. Many reach us through Home Assistant today.
Environmental monitoring
Temperature, water, power and air-quality sensors raise alarms with video context, via Home Assistant or the API.
Command center management
Forward alarms to an existing control-room platform, or pull ours into it over the API.
Parking
Bay occupancy and barrier events tied to plate reads at the entrance and exit.
Weighbridge
Weight tickets matched to the plate and the footage of the vehicle on the bridge.
Retail systems
Point-of-sale exceptions linked to the till camera, so a void or a refund has video against it.
Body-worn cameras
Offloaded footage brought into the same timeline, search and evidence trail as the fixed cameras.
Video encoders
Analogue cameras brought in through any ONVIF or RTSP encoder, counted as ordinary channels.
Networking
Switch and link health raised as alarms beside camera and server health, via SNMP traps or the API.
Not on the list?
Ividiyo has a documented REST API, outbound webhooks, MQTT and plain dry-contact inputs, and a first-class Home Assistant integration that reaches a great deal more. Tell us what you run and we will tell you straight which of the three it is: already supported, a piece of development we will quote before you commit, or something we cannot do.
