A neutral road event network
Real-time road incidents, in one API.
Relay brings official road feeds and the reports of every connected app into one format, delivered in real time. A neutral network: it does not compete with your product, it feeds it.
- 0
- incidents in production
- 13
- event types
- €0
- to publish
official feeds, right now · sandbox excluded
one format, whatever the source
always, on every plan
Every point on the plate is a live event, read from the API while this page rendered — solid for production, faint for the test sandbox.
What Relay does today, and what it becomes
The network starts from official public data. It grows with every app that connects to it, and that is what we are building with our first partners.
Official road feeds, ready to integrate
The French national feed is already on the network: congestion, accidents, stopped vehicles, obstacles, dangerous weather. Relay turns that European standard (DATEX II) into one simple format and delivers it in real time. You integrate a format, not a source per country.
- 0 incidents in production right now
- An API to read, a real-time stream to receive
- Free self-service key, test sandbox, published prices
The reports of everyone who connects
What no official feed carries, your users see. Every connected app publishes what its drivers report and receives what everyone else’s drivers report. A report is only confirmed by distinct vehicles, and it expires on its own.
- Police check
- Speed camera · Mobile camera
- Infrastructure fault
- Roadworks · Emergency works
- Road damage · Pothole
- Road damage · Sinkhole
One integration, the whole network
Fast integration
One contract, one format, a few HTTP calls. No connector to maintain per source or per country: when a source joins the network, it arrives on the same stream with nothing to change on your side.
Pooling
Your users report what they see, and so do every other app’s. Everyone receives the sum. Publishing is free, always: the more contributors, the more the network is worth to each.
Independence
Relay has no app and no drivers to take from you. Your data does not feed a competitor, and nothing on the network says which organisation published an event.
One report, delivered live
Publish an event from this panel and watch it arrive. Each clip runs from the moment the event was created to the moment it expires: a road incident has a lifetime, and Relay manages it for you.
GET /v1/stream?lat=48.8698&lon=2.3078&radius=8000Quiet on this disc right now. Publish one and a clip appears at the playhead, as long as the type’s time to live.
Publish an event and the round trip is timed in this browser — one clock, from the click to the moment it returns down the open stream.
1 000 ms · the published commitment
This panel publishes into the sandbox, the test network every integrator gets — never into production. The incidents already on the tape are real, from the French national road feed. Open the live map
Relay lives inside our partners’ products
A fleet console, a navigation app, an in-car screen: three products of the kind that embed Relay, subscribed to the same stream as the panel above. Publish an event up there and it appears in all three on the same tick.
Road events on your operating area
via Cudatus RelayConnecting to the stream.
Connecting to the stream.
Connecting to the stream.
A fleet operations console
The platform owns the vehicles, the routes and the customers. Relay supplies one panel: what is on the roads they run, queues first, because a queue is what turns into a missed delivery slot.
A driver-facing app
The app owns the map and the route. Relay supplies what is on it — what is next, how far, how bad.
An in-vehicle display
Homologation, functional safety and cybersecurity review run in years — which is exactly the timescale a frozen wire contract is designed to survive. An integration programme rather than an API key.
Cudatus builds none of these. All three are drawn in deliberately anonymous grey, so the only coloured thing inside any of them is the data Relay puts there — which is exactly the shape of what we sell. A quiet road renders quiet — in all three at once, off the same tick. © MapTiler · © OpenStreetMap contributors
Where you plug in
Find your row, and read how you connect.
Telematics platform editors
One POST, one streamYou run the platform a few hundred fleets log into, you have an API and you have developers.
Your boxes already detect what Relay wants — harsh braking, prolonged immobilisation outside a delivery stop, impact detection. The raw material is on your servers; what it costs you is one HTTP call. We never ask for trajectories, only the point events you already derive.
Navigation and mobility apps
Subscribe and apply deltasYou put a route in front of a driver, and a hazard on it is worth more the earlier it lands.
Subscribe to a disc around a position and apply the deltas — one stream, one contract, no per-source integration. An itinerary is covered by subscribing discs along it, each one the same call.
Road operators and public authorities
DATEX II in, JSON outYou already publish DATEX II, and you already asked whether we speak it.
DATEX II in, JSON out. We consume the European standard and serve a real-time developer API over it — we are not replacing it and not competing with it. Your feed is brought up as a connector; the French national feed runs on one already.
Fleet managers
Through your platformA truck stuck behind an accident is a missed delivery slot, and a detour is not trivial at 40 tonnes.
Through the telematics platform you already use, not through us. A fifty-truck haulier has no development team and should not need one: when your platform integrates Relay, your fleet gets the network with nothing to build on your side.
Carmakers
Integration programmeYou have millions of connected vehicles giving data to a supplier who competes with you on navigation.
The reciprocity is the argument: what your fleet publishes comes back as every other participant's events, instead of funding a service you then buy back. Homologation, functional safety and cybersecurity review set this cycle in years — an integration programme rather than an API key, and the wire contract is frozen precisely to survive that timescale.
We are looking for our first partners
A few companies — telematics editors, navigation apps — for a 30-day pilot. You publish or consume real events, we work with you directly, and we measure together what the network brings you.
Free to start, and the prices are published
Publishing never costs anything, on any plan. What you pay for is reading the network.
Plain HTTP, documented
A REST API to publish and read, a real-time stream (SSE) to receive, a stable JSON format: fields are added, they never break an integration.