Race teams
Open the MoTeC and Pi Toolbox files your loggers already write, and lay them over the laps from your simulator.
Build workbooks of your team’s sim and real-car data and work through them together. MoTeC, Pi Toolbox and VBOX files open as they are beside the laps your drivers turn in the sim, and agentic and decision AI help your engineers find the time and make the call. All under the company sign-in, on a stack of your own.

Open the MoTeC and Pi Toolbox files your loggers already write, and lay them over the laps from your simulator.
Every driver’s laps, the live wall and stint planning, under one company sign-in your staff already have.
Sim sessions and track days in one library. Coaches review both on the same screen.
Bring the logger files home from a track day and compare them with practice in the sim.
Lay out sheets of traces, track maps, onboard video, lap trends and channel statistics, and write math channels for anything the logger didn’t record. Save a sheet as a template and start every outing from it.
| Pane | For |
|---|---|
| Traces | Any channel against distance, laps overlaid on one cursor |
| Track map | Where on the lap, coloured by any channel |
| Onboard video | Synced to the data, from the sim or your own camera |
| Lap trend and statistics | How a channel moves lap to lap and run to run |
| Math channels | Your own channels, built from the ones recorded |
Real laps sit in the same library and the same workbook as sim laps. Overlay a simulator lap on the car’s lap from the weekend, on one cursor and one distance, and see where the sim is quicker, slower or simply different.

Comment on a corner or a chart, reply in a thread and resolve it when it’s sorted. Everyone in a workbook sees each other’s pointers move, a share link opens exactly what you see, and during sim sessions the whole crew watches the same live wall.

Drop in a MoTeC .ld with its .ldx, a Pi Toolbox .pds, a VBOX .vbo or a logger’s CSV export. Laps come from the file’s own beacons or lap markers, channels map to standard names in their units, and every file gets a report of exactly how it was read.
| File | From | Laps from |
|---|---|---|
| .ld + .ldx | MoTeC | The .ldx beacons, else a lap channel or GPS |
| .pds | Pi Toolbox | The file’s lap markers or events, else GPS |
| .vbo | VBOX, RaceBox, RaceChrono | GPS, at a start/finish line |
| .csv | Logger exports, AiM included | A lap column, else GPS |
Muretto is an MCP server, so Claude or any MCP client can query your sessions, laps and telemetry with a read-only key, and work through them with your engineers.
| Tool | What it reads |
|---|---|
| Sessions and laps | Your sessions, their laps and your personal bests |
| Lap telemetry | Any lap’s channels, and two laps compared corner by corner |
| Race context | A race’s field, hazards, pit loss and pit window |
| Field pace | Where each car’s pace sits in its class |
Staff sign in with their work email through Okta, Microsoft Entra ID or any SAML identity provider. Take someone out of your identity provider and they can no longer sign in to Muretto.

Your team’s telemetry, video and setups live on a stack of your own. Nothing is pooled with other drivers, and nothing is shared unless one of you shares it.
| Private Cloud | Engineering Partner | |
|---|---|---|
| Runs on | A stack of your own | A stack of your own |
| Region | Your choice | Your choice |
| Shared prediction models | Never pooled | Never pooled |
| Sign-in | Your SSO | Your SSO |
| Engineering analysis | Your team runs it | Done for you |
MoTeC .ld and .ldx, Pi Toolbox .pds and VBOX .vbo open as they are. Logger CSV too.
Sim and real laps in one workbook, on one distance and one cursor.
Grip limit and balance fitted from each lap, so the sim and the car compare like for like.
SAML single sign-on with Okta, Entra ID or your own provider.
Comment threads, live pointers and share links in every workbook.
An MCP server for Claude or any agent, read-only, and every lap exports as CSV.
Tell us about your cars, your simulator, your loggers and who needs access.
Your sign-in, your own stack, and one of your own logger files opened together.
Drivers record in the sim. Engineers drop the car’s logger files in after each run.
Both run on a stack of your own. Your team does the analysis, or we do it with you.
Your team’s workbooks and data on a Muretto stack of your own. Nothing is pooled with anyone.
We build the workbooks and do the analysis beside your engineers, on your Private Cloud.
Enterprise is priced to your programme: talk to us for a quote. Engineers, coaches and crew are included on every tier.
Tell us about your programme and we’ll set up a demo with one of your own logger files beside your sim laps. We reply within two working days.
Or email enquiries@scorsa.io
No. The models propose and score; your team makes the call. Every number they quote is checked against your data.
Yes. Muretto is an MCP server: point Claude or any MCP client at it with a read-only key, and it can query your sessions, laps and telemetry.
MoTeC .ld with its .ldx, Pi Toolbox .pds, VBOX .vbo, and CSV exports from loggers, AiM’s included. Real-car data comes in from the files after a run; there is no live real-car telemetry.
Yes. Real laps sit in the same library and workbook as sim laps. Overlay them on one distance and one cursor, read the delta corner by corner, and compare grip and balance in the Car Model pane.
Any SAML 2.0 provider, Okta and Microsoft Entra ID included. Your staff sign in with their work email, and we connect your provider during setup.
No. Enterprise runs on a stack of your own, so nothing is pooled with other drivers. Telemetry, video and setups are never shared outside your team unless one of you shares them.
On a database and storage of your own, in the region you choose: Australia, Europe or the United States.
Muretto records from iRacing, Le Mans Ultimate, rFactor 2, Assetto Corsa Competizione, Assetto Corsa EVO, Assetto Corsa and F1 23–25. iRacing is fully supported. Le Mans Ultimate, Assetto Corsa EVO and Assetto Corsa are in beta: their data records, streams and analyses, without iRacing’s sim-specific features. rFactor 2, Assetto Corsa Competizione and F1 23–25 are in alpha: not yet verified to work consistently. The available channels vary with each simulator.
Every lap kept with telemetry and onboard video. Overlay any two and see where the time went.
See howEvery team car on one live wall, with fuel, stints and pit calls for the long race.
See howSell setups, reference laps and coaching. Review your students’ laps on the real telemetry.
See how
Tell us about your cars, your simulator and your staff, and we’ll set you up.