For cities & public agencies
Your city's existing cameras, turned into block-face data: posted rules and bays as map layers, live views, and occupancy where detection is on. Data layers and exports, an API on request, a platform for operations, and a companion app for drivers.
Looking for our mobile app? DriversMobile app·Fleets
Cameras
25,000+
across 23 sources, 10 countries (September 2026)
Curb-rule layers
17
NYC rules and coverage, Edinburgh, 14 London boroughs
NYC signs decoded
~440K
all five boroughs, text kept verbatim
Data feeds
52
incidents, signs, weather, flow, parking
Block-face network
~140K
addressable NYC curb network
Detections / day
~17M
pipeline capacity at <5s cadence
Platform uptime
99.7%
measured rolling 90-day
Integrations
12
311, DOF, sanitation, sign mgmt
Data & API
Built from the sources we run and decoded to the block-face. New York and London are live today; both export as GeoJSON, and the API is available for a pilot.
All five boroughs
Every posted curb sign decoded to a block-face rule, with the sign text kept verbatim.
Curb coverage: which faces are signed, which have no curb to park at, and where the record is blank.
Live stills from the city and state camera networks we run.
Free and occupied curb from computer vision, with a confidence figure per block-face.
Camden, Westminster, 12 more boroughs
Parking and loading bays with their hours, maximum stay and length, so a 7.5 t van knows whether it fits.
Controlled parking zone boundaries and the hours they apply.
Live stills from the city-wide traffic camera network.
Free and occupied curb from computer vision, with a confidence figure per block-face.
Also live: Edinburgh bays, off-street parking in both cities, and 25,000+ cameras with 52 traffic and road feeds across 10 countries. Every layer exports as GeoJSON for the area you work in.
Who it is for
Written as a specification with illustrative responses, so your team can see the shapes before a line of code. Pilot access is by arrangement.
POST /v1/kerb/rules
Every regulated block-face in a bounding box, with its posted signs verbatim and its measured geometry.
GET /v1/kerb/schedule
One block-face's week, hour by hour: when it is metered, swept, cleared for rush hour, or free.
GET /v1/parking/occupancy
How full each block-face is right now, from camera detection.
GET /v1/traffic/flow
Counts by vehicle class, and pedestrians and cyclists where the feed carries them.
Data held: the layer is on the platform today and the route is plumbing. Pilot: switched on per study area. 9 further endpoints, coverage beyond the two focus markets, and the figures behind each layer go out on a pilot call. Counts as of September 2026.
Request pilot accessPlatform
Six modules, one data platform. Every capability maps to a specific curb-management workflow that cities are currently solving with spreadsheets, intern labor, or nothing at all.
Every block-face at block-level resolution. Nine data layers, time-travel scrubbing, block inspector with live camera feed, and export to GIS.
Per-meter, per-block, per-district revenue with supply-vs-demand gap mapping, evasion rate, and block-level pricing recommendations.
Deploy officers where violations are most likely, based on predicted block-face violation density. Equity dashboard cross-tabs enforcement rates with neighborhood demographics.
Model meter-hour changes, pricing shifts, loading-zone placement. Before-and-after analysis for council decks.
Council-ready quarterly reports and FOIA-compliant audit exports. Grant packs for FHWA, EPA, FTA.
Native connectors for meter payment, city sign inventory, 311, sanitation, sign management, GIS, and enforcement hardware.
Use cases
01
Reprice underperforming meters with modeled impact on utilization and spillover. Cities have modeled ~8–14% revenue uplift from pricing adjustments informed by utilization data.
02
Enforcement parity across neighborhoods, with audit-ready exports for council oversight. Cross-tabbed against demographic and income data.
03
Cruising-emissions reporting backed by EPA factors. Policy-impact estimates for climate offices and federal grant applications.
04
Pre-built data packs and methodology notes for FHWA, EPA, FTA, and USDOT submissions. Less grant-writing time, more money won.
Modules in depth
Module 01
Block-face occupancy heatmap across the whole city. Nine toggleable data layers. Time-travel from live through year-over-year. Anomaly alerts when a block's pattern breaks.
Module 02
Supply-vs-demand gap mapping. Meter evasion rate. Block-level pricing recommendations. Elasticity modeling that shows what happens when you change a meter price.
Module 03
Agent deployment recommendations based on predicted violation density. Live field-ops mobile companion. Equity dashboard cross-tabbed against demographics.
Module 04
What-if modeling for meter hours, pricing changes, loading-zone placement, parking-to-bike-lane conversions. Before-and-after comparison when changes ship.
Module 05
Council-ready quarterly reports. Grant-application data packs for FHWA, FTA, EPA, USDOT. Audit logs and FOIA-compliant exports. Inter-agency data sharing.
Module 06
No rip-and-replace. We read from existing camera feeds and write into the systems your city already runs: meter payment, citation hardware, GIS, and data platforms.
Also for
For fleets & operators
Live dispatch, loading-zone intelligence, and ticket-risk avoidance for delivery, rideshare, and field services.
Fleets platformFor drivers
Real-time parking guidance for NYC, powered by the same computer vision we sell to cities.
Drivers appStart with a pilot
Scoped pilot. Fixed fee. Convertible to a full deployment.