Live traffic. One line of code.

Roads coloured by how freely traffic is flowing, plus live incidents and roadworks, built from official national road-authority data, normalised into one consistent schema, and painted onto your map client-side. No traffic-tile backend, no second vendor: it draws from the same API key and unit pool as maps, geocoding and routing.

Official road-authority data

Public European road-authority feeds (incidents, roadworks, closures and per-segment speeds) normalised into one schema. Privacy-friendly by construction: no tracking-SDK probe data.

Cheap by design

Static geometry loads once; a small live-state file refreshes about once a minute and joins onto the roads on the client. A refresh moves a few hundred kilobytes, not a tileset.

One unit per map session

The traffic layer adds one unit per map view on top of the basemap session, drawn from the same monthly pool. No separate traffic plan, no per-tile metering.

Turn it on.

The map above is the Rijwind SDK with traffic: true. The SDK bundles MapLibre, opens the tile session, loads the road geometry, and keeps the live state fresh; you enable one flag. Toggle it at runtime behind your own button with map.enableTraffic().

Get an API key Read the docs

map.ts

import { Map, config } from '@rijwind/sdk';
import '@rijwind/sdk/style.css';

config.apiKey = 'rw_live_•••';

const map = new Map({
  container: 'map',
  center: [5.1, 52.1], zoom: 7,
  traffic: true,
});

Everything on one key.

Maps, geocoding, routing, static images, elevation, and now live traffic. One API key, one unit pool, European hosting.

Start building See pricing