Apex ScoutRacing
Request access
Apex ScoutRacing
Request accessInvited sign-in

Understand the lap.
Choose the
next test.

Session analysis for race engineers. Compare runs, challenge driving and setup explanations, and choose one measurable next test.

Request accessInvited sign-in

Private early access. Start with a synthetic Jerez session.

Jerez · Fictional GT4 #27Synthetic scenario

Run B against run A

Median lap delta

+0.780 s

A02 / B02 · sector 2

+0.580 s

Run A, A02Run B, B02

Speed (km/h) · Lap distance (m), sector 2

Synthetic sector 2 speed traces. Dashed grey is run A lap A02, solid red is run B lap B02. Both slow through the corner between 2200 and 2600 metres.

Representative laps stay separate from run medians.

From evidence to a test

Driving, setup,
or both?

Inspect cited evidence and missing measurements. Correct the context, then generate a fresh diagnosis.

One next test

Hold the setup fixed. Repeat one driving cue on clean laps. Compare the corner window and run medians.

Example test wording. AI hypotheses require engineering judgment; the app does not establish causation.

Static preview of the synthetic Jerez workflow. Example test, no live AI result.Compare. Question. Test.

A useful answer
ends with a test.

Racing keeps comparison, corrected context, AI evidence and your next test in one private workspace.

  1. 1

    Compare the runs

    Inspect the laps. Exclude traffic when you decide it belongs outside the comparison. See the medians update.

  2. 2

    Challenge the diagnosis

    Inspect driving and setup hypotheses, their evidence and what is missing. Correct the context and generate a new analysis.

  3. 3

    Leave with a test plan

    Edit and save one change, what to hold constant, how to measure it and when to stop.

Read how it works before you ask.

Three product pages cover what Racing does today. Three guides cover the engineering method behind it.

Product

Session analysisCompare two runs and find where the time changed.AI race engineerDriving and setup hypotheses, each tied to evidence.Data ownershipWhat is stored, where, and who processes it.

Guides

How to compare two stints fairlyPick laps that can be compared.Driving or setup: separating causesRead the traces before changing the car.Designing one discriminating testOne change, held conditions, one measurement.

Design-partner roadmap, 2027 season

Planned with design-partner teams for the 2027 season. None of this is available today; today Racing runs one synthetic Jerez scenario.

  1. Planned, 2027

    MoTeC and AiM CSV import

    Bring your own logged sessions into the same comparison, evidence and test-plan workflow.

  2. Planned, 2027

    A per-team isolated model

    Each team's analysis uses a model trained only on that team's data. No cross-team training and no shared model.

  3. Planned, 2027

    Data ownership in writing

    Team data stays the team's, with export and deletion when a team leaves. How data is handled today

Bring the next test into focus.

Early product. Private access. One synthetic scenario to evaluate the workflow.

Request access