DEMO MODE — INTERSECTION-LEVEL RISK SCORES AND AI RECOMMENDATIONS ARE SIMULATED. SEE THE "REAL DATA" SECTION FOR ACTUAL PUBLISHED FIGURES.
Traffic accident infrastructure hotspot predictor — prototype

Find out why an intersection keeps crashing, not just that it does.

Indlela Safe ("indlela" — isiZulu for "the road, the way") combines accident records, traffic counts, road imagery, and weather data to identify which specific infrastructure combinations — visibility, lighting, lane geometry, signal timing — are driving repeat crashes, so road engineers get a diagnosis, not just a crash count.

Prototype only. The intersection watchlist and AI recommendation below are simulated for demonstration. The "Real Data" section below uses actual published Johannesburg crash-hotspot data, cited.

Articles
Article → Problem → Our AI + IoT Solution → How the AI models solve it going forward

Three real, cited road-safety sources, each traced through to how Indlela Safe's stack would address the specific problem the article describes, and what the AI layer adds as it matures beyond a single pilot.

Article 1 · Local reporting

Johannesburg's most dangerous roads named by JMPD

Source: TimesLive, 27 August 2019 — 41 road deaths recorded in the metro in July 2019, with JMPD naming Nasrec Road, the N1, the N17, William Nicol Drive, Elias Motsoaledi Road, Klipspruit Valley Road and Moroka Road as the worst-affected corridors.

Problem. The report names which roads are dangerous but not why — no per-intersection breakdown of sightlines, signal phasing, lane geometry, or the conditions under which crashes cluster. Engineers are left to guess at root cause without a repeatable diagnostic process.

Our AI + IoT solution. Cameras, inductive-loop counters and a weather sensor at each named corridor feed Azure ML, which correlates crash timing and location against traffic volume, visibility and road geometry to shortlist which specific infrastructure factor is implicated — turning "this road is dangerous" into "this approach has an obstructed sightline during evening peak."

How the AI models solve this going forward. As more pilots come online, Claude cross-references findings against a growing base of historical accident reports across intersections with similar geometry, so recurring fault patterns (like unprotected right-turn phases) get flagged faster at newly-monitored sites, even before enough local incident history has built up.

Article 2 · National road safety data

South Africa's road death toll and the Road Traffic Management Corporation's reporting

Source: Road Traffic Management Corporation (RTMC) — the RTMC publishes periodic national and provincial fatality statistics, generally reported by province and road category rather than by individual intersection.

Problem. National and provincial statistics are useful for policy but too coarse for a road agency deciding which of hundreds of intersections in one metro to fund an intervention at first. There is no standard, continuously updated way to rank intersections by evidence-backed risk.

Our AI + IoT solution. Indlela Safe's spatial risk model treats each monitored intersection as its own case, scored on live sensor input rather than an annual provincial average, so a road safety team can rank and prioritise the intersections actually under their responsibility.

How the AI models solve this going forward. With more monitored intersections, the same Azure ML model can be retrained on a larger, metro-specific dataset, and GPT-drafted summaries can start referencing comparable interventions that worked at similar intersections elsewhere in the network — turning isolated pilots into a shared, growing evidence base.

Article 3 · International practice

Vision Zero and systemic road-safety design

Source: Vision Zero Network — an international road-safety framework holding that road deaths are preventable through safer infrastructure design, not solely through driver behaviour change.

Problem. Many road-safety programmes still focus on driver enforcement (speeding, licensing) rather than fixing the infrastructure conditions — obstructed sightlines, poor lighting, unprotected turns — that make the same intersections crash repeatedly regardless of who is driving.

Our AI + IoT solution. Gemini's imagery analysis is pointed specifically at physical, fixable infrastructure conditions — obstructions, faded markings, lighting — and every recommendation is handed to a human road safety engineer, keeping the focus on infrastructure fixes rather than driver blame.

How the AI models solve this going forward. GPT Image 2 can generate labelled concept illustrations of a proposed infrastructure fix for engineer review, helping shift funding conversations from "who was at fault" to "what would prevent the next crash here" — always as a proposed concept, never a built or approved design.


Real data
Actual published Johannesburg crash hotspots

Real road names, from a real published source — not simulated. This is the kind of data Indlela Safe's spatial risk model would ingest and continuously update, rather than a one-off news report.

Real, cited data. In July 2019, the Johannesburg Metro Police Department (JMPD) publicly named the roads where most fatal crashes occurred that month, following 41 road deaths. Source: TimesLive, 27 August 2019. This is a real historical report, not a live feed — no public API of current, real-time Johannesburg crash data exists for this demo to connect to.

JMPD-identified fatal-crash hotspot roads, July 2019

RoadAreaType
Nasrec RoadSoweto / NasrecArterial
N1Citywide corridorFreeway
N17Eastern corridorFreeway
William Nicol DriveSandton / FourwaysArterial
Elias Motsoaledi RoadSowetoArterial
Klipspruit Valley RoadSowetoArterial
Moroka RoadSowetoArterial

This list is exactly what JMPD published — the source report gives the road names and the citywide monthly death toll (41), not a per-road crash count or contributing-factor breakdown. A real deployment would layer Indlela Safe's own sensor and imagery analysis on top of exactly this kind of official report to get to that level of detail.

Why the intersection-level detail below is still a demo

Getting from "Moroka Road is a hotspot" to "this specific intersection has an obstructed sightline and an unprotected right-turn phase" requires the sensor network, imagery pipeline, and per-incident crash records described in the AI + IoT stack — none of which are connected to this prototype. The watchlist and AI recommendation further down use realistic South African road names and plausible figures to show what that output would look like, clearly marked as simulated so it's never mistaken for the real JMPD data above.


How it works
From crash records to an engineering summary

Multiple data sources feed one spatial risk model. Every recommendation is reviewed by a road safety engineer before any intervention is planned.

01 · Data intake

Accident records, traffic counts, road imagery, and weather data for the metro area.

02 · Azure ML

Identifies high-risk infrastructure combinations through spatial risk modelling.

03 · Gemini + GPT

Gemini analyses intersection imagery for visibility/design issues; GPT drafts an engineering summary.

04 · Claude review

Cross-checks findings against historical accident reports for the same intersection.

05 · Engineer review

A road safety engineer reviews before any safety intervention is scoped or funded.


Interactive 3D model
Drag to rotate. Click a node to see what it does.

An illustrative engineering model of one monitored intersection — not a photograph or CAD export of a real site. Drag inside the scene to rotate it in three dimensions, use the buttons to spin it automatically, or switch between the assembled intersection and an exploded single-component view.

DRAG TO ROTATE
CAM
CNT
WX
ML
AI

Select a component

Click CAM, CNT, WX, ML, or AI in the model to see a detailed description of what that component does, what it physically measures or processes, and what it hands off next in the pipeline.

Roadside Camera
Traffic Counter
Weather Sensor
Azure ML
Multi-Model AI Layer

How it all works together

At one monitored intersection, the roadside camera, traffic counter, and weather sensor each collect one narrow slice of what's happening — an image frame, a vehicle count, a rainfall or visibility reading. None of them alone can explain why crashes keep happening there. Those three streams flow into Azure ML, which lines them up against the intersection's crash history and flags which infrastructure factors — a signal phase, a sightline, a lane marking — correlate with the pattern. That output is then split across the multi-model AI layer: GPT turns the finding into a plain-language summary, Claude checks it against the intersection's own historical accident reports, and Gemini inspects the camera imagery directly for visible causes like an obstruction or faded markings. The combined result becomes one structured recommendation with evidence and a confidence score, which a road safety engineer reviews and either approves, modifies, or rejects before anything changes on the ground. No single sensor or model makes that call by itself — the case for action only stands up when the evidence lines up across all of them.


Live monitor
Metro intersection watchlist
Demonstration only. Intersection names, crash counts, and recommendations below are simulated to show what the product's output looks like. Real published Johannesburg crash-hotspot data is in the "Real Data" section above.

Monitored intersections

62Demo
One metro deployment

Low risk

0
Within expected crash rate

Medium risk

0
Elevated, monitor trend

High risk

0
Recommend intervention review

Intersection watchlist Demo stream

Intersection / roadAreaNotesRisk

AI recommendation — awaiting review Illustrative example

Klipspruit Valley Road / Moroka Road intersection — review sightline and signal timing

Illustrative example scenario, grounded in a real JMPD-flagged corridor · generated by GPT (engineering summary) · reviewed by Claude against historical accident reports · 08:15 today
High
  • Klipspruit Valley Road and Moroka Road were both named by JMPD among Soweto's fatal-crash hotspot roads in its July 2019 report — the corridor context is real
  • Example scenario: right-turn collisions clustering during evening peak, consistent with an unprotected turn phase
  • Example scenario: Gemini's imagery analysis flags a roadside structure partially obstructing a sightline

The corridor is real and cited above. The specific crash count, collision-type breakdown, and confidence score below are an illustrative example of the product's output format — this level of detail isn't in the public JMPD report and would come from Indlela Safe's own sensor and imagery pipeline once deployed.

Confidence: 81% · Status: Awaiting engineer approval

AI layer
Model Type: spatial risk modelling + computer vision + predictive analytics

Each model handles a specific task. No intervention is planned or funded without a human engineer's sign-off.

Azure ML

Spatial risk modelling

Identifies which specific infrastructure combinations — geometry, lighting, visibility, signal timing — correlate with repeat crashes at a given intersection.

GPT

Engineering summaries

Latest GPT model turns the risk model's findings into a plain-language engineering summary for the road safety team.

Claude

Historical accident review

Latest Claude models review historical accident reports for the same intersection, checking new findings against past incidents and prior interventions.

Gemini

Intersection imagery analysis

Latest Google Cloud Gemini model analyses intersection imagery for visibility obstructions, lane markings, and lighting condition.

GPT Image 2

Proposed safety interventions

Generates illustrative concept imagery for a proposed safety intervention — labelled as a concept illustration, never presented as an approved or built design.

DATA INTAKE (accidents / traffic / imagery / weather) | AZURE ML -> spatial risk model, infrastructure factors | ----------------------------------------------- | | | | GPT CLAUDE GEMINI GPT IMAGE (engineering (historical (intersection (proposed summary) accident imagery) interventions) review) ----------------------------------------------- | STRUCTURED RECOMMENDATION + CONFIDENCE + EVIDENCE | ENGINEER REVIEW -> APPROVE / MODIFY / REJECT | ACTION LOGGED

Model identifiers (the exact GPT, Claude, and Gemini versions, and the current OpenAI image-generation model) must be verified against each provider's live API documentation at implementation time — "latest" maps to a configurable, verified identifier, never a hardcoded guess.


Cost
Priced per metropolitan deployment

Indlela Safe monitoring stack

  • Spatial risk modelling across all monitored intersections in the metro (Azure ML)
  • Engineering summary drafting (GPT), historical accident review (Claude), imagery analysis (Gemini), and intervention concepts (GPT Image 2)
  • Scales with number of monitored intersections and how many are actively flagged for engineer review each month
R5,000–R25,000
/ month / metropolitan deployment

Estimate — actual cost depends on metro size, data refresh frequency, and how many intersections are under active review in a given month. Validate against current provider pricing before quoting a client.


Company
Project information

Registered enterprise and director details for Indlela Safe, a product of Noir AI Technology Solutions (Pty) Ltd, as recorded with the Companies and Intellectual Property Commission (CIPC) of South Africa.

Real, registered company. Noir AI Technology Solutions (Pty) Ltd was incorporated on 24 August 2026 under the Companies Act, 2008, and is currently IN BUSINESS with the CIPC. Details below are taken directly from the company's CIPC registration certificate (Form COR 14.3) and Memorandum of Incorporation (COR15.1A).

Registered entity

Noir AI Technology Solutions (Pty) Ltd

Registration number: 2026/670777/07
Enterprise type: Private Company
Enterprise status: In Business
Registration date: 24/08/2026
Business start date: 24/08/2026
Financial year end: March
Type of MOI: Standard (COR15.1A)
Main business/object: Business activities not restricted

Registered office & postal address

113 1st Avenue, Geradsville
Centurion, Gauteng, 0157
South Africa

Company location of records: same address.

CIPC reference: 2026/670777/07 · Tracking number: 9464893273 · Customer code: AFJJGO

Contact by department

DepartmentEmail
General / admin enquiriesAdmin@noiraitechnologysolutions.co.za
Finance & billingFinance@noiraitechnologysolutions.co.za
Engineering / developersDevelopers@noiraitechnologysolutions.co.za

Director

Salah Setlhare

Director · Noir AI Technology Solutions (Pty) Ltd — appointed 24/08/2026, per CIPC disclosure

Director email: salah@noiraitechnologysolutions.co.za

"I built Indlela Safe because too many South African families lose someone on a road that everyone already knew was dangerous. My goal isn't just to name another dangerous intersection — it's to give the engineers who can actually fix it the evidence they need to act with confidence. If this technology helps even one community stop losing people to a crash that infrastructure could have prevented, it's done its job."
— Salah Setlhare, Director

Contact
Request a metro pilot

For metropolitan roads agencies, traffic departments, and road safety councils. This form opens your email app with a message addressed to palesachantelle1@gmail.com — it doesn't require any account or server.

Clicking send opens your default email app with everything pre-filled — you just hit send from there. Nothing is transmitted by this page itself.