Skip to content

Built around the driver and team

Practical race tools for the work teams actually do.

TeamManager exists because endurance racing asks small teams to coordinate like large ones, often with a patchwork of documents, overlays, voice calls and memory.

A dark endurance racing operations room overlooking the circuit
Concept artwork · placeholder. Real screenshots will follow.

We are building the tool we wanted before and beside the simulator.

Planning a long race is rarely the hard part. Keeping the plan useful when fuel changes, traffic appears and drivers swap is where context gets lost.

We are a small, focused product effort with direct experience of sim racing and endurance workflows. That keeps the work grounded: fewer speculative systems, more robust tools that help during an actual event.

01

Show what is known.

When race data is missing or uncertain, Race Engineer says so instead of guessing.

02

Keep each job clear.

Local Race Engineer is nearly ready and works on its own. TeamManager is in development for an upcoming Alpha: shared preparation, event planning and connected race context. Pre-Race Intelligence and automatic strategy adaptation are planned.

03

Build in useful pieces.

We ship and validate features around actual race work, then show clearly what is still in development.

YOUR PC / YOUR ENGINEER

What Race Engineer needs

Leave room for the simulator first. These are provisional sizing recommendations, not measured minimum requirements.

Windows & simulator
64-bit Windows 10/11 and iRacing for live race data. A microphone is needed for voice questions; typed questions remain an option.
CPU recommendation
A modern six-core processor, such as an AMD Ryzen 5 5600 or Intel Core i5-12400, is a provisional starting point. Faster cores and spare CPU capacity help when local voice processing runs alongside the simulator.
System RAM
Start with 16 GB total system RAM; 32 GB is recommended for more room alongside iRacing, overlays and local voice models. The Moonshine estimates below cover speech recognition only, not the complete app or simulator.
Downloads & disk space
Installer size varies by Alpha release. Optional Moonshine speech models add approximately 37 MB (Tiny), 122 MB (Small) or 237 MB (Medium) to download. Natural Radio has a separate optional model download after you enable it. Allow extra disk space for installation, updates and voice profiles.
Moonshine RAM estimate
Speech recognition only · approximate sizes
ModelModel filesRAM estimate
Tiny45 MB0.3–0.6 GB
Small142 MB0.5–1 GB
Medium269 MB0.8–1.5 GB
Estimates start from unpacked model size, then allow for runtime overhead, working buffers and speech context. They are not measured peak RAM figures. Moonshine is optional and experimental.
Performance during a race
Speech recognition, voice generation and optional Natural Radio share CPU and memory with iRacing. They may increase response latency or affect frame times on a busy PC; no FPS-impact figure is established. Try your setup in practice first, and start with a smaller speech model if headroom is limited.
Measurements still ahead
Real RAM, CPU, latency and frame-time measurements from opt-in machines are still pending. We will refine these recommendations when that evidence is available.
TeamManager connection
Optional for core local race features. Sign-in is required for the protected Alpha download and connected team features.

“A driver should be able to run a local engineer. A team should be able to prepare the race together.”

TeamManager product principle

Local Race Engineer is nearly ready. TeamManager is in development for an upcoming Alpha.

Plan with the team. Run the engineer locally.