Home· OTTO · Paddock· OTTO 1· TRACE· TRACE · Fleet· Team portal demo· Owner app demo
OTTO · Paddock — for teams & race programs

Your onboard feed hits the pit wall
before it hits the broadcast.

A quick-release race kit that moves between cars — front and rear camera pods, a sealed telemetry box, dual-antenna GNSS — with a bonded LTE uplink built in. Live video and timing to the pit wall and to your fans, from the same box that does the engineering. No extra box, no separate vendor.

~1.5 s glass-to-glass vs broadcast's 5–8 s $8,500 per car · race spec, everything included $500 per car / month · uplink + fan stream + platform quick-release — moves between cars CAN / ECU listen-only

Everything below is running in the demo right now — the actual software, seeded with a three-car GT4 test day. Start with the uplink ↓

The headline feature

LTE live streaming, built into the box

Race spec drops the silence rule: active fan cooling for sustained flat-out duty (race cars are loud anyway), and a built-in LTE uplink that streams live video and timing to the pit wall and your fans — included, from the same box that does the engineering. Two modems, two carriers, bonded into one stream off the car.

Uplink · bonded dual-modem, live from the cars running in /demo

1.58s
Glass to glass · pit wall
OTTO pit wall1.58 s
Broadcast TV6.4 s
The pit wall sees the car 4.8 s before the TV audience does. Broadcast glass-to-glass runs 5–8 s; this stack holds 1.4–1.9 s over public LTE.
Two modems, two carriers, one stream. A racetrack is the worst RF environment there is — tens of thousands of phones on the same towers and a car crossing cells at speed. Bonding is why the feed survives it: when one carrier collapses the other takes its share inside a second, and the picture never breaks. Timing, onboard video and CAN all arrive on the same uplink — one link off the car.

Fan-out · one uplink, many viewers

CAR #07 — quick-release camera pods, 2 cams + CAN + GNSS
bonded LTE uplink · 12.4 Mb/s · the car sends it once
OTTO edge — de-jitter, transcode, fan out
car-side bandwidth does not move with viewer count
Pit wallWEBRTC1.58 s
Team portalWEBRTC1.9 s
Fan streamHLS6.5 s
Add ten thousand fans and the car still sends 12.4 Mb/s — the edge does the multiplying, so the pit wall stays sub-2 s while the public feed runs on standard HLS with no viewer ceiling.

One link off the car

Timing, onboard video and CAN share the same bonded uplink. Nothing else to mount, power or pay for.

No second vendor

The streaming box is the engineering box. The kit that coaches your driver is the kit that feeds the broadcast.

One subscription

$500 per car per month carries the live uplink, the fan stream and the whole platform — covering the team and the stream together.

The pit wall is a screen

Not a separate product — a view in the portal, with telemetry streaming in from every running car.

The uplink monitor, the fan-out and the pit wall are all live in the demo — watch a carrier drop and the stream hold. Watch it run →

The live pit wall

Telemetry beside the radio, in the same room

The pit wall is a screen in the portal, not a separate product: telemetry streaming in from every running car — sectors, tire and brake temps, fuel — sitting beside the radio channel where the race engineer, the data engineer and Otto call the session between them.

01Every running car, one board

Sectors, tire and brake temps and fuel stream in from each car on the same bonded link that carries the video.

02Otto is on the channel

The AI race engineer sits in the radio thread with your engineers, answering from what's on the board in front of it — not from a car in general.

03Ahead of the broadcast

At 1.4–1.9 s glass-to-glass the wall sees the incident before the TV feed does. That's a call you can still make.

04Fans on the same feed

The public stream comes off the same uplink — no extra box, no separate vendor, no second production truck.

The live view — onboard video, live timing, the uplink monitor, the pit computer log and the pit radio — is open right now. Open the live pit wall →

Race day

Live coaching on test days. Log-and-debrief when it's sanctioned.

Live driver aids are prohibited in most competition classes. We're not going to pretend otherwise — so Paddock is built around the rule instead of against it. Teams get the data either way.

Class-rules honest

Live aids are for testing and practice — where the speed is actually found

When it's sanctioned, Otto runs silent record-only where your rulebook allows onboard logging, or comes off the car in two minutes where it doesn't. Then everything syncs, and the debrief writes next week's test plan.

Test & practice days

Full live coaching in the car — deltas, braking points, and traffic called out while the driver learns the track.

Race weekends

Live aids off, logging on. Every lap, every channel, every camera captured to the box and synced in the paddock.

Where logging isn't allowed

Quick-release means the whole kit comes off the car in two minutes — no bodywork to undo, no fitment to redo afterwards.

Either way, you get the data

Everything syncs the moment the car is back in the paddock, and the debrief engine goes to work on it.

Class-rules honest: live driver aids are prohibited in most competition classes — so Paddock runs live coaching on test days and switches to log-and-debrief for sanctioned sessions. Teams get the data either way.

Listen-only, always. The box reads OEM CAN or an aftermarket race ECU stream directly — nothing we do can touch how the car runs.

The hardware

The same brain, on a quick-release mount

Race cars don't get bespoke pods. Paddock ships on quick-release mounts — cameras, box and antennas come out in minutes and move to the next car. One kit follows the driver, the chassis, or the trailer, whichever makes sense that weekend. No chassis-specific bodywork means no fitment wait.

OTTO. OTTOMOTIV3. DUAL GNSS — TRUE HEADING FINNED BODY + FAN RACE-DUTY COOLING STATUS LIGHT CAN · READ-ONLY
The telemetry box — sealed, race-duty build,
Jetson-class compute at ~20 W
OTTO. QUICK-RELEASE MOUNT OUT IN MINUTES SONY LOW-LIGHT SENSOR STATUS RING — REC · SENTRY · OFF PP-CF BODY — MATTE CARBON, HEAT + UV STABLE CABLE EXIT
The camera pods — front + rear,
quick-release, matte carbon finish

In the case

  • Quick-release mounts — cameras, box and antennas out in minutes
  • Two camera pods — front and rear
  • Sealed telemetry box — machined aluminum, industrial-temp storage
  • 7″ OTTO 1 Display — pit-ready, sunlight-viewable
  • Transit case — black anodized aluminum, laser-etched unit number, custom foam for every component

What's inside it

  • Jetson-class compute — continuous object tracking on ~20 watts, running the spotter onboard
  • Dual-antenna GNSS — true heading, real slip angle, not an estimate
  • Bonded LTE uplink — two modems, two carriers, one stream
  • Active fan cooling for sustained flat-out duty — race spec drops the silence rule
  • Works offline — satellite positioning, everything captured to the box

How it reads the car

  • OEM CAN or an aftermarket race ECU stream, directly — CAN-FD tap
  • Listen-only, always. Otto reads your car and never writes to it — nothing we do can touch how the car runs
  • Every car's trims, temps and pre-code warnings in one fleet-health view — catch the failure in the trailer, not on lap three
  • Between cars it lives in the transit case — the crew knows what's missing at a glance
Dual-antenna GNSS — real slip angle Jetson-class compute — ~20 W CAN-FD tap — listen-only, tune untouched Active fan cooling — race duty Industrial-temp storage PP-CF pods — heat + UV stable 7″ OTTO 1 Display — sunlight-viewable
Paddock portal

Every car, every session, one screen

Units sync the moment they hit paddock WiFi. The engineer opens a laptop and it's already there — no card readers, no per-car software, no waiting on a data guy.

paddock.ottomotiv3.com
The fleet
Car 24SESSION LIVE
Car 08SYNCED · 12M AGO
Car 411 WARNING
SpareIN THE TRAILER
Session
Practice 234 LAPS

Practice 2 — driver comparison

BEST 1:27.91 · CAR 24
DRIVER A1:27.91
DRIVER B1:28.44
DRIVER C1:29.02
S1
28.9
S2
31.2
S3
27.4
THEORETICAL
1:27.12
Otto: Driver B loses it all in sector two — he's lifting where A is flat. Two tenths sitting there.
Car 41 — oil temp climbing 4°C per session across three runs. Nothing thrown, but worth a look before the race.
Auto-sync in the paddock — no cables Driver vs driver, corner by corner Plain-English debrief in minutes Fleet health across every car Export raw data — it's yours
The debrief engine — your AI race engineer

Driver-vs-driver overlays in plain English, minutes after the session

Not that night, not next week. "P2 gains it all in sector two — he's flat where you lift." The engine writes next week's test plan out of what actually happened this weekend, and the AI race engineer answers from your session — with your numbers in the answer, not a car in general.

Driver vs driver

Corner by corner, in language a driver can act on. The overlay says where the time went and who has it.

Fleet health

Every car's trims, temps and pre-code warnings in one view. Catch the failure in the trailer, not on lap three.

Ask it anything

The AI race engineer reads the session that's loaded — laps, channels, best lap — and answers out of it.

Your data, exportable

Raw export, any time, in open formats. It's yours.

The portal is open right now, loaded with a three-car GT4 test day across six real circuits. Open the team portal demo →

The circuits

Six real tracks — with the hills left in

The portal doesn't run on a generic loop. It runs on layouts you actually race, with the real corner names and the real elevation profile of each one. The lap model reads the grade at every point — so climbs cost acceleration and descents cut braking capacity, exactly like they do in the car.

WeatherTech Raceway Laguna Seca — the Corkscrew Circuit of the Americas — T1 up the hill Michelin Raceway Road Atlanta — the downhill esses Watkins Glen International — the uphill Esses Sonoma Raceway — the drop to T7 Road America — the Kink

01The hill is in the physics

Every track carries a distance-to-height profile, and the speed model solves against it. An uphill stop and a downhill stop don't come out the same — because they aren't the same.

02Brake references are computed

Ask about a corner and you get brake distance, entry and apex speed, and the height change through the zone — solved by the model for that car on that profile. Nothing is read out of a track guide.

03Corners have names

The Corkscrew, the Carousel, Canada Corner, the Bus Stop, the Boot. Otto talks about the lap the way your driver does, not in turn numbers off a map.

04It shows its work

The elevation strip sits under the trace, so you can see the same climb the model is braking against. Disagree with a number and the profile's right there to argue with.

AI race engineer · Circuit of the Americas
T1: brake reference ~176 m out, 218 → 64 km/h. Uphill zone, +14 m — the hill does some of the braking for you, so you can go deeper than it feels.
AI race engineer · Sonoma Raceway
T7: brake reference ~152 m out, 191 → 64 km/h. The zone drops 7 m and the car goes light — take the marker earlier than it feels.

Those two references came out of the solver, not a spreadsheet. Switch circuits in the portal and every number on the page — brake points, sector splits, the theoretical lap — is recomputed for the new profile. Go pick a track →

Bring your own logger

Keep the logger you already own

Nobody's asking you to bin a RaceBox or relearn a toolchain to try this. Export what you already record, drop the file into the portal, and it's parsed in seconds — laps, channels and best lap, straight into the AI's working memory. Ask about it one view over and the answer comes back with your numbers in it.

Imports today

  • RaceBox / RaceBox Pro — CSV export
  • MoTeC i2 — CSV export
  • AiM RaceStudio — CSV export
  • VBOX Circuit Tools — CSV export
  • Garmin Catalyst — session CSV
  • Plain CSV too — if it's tabular, it gets read

What comes back

  • Laps split automatically, with the best one called out
  • Channels found by name — speed, RPM, throttle, brake, gear, g, tire and brake temps, water, oil — min, average and peak on each
  • Sample rate and session length read off the file, and the logger identified from its own fingerprint
  • Parsing happens in your browser. Only the short digest is ever sent anywhere — the raw file doesn't leave your laptop
  • Typed debriefs and pasted stint notes land in the same place. Notes are data too

Coming PILOT — NOT SHIPPING

  • Direct MoTeC and Bosch ECU feeds — no export step at all
  • Direct CAN from Link, Haltech and ECUMaster
  • These are not shipping yet. They go to pilot teams first — if you want to be one of them, say so at the team desk

No file handy? The portal will generate a sample RaceBox export and run it through the same parser. Try the import →

The gap

Everything on the market does one third of the job

Nobody sells a factory-clean install that talks to you and is also your dashcam.

CapabilityRaceBox / AiMGarmin CatalystDashcamOTTO
Real telemetry + GPSYesYesYes
Live voice coachingYesYes
Looks like it came with the carSuction cupBulky podWire down the glassBuilt per chassis
Doubles as a daily dashcamYesYes
Engine health / pre-code warningsYes
Measured slip angle (drift)Yes
Radar threat integrationYes
Auto-edited clips for socialsYes
Gets better after you buy itMonthly OTA

Scroll the table sideways for the OTTO column →

None of which means you have to pick a side on day one — the team portal reads their exports, so you can run whatever you own today and still get the engineer.

The trade

Bring your history. Otto learns your cars overnight.

Most teams are sitting on years of data doing nothing — old session logs, setup sheets, lap times from tracks you've run a dozen times. Hand it over on day one and Otto starts smart instead of starting blank.

A genuinely two-way deal

You get an AI engineer that already knows your program. We get the one thing money can't buy.

A coaching system is only as good as what it's seen. Ours could spend a year learning from scratch — or start from your archive: every stint, every setup change, every lap at every circuit you've run. Import it once and the coach shows up already fluent in your cars, your drivers, and your tracks.

What you dump in

Old session logs — MoTeC, AiM, RaceBox, VBOX, Catalyst, plain CSV — through the same importer that's live in the portal today, plus setup sheets, tyre and fuel notes, historic lap and sector times, driver rosters.

What you get back, immediately

Benchmarks against your own history instead of nothing. "That's your third-best S2 ever." Setup-to-laptime correlations across seasons you never had time to analyse.

What it becomes by round three

A coach fluent in your specific cars — knowing that car 41 always runs hot late in a stint, that this driver brakes early at this circuit, what your fast setup looked like last year.

What we get

Real racing data at a volume no startup starts with. It makes the coaching sharper — for you first, then for everyone after you.

Your data stays yours. You own it, you can export all of it any time, and you can delete it. Anything that improves the shared model is aggregated and stripped of identity — no team's setups, times or telemetry are ever visible to another team. That's in the agreement, not just the pitch.

Founding programs get more than a discount: the cars you run shape what the coach becomes, and the features you ask for get built first.

Timing

Why this is buildable now and wasn't three years ago

Three parts got cheap at the same time. That's the window.

01Dual-antenna GNSS got affordable

True vehicle heading used to mean motorsport-grade equipment. It's now a module you can buy — which is the entire reason real slip angle is possible at this price.

02Edge AI runs in a car

Vision inference used to need a workstation. A Jetson-class module now does continuous object tracking on 20 watts, passively cooled, in a box under a seat.

03Voice AI became conversational

The coach only works if it talks like a person. That stopped being science fiction very recently — and it's the part every existing data logger still can't do.

04The CAN work is already public

A decade of tuning-community reverse engineering means supported platforms are verification work, not invention.

The plan

Race teams first. Then everyone else.

Not because the street product is an afterthought — because this is how you make it good.

01The hardest users first

Race engineers tell you exactly what's wrong, immediately, without being polite about it. That's the feedback loop you want before a single street car gets one.

02Data no enthusiast can generate

Thousands of hard laps across multiple cars and drivers in a season. The coaching gets sharpened on real racing, not commutes.

03Proven where it's brutal

Heat, vibration, curbs, and mechanics who baby nothing. Survive a season in the paddock and your daily is easy.

04Ready soonest

Quick-release mounting means no per-chassis wait — teams can be running before the first consumer platform exists. Limited first-season slots.

Built by drivers, for drivers.
Pricing

One kit price, one subscription — covering the team and the stream

Target positioning; final pricing set after the first production run. Limited slots for the first season.

The kit FIRST SEASON — LIMITED SLOTS
$8,500 / car · race spec
Everything included — no options list, no upsell to make it work:
  • Quick-release mounts that move between cars
  • Two camera pods — front and rear
  • Active fan cooling · race-duty build · sealed telemetry box
  • 7″ OTTO 1 Display — pit-ready, sunlight-viewable
  • LTE live streaming built in — live video and timing to the pit wall and your fans, no extra box, no separate vendor
The subscription
$500 / car / month
Carries the live uplink, the fan stream and the whole platform. One subscription covers the team and the stream.
  • The bonded LTE uplink off every car
  • The fan stream — no viewer ceiling
  • The portal, the debrief engine and the AI race engineer
  • Fleet health across every chassis in the trailer
  • Fleet rates from 3+ cars — quoted per program
What that adds up to

The streaming vendor, the logger and the data engineer are all in the one line

Live coaching on test days, silent record-only when sanctioned, driver-vs-driver debriefs minutes after the session, fleet health across every chassis, and the live pit wall with the fan stream coming off the same link. Fleet rates from 3+ cars, quoted per program.

No chassis-specific bodywork means no fitment wait — teams can be running before the first consumer platform exists. Limited slots for the first season. Pricing shown is target positioning, not a quote.

Straight answers

The questions teams ask first

01Is this legal in our class?+
Live driver aids are prohibited in most competition classes — so Paddock runs live coaching on test days and switches to log-and-debrief for sanctioned sessions. Where your rulebook allows onboard logging, Otto runs silent record-only; where it doesn't, quick-release means the kit comes off the car in two minutes. Teams get the data either way.
02Can it touch the ECU?+
No. The box reads OEM CAN or an aftermarket race ECU stream directly — listen-only, always. Otto reads your car and never writes to it. Nothing we do can touch how the car runs.
03Do we have to bin the logger we own?+
No. RaceBox, MoTeC i2, AiM RaceStudio, VBOX Circuit Tools, Garmin Catalyst and plain CSV all import today — parsing happens in your browser and the raw file doesn't leave your laptop. Direct MoTeC/Bosch ECU feeds and direct CAN from Link, Haltech and ECUMaster are not shipping yet — they go to pilot teams first.
04Who owns the data?+
You do. You can export all of it any time, in open formats, and you can delete it. Anything that improves the shared model is aggregated and stripped of identity — no team's setups, times or telemetry are ever visible to another team. That's in the agreement, not just the pitch.
05Does the kit fit our cars?+
Race cars don't get bespoke pods. Paddock ships on quick-release mounts — no chassis-specific bodywork, so no fitment wait. Swap it into the spare, the test mule, or a different class car the same afternoon. One kit follows the driver, the chassis, or the trailer.
06When can we start?+
Quick-release mounting means no per-chassis wait — teams can be running before the first consumer platform exists. Slots for the first season are limited, and fleet rates start at 3+ cars. Tell the team desk what you run.
Team desk

Talk about a Paddock program

No deposit, no card. Tell us what you run and you'll hear back from the person building it — usually within a day.

Race programs

Talk about a Paddock program

Quick-release units across your cars, fleet rate per unit plus a team subscription, quoted per program. Limited slots for the first season.

See it first

Or just open the demo

A three-car GT4 test day on six real circuits — sessions, laps, telemetry traces, driver-vs-driver analysis, file import, the live pit wall and an AI race engineer that answers from your session. Not a video — the actual software.

Live pit wall + uplink monitor Import your own export Ask the race engineer
Open the team portal demo →