MAYA #12
Tony Kart Racer 401 RR
Team Garage
Every setup. Every heat. One trackside record.
Give mechanics a live view of the fleet, the conditions, and what is running on each kart. Start from a proven baseline, record every change, connect the session, and carry the right setup into the next heat.
Race-day control
The whole morning, in one operating view.
Check live conditions and fleet readiness, then open the kart that needs the next decision. Its baselines, today's heats, setup changes and assigned sessions are already together.
Conditions · Here
Open ›
94.8%Relative air density
Scattered clouds
Carb icing · Low
Carb icing · Low
Air22.4°C
Humidity58%
Wind9 km/h
Station1004 hPa
8-hour outlookWeather data provided by OpenWeather
Current Team vehicles
3 / 15
Ready
LEO #34
Kosmic Mercury RR
NOAH #07
KR2
MAYA #12Tony Kart Racer 401 RR
ReadySetupHistoryServiceDetails
HeatsBaselines
Start from a baseline
Dry · high gripWet setup
Heat 1 · Warm-up2 sessions
Rear sprocket 82 → 83
Dry · Normal grip · Air 22°C · Track 31°C
Heat 2 · Qualifying1 session
Rear track 1390 → 1400 mm
Dry · Rubbered grip · Air 24°C · Track 36°C
Two useful truths. Live conditions are fetched for where you are. Each heat also keeps the mechanic's own paddock readings — track state, grip, air and track temperature, humidity and pressure. They sit together without pretending they are the same measurement.
Between-run workflow
Start with intent. Finish with evidence.
Every heat is independent. The setup it started from is frozen as a snapshot, the changes belong to that heat, and the recorded session is attached only when the mechanic chooses it.
Choose the starting point
Begin from a named baseline, clone the last heat, or start blank. Nothing is guessed for you.
Record what is running
Capture the kart setup and the paddock conditions for this heat without rewriting any other one.
Connect the session
Assign the recorded session to the heat it actually used, then open its lap data and logger telemetry.
Build the next heat
Clone the setup forward, make the next change, and save a successful heat back to the baseline library.
The record behind the race day
The driver has a history. So does the vehicle.
The fast trackside workflow sits on top of a durable vehicle record: identity, readiness, service work, photos and the full setup history.
One current machine
Keep the kart, car or bike and its real chassis and engine identifiers beside the driver it belongs to.
Service history
Log inspections, repairs, engine hours or distance, next-service notes and supporting photos.
Replace without erasing
Archive an assignment with its reason. Its vehicle, service and setup history remains readable.
Restore with context
Bring an archived assignment back only when no replacement exists. The audit trail stays with it.
Access by role
Give the mechanic the trackside controls — not the private office.
Included with Teams. Each role gets the part of the workflow it needs, while private driver information and Team administration stay separated.
Owner
Full vehicle, service, archive and setup control across the Team, plus billing and Team administration.
Coach
Run the complete Garage and setup workflow without gaining billing or ownership controls.
Mechanic
See the fleet, sessions and telemetry; edit setups, heats and conditions; assign sessions and set readiness. Private CRM and broad vehicle or service edits stay closed.
Driver
See their own current and past Team vehicles. Teams can separately allow the driver to edit their own setup sheets.
Make the next setup decision before the next run.
Team Garage is included with Teams: live conditions, setup baselines, heat records, session links, readiness, service history and vehicle history in one trackside workflow.