Access control
Card readers, controlled doors and access control panels — both entry and exit events and forced-door alerts.
Integrations
The equipment you already have keeps working
We connect to the manufacturer's SDK directly when we need a capability specific to that brand, and use common standards such as ONVIF or RTSP when they are enough — both routes end on the same screen for operators.
Simulated
| Brand / standard | Live view | Playback | Clip export | Connection method |
|---|---|---|---|---|
| Milestone XProtect | Supported | Supported | Supported | MIP SDK |
| Hikvision | Supported | Model dependent | Model dependent | Manufacturer SDK |
| Dahua | Supported | Model dependent | Model dependent | Manufacturer SDK |
| Bosch | Supported | Supported | Supported | ONVIF Profile G |
| Tiandy | Supported | Supported | Supported | Manufacturer SDK |
| Avigilon Alta | Supported | Supported | Supported | RTSPS + REST API |
| Axis | Supported | Model dependent | Model dependent | ONVIF / VAPIX |
| Hanwha Vision | Supported | Model dependent | Model dependent | ONVIF / SDK |
| Uniview (UNV) | Supported | Model dependent | Model dependent | ONVIF / SDK |
| ONVIF-standard devices | Supported | Profile dependent | Profile dependent | ONVIF Profile S / G |
| Generic RTSP cameras/streams | Supported | Not in the standard | Not in the standard | RTSP |
What works in practice depends on the device model, firmware and SDK version at each site — our team always confirms it project by project first.
The table shows how each brand connects (SDK, ONVIF, VAPIX, RTSPS and so on). What is available depends on the model and firmware. Beyond these, the platform supports more than 95 camera brands through the ONVIF standard and the recorder connection layer (Recorder Integration).
Not just cameras
Other systems that can connect to the same center
Intrusion detection
Burglar alarm panels and detection sensors, escalated into events linked to camera video of that area.
Fire alarm
Fire alarm panels, sending signals to the command center with the zone location on the map.
Sensors and industrial devices
Devices that communicate over standard protocols such as Modbus. Their values can be displayed and alert thresholds set.
Maps and area layouts
Show device locations on a map or building plan. Offline map sets can be used for closed-network sites.
External notifications
Send alerts to the channels your team already uses, such as email or chat apps, according to the organization's policy.
Brands not on the list
A new connector can be added without affecting the existing system
The layered architecture means supporting a new brand is a matter of adding a connector, not changing the core. The screen operators use does not change, and no retraining is needed.
- Assess feasibility from the SDK documentation or the standards the device supports
- Test with real devices in the lab before going to site
- Deliver with test results showing which features work and which hit manufacturer limits
- State the scope clearly from the start, and promise no capability the device cannot deliver
Open standards
Talk to other systems through common standards
Besides brand-specific SDKs, the platform supports many open standard protocols, covering video, building devices and data connections.
ONVIF
PSIA
RTSP
REST API
MQTT
SNMP
BACnet
Modbus
OPC
SQL
SMTP
SFTP
SIP
Supported video formats: MJPEG · MPEG-4 · H.264 · H.265 — export files as Raw / AVI / MP4
Send us your equipment list to assess
Tell us the brands, models and number of devices you use, and we will reply with how far they can connect.