Trafficure · FAQ
Trafficure, your questions, answered
What it is, where the data comes from, how fast you go live, who runs on it today, the results it has produced, how it sits beside camera ITMS, the privacy posture, and how it is priced, the questions city traffic and planning leaders ask most, answered straight from how Trafficure is deployed.
Get a demo →What is Trafficure?
A software-only traffic intelligence platform for cities. It turns Google Maps probe data into real-time congestion alerts, road-level analytics, and automated reports, with no cameras, sensors, or construction. The map is the interface; monitoring, alerting, analytics and reporting come first.
Where does the data come from?
Google’s Roads Management Insights (RMI): anonymized, aggregated movement data from over a billion Google Maps and Waze smartphones, refreshed about every 2 minutes across 100% of the road network. RMI is the data layer; Trafficure is the activation layer of dashboards, alerts and reports built on top of it.
How fast can we go live?
Typically 2 to 4 weeks. Pune City Traffic Police went live on 100% of their road network in 3 weeks. If you already hold an RMI subscription, Trafficure activates it in 2 to 4 weeks; from a fresh signature the activation layer is delivered in roughly 4 to 8 weeks.
Who uses it today?
Pune City Traffic Police, the first software-only city-wide traffic deployment in India (Feb 2026, with Google India), alongside Pune Municipal Corporation, Kolkata Police, Howrah Police Commissionerate, Bidhannagar, and Barrackpore.
What results has it produced?
In the Pune 45-day pilot, average speed rose from 20 to 26.8 km/h (a 34% gain) across 550 monitored zones. The 102-day report recorded 1.27M litres of fuel saved, ₹13.4 Cr of commuter spending retained, and 2,937 tonnes of CO₂ avoided, with 39,734 congestion build-ups surfaced and closed at a median clearance of 26 minutes.
How is this different from our camera ITMS?
Trafficure is complementary, not a replacement. Camera ITMS handles junction enforcement, ANPR and signalling on the 2 to 3% of roads it can see; Trafficure covers the other 97% of the network that cameras never reach, at a 2-minute refresh, deployed in weeks rather than years, on a subscription rather than tens of crores of capex. See Trafficure and camera ITMS, side by side.
Does it control traffic signals?
No. RMI data is not built for sub-second junction signalling; that remains a sensor and ITMS job. Trafficure is monitoring, alerting, analytics and reporting across the whole network. We are honest about the boundary: k-anonymity thins out very quiet roads, so this is city-wide situational awareness, not junction-level actuation.
What about privacy?
There is no personally identifying information. Google aggregates and anonymizes the movement data with k-anonymity at source before Trafficure ever sees it. The platform is designed for GDPR and India’s DPDP Act.
How do alerts reach our officers?
Through the command-centre dashboard plus WhatsApp and SMS, email, Slack, webhook, and X. Thresholds, priorities and auto-resolve are configurable, with a full alert history retained. After re-architecting to a 2-minute cycle, alert latency runs under 3 minutes, down from about 7.
What does it cost?
Subscription, scoped per agency by network size. Zero capex, no AMC, and no hardware to replace. A demo runs on your city’s actual road data rather than slides. See how a city gets started for the engagement model.