Pilot partner programme
Build the network with its first partners
Today Relay delivers the official road feeds. What will make it a network is the reports of those who connect to it. We are looking for a few companies — telematics editors and navigation apps — for a 30-day pilot with one simple goal: measure what the network brings you, on your own data.
What we bring
Production API access
A production key for the length of the pilot, on top of the test sandbox. Publishing is free, always.
Direct support
You work with the team that builds Relay: a review of your integration, same-day answers, one named contact.
A say in what comes next
What you ask for during the pilot decides what we build next. You shape the network before it settles.
A measured report
At the end of the 30 days, a write-up of what the network brought you, measured on your own data.
What we ask of you
A technical contact
One person on your side who can make an HTTP call and tell us what gets in the way.
Publish, consume, or both
Publish the events your devices or your users already detect, or show the stream in your product. We never ask for trajectories, only point events.
Straight feedback
A short check-in each week, and a plain verdict at the end: what helps, what is missing, what does not work.
Thirty days, four steps
There is no price list for the pilot: the terms are discussed with each partner, from the first call.
1A 20-minute call
Your product, your data, what you expect from a road event network. We set the success criteria and the terms of the pilot together.
2Week 1 — integration
Self-service key, integration against the sandbox, then the move to production. We review your integration code if you want us to.
3Weeks 2 to 4 — in production
Your events flow, or the network's arrive in your product. We measure as it goes.
4The review
The numbers, your feedback, and a decision that is yours: continue, adjust or stop.
What the review counts
Measured during the pilot, on your real traffic, never on the test sandbox.
- Useful events received and published
- Geographic coverage
- Event freshness
- Duplicates and rejected reports
- Delivery latency
- Actual integration effort
What exists, and what the pilot builds
A pilot partner checks everything on day one. So here is the real state, unembellished.
- The French national feed (DATEX II), normalised and delivered in real time
- An API to publish and read, a real-time stream to receive
- Self-service keys, test sandbox, published prices
- Automatic confirmation and expiry of reports
- Reports from the first connected apps
- More countries, one connector at a time
- Whatever you tell us is missing
Your data stays yours on the network: nothing that circulates says which organisation published an event. Security in detail
Tell us who we are talking to
So our first reply is about your case rather than a round of questions, your message should tell us:
- 1Your company and your role
- 2Your product (telematics, navigation, fleet, other)
- 3How many vehicles or active users
- 4The countries you operate in
- 5What you want to do (publish, consume, or both)
- 6What road data you are missing today