VMS integration

FI Tech + Axis Camera Station: AI Vision on Your Existing CCTV

FI Tech is camera-agnostic and integrates with Axis Camera Station via ONVIF Profile S/T, RTSP and VAPIX — no rip-and-replace. We pull streams from your ACS server, run PPE, intrusion, fall, fire, license-plate and occupancy models, then post detections back as VAPIX events, ACS bookmarks or MQTT messages. 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 linesAxis Camera Station Pro and Edge, all current Axis IP cameras (Q, P, M, F series); third-party ONVIF cameras attached to ACS
Required ONVIF profileProfile S minimum, Profile T recommended for H.265 and metadata. Axis cameras are natively ONVIF S and T conformant.
AuthenticationAxis camera credentials (digest), VAPIX API key, optional 802.1X / TLS client certs
Streaming protocolsRTSP/RTP (H.264, H.265, MJPEG), VAPIX HTTP API, MQTT events from Axis cameras
Event channelVAPIX events, ONVIF metadata, ACAP application bridge, webhook, syslog, MQTT
FI Tech deployment topologyFI Tech inference VM peers with the ACS server on the LAN. Detections post back via VAPIX action rules and MQTT, or as ACAP application overlays.

Setup guide

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

  1. 01

    Verify ONVIF profile and Axis firmware

    Confirm cameras run AXIS OS 11.x or newer (recommended for ONVIF Profile T and metadata). Enable ONVIF in the camera web UI under Plain Config.

  2. 02

    Open the LAN path to FI Tech

    Allow RTSP 554/TCP, ONVIF 80 or 443/TCP, and MQTT 1883 or 8883/TCP from the FI Tech inference host to each camera and to the ACS server.

  3. 03

    Provision Axis and ACS users

    On each Axis camera, create a dedicated ONVIF / VAPIX Operator user. In ACS, create a service account with Operator privileges to read live and write events.

  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 ACS server and authenticate.

  5. 05

    Map cameras and AI models

    Select Axis 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 alert routing

    Choose how detections appear: ACS bookmark, VAPIX action rule (relay output, PTZ preset, email), MQTT topic for SCADA, or webhook. Test with a tripwire event.

  7. 07

    Test the end-to-end alert path

    Stage a controlled scene. Verify the detection reaches the ACS operator within ~1.5 s and that the configured action fires.

AI models supported on Axis Camera Station

  • PPE compliance

    Hard hat, vest, gloves, boots, harness — strong on Axis Q/P bullet streams.

  • Intrusion / perimeter

    Polygon zones, loitering, tailgating; complements Axis Object Analytics on supported cameras.

  • Fall detection

    Slip and from-height events for industrial sites.

  • Fire and smoke

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

  • License plate (LPR)

    Saudi + GCC plates, runs alongside or in place of AXIS License Plate Verifier.

  • Occupancy and people-counting

    Per-zone counts and queue length; fuses with AXIS People Counter where available.

Sample latency and accuracy

End-to-end latency
0.8 – 1.6 s end-to-end (camera → inference → ACS event)
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 ACS server load.

Saudi-specific deployment

For KSA customers, FI Tech offers a PDPL-aligned data path: raw video stays on your ACS server, 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 Axis cameras to use FI Tech?

No. FI Tech is camera-agnostic and integrates with Axis Camera Station via ONVIF, RTSP and VAPIX. Cameras already on your ACS server are eligible — no firmware swap required.

Is FI Tech an Axis Application Development Partner?

FI Tech connects via the publicly documented ONVIF, RTSP, VAPIX and MQTT interfaces. An optional ACAP application is available for on-camera overlay. Formal partner status is tracked separately on our partners page.

How do detections show in Axis Camera Station?

Detections post as VAPIX events that ACS renders as bookmarks, alarms or action rules — relay outputs, PTZ presets, audio playback, email or webhook. Bounding boxes can render via an ACAP overlay.

Can FI Tech run alongside AXIS Object Analytics?

Yes. We treat AOA events as additional inputs and fuse them with our analytics — useful for raising precision or for analytics AOA does not cover (PPE, fall, fire, LPR).

How does data residency work in KSA?

Raw video stays on the customer ACS server. 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 Axis Camera Station deployment?

We will scope cameras, models and VAPIX action rules on a 30-minute call.

Contact FI Tech