Integration brief · Verkada ← Back to the page   Print or save as PDF
Integration brief VerkadaCameras, VMS and NVR

Live Alerts on Verkada Cameras, Evidence Kept on Site

Verkada cameras are managed and watched from Verkada Command in the cloud. AI Live Insight reads the same cameras over RTSP on the site's own network and watches all of them, raising an alert when a rule fires. The clip around each event lands in Nexus, AI Intelligence Hub answers questions over those clips, and Redactor blurs faces before a copy goes out. Command stays in charge of the cameras.

What you can do together

  • Watch every Verkada feed for people, vehicles, weapons, license plates, fire, and PPE or its absence, with zone rules for loitering, intrusion, line crossing, crowd count and direction of travel, through AI Live Insight.
  • Get an alert with a snapshot by email or webhook when a rule fires, and keep the seconds around it with event-driven recording.
  • Hold the clips in Nexus with a SHA-384 integrity hash, a chain-of-custody log and a retention schedule, and ask AI Intelligence Hub which clips show what, each answer cited.
  • Release a copy with Redactor blurring students' and bystanders' faces and plates, a code on each redaction recording why, and the original left in the library.

How it connects

AI Live Insight connects over RTSP. Where RTSP is enabled for a camera in Verkada Command, it publishes a stream on the local network and is added with its address, port, stream path and credentials. The H.264 or H.265 bitstream is read as emitted, codec detected per source.

Only the live stream flows, inbound, to a GPU server on the same network. Detections become a timed metadata track beside each recorded segment, and the clip around an event is filed in the library under one Recording Folder, under its access control, retention and chain of custody. Classes, thresholds, zone rules and clip length are set per camera in the portal.

There is no pull from the Verkada cloud archive. Footage held in Command reaches Nexus by export and upload; no API carries it across. Camera settings, Command's own analytics and alerts, and its users stay with Verkada.

VIDIZMO and Verkada · Integration briefPage 1 of 2
How it works VerkadaCameras, VMS and NVR
Verkada cameras, VMS or NVR, existing estate RTSP / ONVIF live stream AI Live Insight detect, alert, zone rules watchlists, event clips live view, built-in NVR event clips and detections Nexus the record: storage, retention, audited access, hash and chain of custody ask across it AI Intelligence Hub ask, describe, correlate workflows and alerts redact before release Redactor faces, plates, audio, documents; audit trail Verkada VIDIZMO

A scenario

  1. 15:05, middle school bus loop cameraA car enters the loop against the arrow while buses are loading. AI Live Insight fires the direction-of-travel rule at Medium and emails the front office a snapshot. The assistant principal walks out; the plate is read and kept as a searchable event.
  2. 22:30, high school gym entrance cameraTwo people have stood in the zone at the gym doors past the dwell threshold. The loitering alert reaches the on-call administrator by webhook with a snapshot, and the clip lands in Nexus.
  3. 22:40The administrator watches the clip, recognizes two students, phones their parents and resolves the alert with a note carrying her name and the time.
  4. Next morningThe Operator Dashboard shows two elementary school cameras Offline together. The IT lead reads that as a switch, not two cameras, and fixes it before the school notices.
  5. Two weeks laterA parent disputes the bus loop incident. The district asks AI Intelligence Hub for that week's bus loop clips, exports the hour from Command and uploads it beside them. Redactor blurs every student's face before the copy goes out under FERPA. The original stays untouched.

What stays where

Verkada Command remains in charge

It configures and records the cameras and manages the district's users. AI Live Insight reads the stream each camera publishes locally. Nothing is replaced.

No API into the cloud archive

VIDIZMO products read live streams only. Footage exported from Command and uploaded to Nexus then sits under the same retention and chain of custody.

Processing on your own network

A GPU server on site runs detection and recording, so alerts do not need the internet link. The library, the assistant and redaction run there too, in your own cloud, or air-gapped with self-hosted models.

Two orders, one setup

Cameras and Command licenses come from your Verkada reseller. VIDIZMO licenses its software separately; adding a camera is configuration, not a project.

Products and solutions

Next step

See it on your own Verkada instance.

We will show the connection made, the data moving and the output, then size it for your deployment.

Contact VIDIZMO

sales@vidizmo.ai

+1 571-969-2180

vidizmo.ai

Product names and logos are the property of their respective owners.Page 2 of 2