[Developers]

ONVIF Standards Integration

Native ONVIF support lets the platform onboard virtually any IP camera or video recorder, stream live media, retrieve recordings and analytics, and export evidence as standards-compliant bundles other systems can read.

Category: Data IntegrationLast Updated: Jul 16, 2026
data-integrationreal-time

Overview#

Native ONVIF support lets the platform onboard virtually any IP camera or video recorder, stream live media, retrieve recordings and analytics, and export evidence as standards-compliant bundles other systems can read. A city surveillance estate rarely comes from a single manufacturer: it accumulates cameras and network video recorders across procurement cycles, each generation with its own onboarding quirks, and vendor-specific integrations cannot keep pace. Because the vast majority of IP video devices already implement the open ONVIF standard, speaking that standard natively removes the integration bottleneck entirely.

The module probes any ONVIF device, detects which profiles it supports, and onboards it without bespoke connector work. From there, operators get live media and recording-source discovery, investigators get recording search and retrieval from network video recorders, and analysts get parsed analytics metadata and device event subscriptions. An export engine closes the loop by packaging platform evidence, including body-worn camera recordings, as ONVIF-standard evidence bundles that a partner agency's video management system can import directly. Everything runs without external service dependencies, so fully air-gapped deployments are supported.

Key Features#

  • Universal Device Onboarding: Probe any ONVIF device, detect its supported profiles automatically, and onboard it regardless of manufacturer, with no vendor-specific integration required.
  • Live Media and Source Discovery: Stream live video from Profile S and Profile T devices and discover the recording sources each device exposes.
  • Recording Search and Retrieval: Search stored footage on Profile G network video recorders and retrieve it into platform evidence workflows.
  • Analytics Metadata Handling: Parse Profile M analytics metadata streams covering objects, events, and positions, and generate compliant metadata on the way back out.
  • Device Event Subscription: Subscribe to device events through the ONVIF pull-point mechanism so alarms and analytics events flow into operational views as they happen.
  • Standards-Based Evidence Export: Package recordings as ONVIF-standard evidence bundles, embedding the analytics metadata track directly into the MP4 container when a transcoder is available.
  • Air-Gapped Operation: Run the full capability with no external service dependencies, backed by hardened XML parsing and network-safety guards.
  • Conformance Test Harness: Verify a device's compatibility with a built-in conformance harness before committing to fleet-wide deployment.

Use Cases#

  • Mixed-Estate Onboarding: A municipal surveillance manager onboards CCTV cameras and recorders from many manufacturers in one pass, without commissioning a separate integration for each vendor.
  • Cross-Agency Evidence Handover: An evidence officer hands recordings to a partner agency as a standards-based bundle that the receiving agency's video management system imports directly.
  • Recorded Footage Investigation: An investigator searches network video recorders for footage around an incident window and pulls the relevant recordings into the case.
  • Pre-Purchase Compatibility Testing: A systems administrator runs the conformance harness against a candidate camera model before approving a large procurement.
  • Secure Facility Deployment: A security lead at an air-gapped site operates device onboarding, live streaming, and recording retrieval entirely inside the facility network.

Integration#

ONVIF integration feeds the wider surveillance and evidence capabilities of the platform. Onboarded devices sit alongside the platform's camera telemetry and surveillance camera domain capabilities, retrieved recordings flow into platform evidence workflows, and body-worn camera material managed elsewhere in the platform can leave through the same standards-based export engine. Embedding the analytics metadata track into exported MP4 bundles depends on a transcoder being available in the deployment; everything else runs without external service dependencies.

Open Standards#

  • ONVIF Profile S and Profile T: Govern live video streaming and media configuration for the IP cameras the platform onboards.
  • ONVIF Profile G: Defines the search and retrieval of stored recordings from network video recorders.
  • ONVIF Profile M: Specifies the analytics metadata for objects, events, and positions that the platform both parses from devices and generates for export.
  • OASIS WS-BaseNotification: Underpins the ONVIF pull-point mechanism used for device event subscription.
  • RTSP (RFC 2326): Provides the streaming control protocol used by ONVIF media profiles for live video delivery.
  • ISO Base Media File Format (MP4): Exported evidence bundles embed the analytics metadata track directly into MP4 containers when transcoding is available.

Last Reviewed: 2026-07-16 Last Updated: 2026-07-16

Ready to Build?

Get started with our APIs or contact our integration team for support.