When an intrusion or motion alarm fires, security teams lose critical minutes hunting for the clip. AlarmResponder connects to XProtect, grabs the relevant video automatically, transcodes it, and delivers it to the right people — before anyone has touched a keyboard.
The whole pipeline runs unattended. By the time an operator looks up, the right people already have the clip on their phone.
XProtect raises an intrusion, motion or analytic alarm. The service catches the event instantly.
Per-camera rules check alarm type, time window and cooldown — suppressing noise before anything is sent.
The relevant clip is pulled, transcoded with FFmpeg to under 8 MB, and uploaded to Azure Blob Storage.
A time-limited SAS link goes out over WhatsApp and Email, with an outbox retry queue guaranteeing delivery.
Alarm events trigger automatic clip capture and dispatch via WhatsApp (Meta Cloud API) and Email. An outbox retry queue guarantees delivery even through network blips.
Per-camera rules filter by alarm type, time window and cooldown interval — so operators receive only the alerts that matter, not a flood of false positives.
Clips are transcoded with FFmpeg to under 8 MB, uploaded to Azure Blob Storage, and served via time-limited SAS URLs — nothing is stored on end-user devices, and links expire on schedule.
A JWT-authenticated web dashboard gives managers a live view of alarm history, camera rules and recipients — all in one place.
Failed sends are queued and retried automatically — no alarm clip is ever silently dropped.
Installs alongside XProtect as a managed Windows Service — no extra infrastructure to babysit.
AlarmResponder sits beside XProtect and orchestrates capture, transcode, storage and dispatch — with the dashboard and retry queue keeping everything observable and reliable.
AlarmResponder is in active development. Join the early-access programme to pilot it on your XProtect deployment.