RaceOSPlan the physical race before race day
Upload a surveyed course and record planned timing, hydration, medical, camera, display, sponsor and network-relay nodes in one event model.
Race intelligence, connected
See the race as one living system.
RaceOS connects the surveyed course, timed bib crossings, field devices, people, safety and race-day decisions in one operational picture—from first layout to final replay.
Confidence at a glance. See which runner positions were just confirmed at a timing point and which are progressing between checkpoints.
RACE CONTROL MODEL
GPX COURSE REPLAYREAL GPX PROJECTIONHalf-marathon course projection360 supplied track points · 21.1 km replay
Timing-point confirmed Progressing on course Field infrastructure
TIMING SOURCETIMED BIBScheckpoint crossings
FIELD DEVICESENROLLED / LIVEreal event data only
COURSE STATESOURCE-LABELLEDlive, estimated or stale
One event modelPlan → deploy → operate → replay
Confidence-awareRecent confirmations stay visible
Field-awareDevices, teams and runners in context
Official timing protectedEstimates never create results
Not a decorative map
The operating layer between what you planned and what is actually happening.
Most race systems separate timing, maps, devices, staff and messaging. RaceOS keeps their event identity and physical location connected, so an operator can move from a signal to the right action without reconstructing context across tools.
One course, multiple operational lenses
Heatmaps, crowd movement and traffic planning—spatially connected.
Follow movement through every course zone.
Accepted crossings build zone occupancy and average pace between timing points. Race control sees how the field is progressing without turning an estimate into an official split.
SUPPLIED GPX COURSECrowd movement
Course-shaped overlay Event-scoped data Source-labelled view
Inspect the evidence RaceOS actually received
Source-labelled position estimates, checkpoint crossings, enrolled-device heartbeat and recorded incidents appear only when their real feeds provide data.
Respond without losing event context
Device alerts and recorded incidents remain attached to the same event and course workspace used by operators.
Replay recorded race state
Historical position records can be replayed separately from the live view; timing exceptions remain available for human review.
A richer race picture
Every layer helps the team make a better decision.
Runner progress, field infrastructure, operational health, crowd context and replay come together without turning the map into noise.
Timing
Timed bib crossings anchor official times and checkpoint splits.
Field position
Between mats, progress is estimated along the surveyed course and visibly labelled as confirmed, interpolated or stale.
Infrastructure
Planned readers, displays, cameras, mesh, medical, hydration, barricades, sponsor nodes and drone paths share one spatial model.
Operational health
Heartbeat, battery, connectivity, alerts and correlated incidents reveal whether the physical system is actually working.
Crowd intelligence
When field sensors are deployed, zone occupancy and separately labelled anonymous density can add context without becoming timing data.
Predict and replay
Forward projections are visually separate from observed state; historical replay is explicitly marked as non-live.
How runner movement works
Timed bib crossings anchor the journey.
Each accepted timing-point crossing creates an exact moment at a known course distance. Between those points, RaceOS uses the surveyed route and the runner’s recent pace to present a smooth, confidence-labelled race view.
01
CONFIRMEDTimed bib crossing at a known checkpoint
02
INTERPOLATEDBounded course estimate from the last confirmed pace
03
STALEToo old to present as a reliable live position
From control room to finish line
Run the event from one connected command layer.
Explore a listed race, or talk to RaceOS about mapping and operating your next event.