1 Detect
Recognise the object
The local model identifies a car in the camera view.
How computer
vision works.
Cameras supply the view. An on-site device turns it into counts and events. Use the results in dashboards, reports and alerts.
How a count is created.
A configured line turns movement through a camera view into a recorded crossing.
2 Track
Measure the crossing
The same object is followed across frames. Crossing the configured line creates an event.
Event record
+1 crossing
- Class
- Car
- Direction
- Entry
- Timestamp
- Location
- Camera 1 · Entry 1
3 Record
Store an event
Object class, direction, timestamp and location form a useful record, without reading the vehicle's registration number.
A crossing count is not a count of unique people or vehicles.
What leaves the site.
Traffic analytics records vehicle types and movements, not vehicle registration numbers.
Stays on site
- Camera video, processed on the edge device.
- Detection and tracking, by a model running locally.
- Event records, in an encrypted local database that buffers them while the cloud connection is unavailable.
Sent to your dashboard
- Batches of events and statistics, sent over HTTPS when connectivity allows. The camera stream does not follow that route.
- Counts by class, including the unified utility category, and pedestrian counts when the relevant model is enabled.
- Direction (entry, exit or passing through a monitored line), timestamps and location context.
- Calibrated speed measurements and accuracy ratings where configured.
- Zone activity, dwell-time events and configured alert notifications.
Never collected
- Video or images uploaded to the cloud, or kept as an analytics recording.
- Number plate reading (ANPR) or plate records.
- Facial recognition, names or personal identities.
- Individual visitor histories or identity tracking between sites.
- Audio capture for the analytics pipeline.
Frames are processed on the device and immediately discarded. Only anonymised events and statistics leave the site; no images or video are sent.
PrivacyUsing your results.
Access is separated by customer. Choose the format that suits your work.
Web dashboard
Current device status, historical trend charts, filterable event tables and report generation. Role-based access controls govern who can see the data.
REST API
Programmatic access to paginated events and hourly or daily aggregates. Tenant API keys and IP allowlists support controlled integrations and automation.
Near real-time alerts
Built-in or custom rules cover inactivity, thresholds and loiter time. Review alert history and resolution tracking; timing depends on the configured evaluation cadence.
Bulk CSV export
Download data filtered by date and location for Excel, Python or other analysis tools. Background processing supports exports of up to 365 days of available data.
Technical details.
Reference specifications, not a performance guarantee: we confirm hardware, rates, available history and deployment requirements for your site.
Edge hardware & camera inputs
- NVIDIA Jetson Orin series with Ampere GPU architecture.
- NVDEC hardware decoding for H.264 and H.265.
- Reference processing rate: 12-15 frames per second at 1080p; camera capture can be up to 30 frames per second.
- USB, RTSP and ONVIF inputs, with compatible PTZ control.
- Encrypted local event storage, local buffering and offline-resilient processing.
Detection model & tracking
- Custom-trained UK traffic model with TensorRT FP16 acceleration.
- Six supported classes: car, utility, motorcycle, bicycle, bus and person.
- Training includes elevated and aerial views, night conditions and more than 50,000 road images in the reference model.
- Multi-object tracking reconnects detections across frames, so movement is measured without counting the same detection repeatedly; these temporary object IDs do not identify people.
- Reference inference time is under 100 milliseconds per frame, with local capture-to-event storage under 200 milliseconds. Confirm performance against the deployment configuration.
- Bespoke detection model integration can be scoped for other use cases.
Data protection & access controls
- Full-disk encryption and AES-256 local database encryption.
- Password-protected devices without default credentials.
- HTTPS/TLS 1.3 transport and per-device API keys in the reference configuration.
- Tenant isolation, role-based portal access and configurable retention.
- The client portal supports MFA.
Cloud, sync & operational health
- Cloud hosting with an EU-region option; confirm the deployment region.
- REST data API with tenant API keys and IP allowlist controls.
- Reference statistics sync interval: 15 seconds; reference device heartbeat: 30 seconds.
- Alert evaluation follows its own configured cadence after data arrives, so a sync interval is not an alert-delivery promise.
- Health monitoring, automatic recovery and transparent device status support operations.
- Bulk CSV exports support up to 365 days, subject to the data available and configured retention.
Planning a deployment.
Camera placement, lighting, calibration and the question being asked all influence a useful deployment.
Confirm the conditions
Review the camera view, occlusion, indoor or outdoor setting, power and connectivity. Define which areas are and are not monitored.
Agree the success criteria
Specify the required counts, zones, rules, reports and data retention.
Review a site pilot
Check the resulting data against the operational question before expanding. Confirm that local processing, cloud sync and reporting work together for your site.