Alarm Platform Integrations

Alarm-platform integrations send classification outcomes to the monitoring systems your operators already use, rather than to a generic endpoint. Reach for them when your goal is to raise or enrich an alarm: if you only need the raw result, see Choosing a Delivery Method instead.

Gaard supports four alarm platforms. All are configured from Settings → Platform → Integrations and scoped to a flow.

Compare the platforms

Platform	Direction	Protocol	Typical use
Azursoft	Inbound and outbound	Gaard classify API (HTTPS)	Native Gaard verification inside Azursoft supervision: Azursoft submits clips and shows the verdict to operators.
Evalink	Inbound and outbound	HTTPS alarm API	Add AI verification to an existing Evalink alarm by creating a linked follow-up alarm.
Prysm	Inbound and outbound	HTTPS webhook (annotated video)	Push a verified, annotated clip to Prysm (ESI Vision) monitoring.
SIA DC-09	Inbound and outbound	SIA DC-09 over TCP	Interoperate with alarm panels and central stations over the standard alarm protocol.

Pick a platform

Azursoft Let Azursoft supervision submit clips and read verdicts with a flow-scoped API key.

Evalink Create a follow-up alarm in Evalink carrying the classification outcome.

Prysm Post an annotated clip and event metadata to a Prysm webhook.

SIA DC-09 Send events to a central station receiver, or receive and classify panel events.

Prerequisites

Every alarm-platform integration needs:

• An admin role in the tenant.
• A flow to attach the integration to. See Flows.
• Credentials and endpoint details from the platform you are connecting: each platform page lists exactly what to gather.

Related

Choosing a Delivery Method When to use an alarm platform versus polling, webhooks, or SFTP.

Webhooks Receive the result JSON as an HTTP callback.

SFTP Delivery Deliver results as files to your own server.

Flows How flows scope integrations, tokens, and webhooks.