How it works

Kerbside runs a data pipeline for each city it supports. The pipeline fetches raw open data from the council, transforms it into a consistent format, and stores it so it can be queried by postcode.

The pipeline

Keeping data fresh

Each city’s sync job runs on a schedule and checks whether the council has published new data since the last run. If nothing has changed, the job exits without touching the database. When new data arrives, only the changed rows are updated.

Council open-data portals vary in how often they publish updates — typically anywhere from daily to weekly. Kerbside reflects whatever cadence the council uses.

Per-address accuracy

Most properties in a postcode share the same collection schedule, but exceptions exist — a block of flats served separately, a road split across two rounds. Kerbside tracks both the majority schedule for a postcode and the exceptions, so the data is accurate at the individual address level, not just the postcode level.

City data

Each city’s data is isolated so an update or issue with one city cannot affect another. See Cities for the list of supported cities and their data sources.