Camera + VMS integration

FI Tech + Hikvision: AI Vision on Your Existing CCTV

FI Tech is camera-agnostic and integrates with Hikvision cameras and HikCentral via ONVIF Profile S/T, RTSP, ISAPI and the HikCentral OpenAPI — no rip-and-replace. We pull streams from your NVR or HikCentral, run PPE, intrusion, fall, fire, license-plate and occupancy models, then post detections back as HikCentral alarms or NVR ISAPI events. Typical pilot deploys in 2–4 weeks on a Riyadh-hosted, PDPL-aligned data path.

Talk to integrations teamRead setup guide

Compatibility matrix

Supported product linesHikvision IP cameras (DS-2CD, ColorVu, AcuSense, DarkFighter, Pro / Ultra), HikCentral Professional VMS, DS-7000 / 8000 / 9000 NVR series
Required ONVIF profileProfile S minimum, Profile T recommended for H.265 + events. Hikvision cameras typically expose ONVIF S/T after the user is enabled in System → Security → Network Service.
AuthenticationHikvision-side ONVIF user (digest) — must be created separately from the admin user. ISAPI / ISUP HTTP basic. Optional 802.1X / TLS.
Streaming protocolsRTSP/RTP (H.264, H.265, MJPEG), Hikvision ISAPI HTTP, ISUP for cameras behind NAT
Event channelONVIF metadata, ISAPI alarm-stream long-poll, HikCentral OpenAPI events, webhook, syslog
FI Tech deployment topologyFI Tech inference server peers with Hikvision NVR or HikCentral on the LAN. Detections post back as ISAPI external alarms or HikCentral OpenAPI events.

Setup guide

Seven steps from "verify ONVIF" to "test alert".

  1. 01

    Verify ONVIF and Hikvision firmware

    Confirm cameras run a recent Hikvision firmware (V5.7.x or newer) and that ONVIF is enabled under System → Security → Network Service. Create a dedicated ONVIF user with Operator level.

  2. 02

    Open the LAN path to FI Tech

    Allow RTSP 554/TCP, ONVIF 80 or 443/TCP, and ISAPI 80 / 8000/TCP from the FI Tech inference host to each camera and to the NVR / HikCentral server.

  3. 03

    Provision Hikvision and HikCentral users

    On each camera, create a dedicated ONVIF / ISAPI Operator user. In HikCentral, create a service account with View Live and Receive Events privileges, plus an OpenAPI partner key.

  4. 04

    Install the FI Tech connector

    Deploy the FI Tech connector container on Ubuntu 22.04 LTS or Windows Server 2022. Point it at the NVR or HikCentral server and authenticate with the OpenAPI key.

  5. 05

    Map cameras and AI models

    Select Hikvision cameras in the FI Tech console and assign AI models per stream — PPE, intrusion, fall, fire, license plate, occupancy. Save the mapping.

  6. 06

    Configure alarm routing

    Choose how detections appear: HikCentral alarm with workflow, ISAPI external alarm into NVR alarm stream, smart-event overlay, or webhook to your SOC. Test with a tripwire event.

  7. 07

    Test the end-to-end alert path

    Stage a controlled scene. Verify the alarm reaches HikCentral or the NVR client within ~1.5 s and that the configured workflow fires.

AI models supported on Hikvision

  • PPE compliance

    Hard hat, vest, gloves, boots, harness — strong on Hikvision ColorVu and AcuSense streams.

  • Intrusion / perimeter

    Polygon zones, loitering, line crossing; complements Hikvision AcuSense on-camera events.

  • Fall detection

    Slip and from-height events for industrial sites and elderly-care.

  • Fire and smoke

    Early-stage detection with optional Hikvision thermal-camera fusion.

  • License plate (LPR)

    Saudi + GCC plates, runs alongside or in place of Hikvision Capture Unit cameras.

  • Occupancy and people-counting

    Per-zone counts, queue length, dwell time. Fuses with Hikvision DeepInMind people-counting where available.

Sample latency and accuracy

End-to-end latency
1.0 – 1.8 s end-to-end (camera → inference → HikCentral alarm)
Throughput
10 – 25 FPS per stream depending on model and GPU class
Model accuracy
PPE 92–96% mAP, intrusion 96%+ recall, LPR 94%+ on Saudi plates

Typical figures — depend on resolution, codec, lighting, GPU (T4 / L4 / A2000) and NVR load.

Saudi-specific deployment

For KSA customers, FI Tech offers a PDPL-aligned data path: raw video stays on your Hikvision NVR or HikCentral storage, inference runs on a sidecar appliance on your LAN or in our Riyadh region, and only structured detections leave the camera network. Alert routing is hosted in Riyadh with a documented residency boundary, and audit logs are exportable for NCA / SDAIA review.

Frequently asked questions

Do we need to swap our Hikvision cameras to use FI Tech?

No. FI Tech is camera-agnostic and integrates with Hikvision cameras and HikCentral via ONVIF, RTSP and ISAPI / OpenAPI. Cameras already on your NVR are eligible — no firmware swap.

Is FI Tech a Hikvision Technology Partner?

FI Tech connects via the publicly documented ONVIF, RTSP, ISAPI and HikCentral OpenAPI interfaces. Formal partner status is tracked separately on our partners page.

How do detections show in HikCentral?

Detections appear as alarms in HikCentral with the configured workflow — pop-up live view, sound alarm, email, or trigger a relay output. They can also flow as smart-event metadata for timeline filtering.

What if our cameras are on an NVR without HikCentral?

We support direct NVR integration via ISAPI external alarms and ONVIF event sinks. Operators see detections in the NVR client alarm stream and on the live timeline. Bookmarking and snapshot extraction also work.

How does data residency work in KSA?

Raw video stays on your NVR / HikCentral storage. Inference runs on-prem or in our Riyadh region; only structured detections cross the network. Audit logs are exportable for NCA / SDAIA review.

Ready to add AI to your Hikvision deployment?

We will scope cameras, models and HikCentral workflows on a 30-minute call.

Contact FI Tech