Edge-first · Events, not video
NEXUS connects CCTV and ANPR feeds at the edge, fuses observations across cameras, and delivers vehicle journeys and traffic analytics from one graph.
Works with your stack
0
Video frames sent upstream
4
Signals in identity fusion
100+
Cameras per deployment target
1
Graph for journeys & traffic
Platform
Detect, track, and OCR at the camera.
Every feed becomes an edge node. Video stays local. Upstream traffic is structured JSON events only: plate, appearance, timestamp, direction.
Associate vehicles across the city.
Four-signal fusion: plate, appearance, time, topology. Outputs are scored and explainable: MATCH, PROBABLE, UNRESOLVED, CONFLICT.
Operate journeys and city traffic.
Map-first operator console: live sightings, plate search with explain panels, corridor analytics, and human-gated alerts — wired to the NEXUS API.
01 · Observe
NEXUS sits on top of CCTV and ANPR you already deploy. Edge nodes run detection, tracking, and plate OCR locally, emitting structured events, never raw video streams.
See capabilitiesCorridor live view
02 · Connect
Observations fuse across cameras using plate, appearance, time, and topology. The graph powers both vehicle identity and city-level traffic metrics from the same data.
See capabilitiesVehicle path · graph animation
Mission
Sectors
Search by plate or appearance, replay full journeys on a map, and review alerts with transparent scoring: plate, Re-ID, time, and corridor topology.
Includes
Journey replay
Plate, appearance, time, and topology, scored, never forced.
Natural-language queries with journey replay and match rationale.
Video stays local. Upstream is structured JSON only.
Vehicle journeys and corridor / OD metrics from one event stream.
Architecture
01
Ingest
RTSP / ONVIF · existing CCTV & ANPR
02
Edge
Detect · track · OCR · attributes
03
Event
JSON schema · no raw video upstream
04
Graph
4-signal fusion · spatial-temporal links
05
Console
Map · search · alerts · analytics
Latency
Edge-first · sub-second local inference
Privacy
Video on-prem · events only upstream
Scale
Corridor → district → city rollout
Use cases
“Show me this plate since 09:00 across the corridor, and tell me why you matched C07.”
“Give me travel time on C03→C15 and the OD for this hour, from the same events.”
Principles
I
Upstream traffic is structured JSON. Raw feeds never leave the edge node unless policy explicitly allows it.
II
Every cross-camera link is scored and labeled: MATCH, PROBABLE, UNRESOLVED, CONFLICT. Operators see why.
III
Vehicle journeys and city traffic metrics derive from the same spatial-temporal graph. No duplicate pipelines.
IV
Consequential alerts require operator acknowledgment. Automation assists; humans decide.
FAQ
No. NEXUS is a layer over CCTV and ANPR you already own. Each feed becomes an edge node that emits events, not video.