Musette For broadcasters

You already own the rider positions. Musette turns them into race state.

A cycling feed gives you coordinates and timestamps. What a viewer wants is the race: how far the break is ahead, who is in it, which group a rider has just lost, whether the gap is coming down. Musette derives that — gaps, group composition, splits, who is with who and how it is changing — from positions alone, and renders it live and on replay. It is a live, public, working product, not a prototype.

What it needs from you

Rider positions and timestamps. That is the load-bearing input, and your production already ingests it — you need it for your own on-air graphics. A course polyline with elevation, and the rider and team roster, complete the picture. Native cadence of roughly one sample per rider every six seconds is enough; nothing needs resampling or densifying before it reaches us.

Classifications and official results are used where you have them, and degrade gracefully where you don't. The data interface states exactly what is required, what is optional, and what is derived.

What it produces

• Race state — live gaps between every group, group composition as riders join and are dropped, splits as they happen, and the whole classification picture moving with the race.
• Two views of it. A 3D reconstruction of the road for the moments that carry emotionally, and Radio — the whole race on one flat screen, every group and every gap at once. Radio is the one that answers "what is happening everywhere", and it is the one no broadcast can cut to.
• In your brand, in your app. Colours, type, logo and wordmark are configuration, not a fork. Every surface re-skins from one file.

Deployment shapes

Proof

It exists and it is running. Both of these are public, ungated, and open in a browser.

Talk to someone