Versus · the whole market, one table

"Have you heard of Garmin?" Yes. Here's the table.

Everything else on the market is one tool. OTTO is the whole race-engineering team, in the reach of your hand — race engineer, data engineer, driver coach and pit wall, in one system that reads the car, thinks, and talks back. Garmin Catalyst, RaceBox, AiM, VBOX, Apex Pro, the phone lap timers and every dashcam are good at one slice of the job. Each one is listed below with what it does, what it doesn't, and what OTTO does — no hand-waving, no "coming soon" dressed up as shipping. Where a competitor is better at something, it says so.

23 capabilities compared 8 products Every competitor's CSV export imports into OTTO today

Garmin, specifically ↓ Reads every other product's data ↓ The full matrix ↓ Fail-proof data ↓

Garmin Catalyst

Catalyst coaches from a GPS and a camera. OTTO coaches from the car.

Credit where it's due: Catalyst is the best standalone lap coach you can buy off a shelf. It is also, by design, blind to everything the car is doing.

What Catalyst does — and does well

A screen on the windshield that times you and talks

Real-time audio cues — "brake later here", played against its own optimal-lap model.
10 Hz GPS lap and sector timing, with an "optimal lap" stitched from your best segments.
Single front camera, video with data overlay, reviewed on the unit after the session.
Works on its own — no phone, no subscription, no install beyond a suction cup and a 12 V plug.

Where it stops

It only knows what a GPS puck can know

No vehicle data. No RPM, throttle, brake, tire or brake temps, fuel, or engine health — it never plugs into the car.
One car, one screen. No pit wall, no live stream, no team portal, no driver-vs-driver across cars, no history that learns your program.
Scripted cues, not thinking. Its lines are a fixed set triggered by GPS position. It can't be asked why, can't see the car, and can't compute brake references from the circuit's elevation. OTTO reasons over the live data and talks like a person on the radio.
A pod, not a fitment. Suction cup on the glass; it is not your daily dashcam, has no Sentry, no rear camera, no radar tie-in, and no sector beacons.
Feature set is what's in the box. Firmware updates, yes — new capabilities, no.

Cut and dry: Catalyst is a lap timer that talks. OTTO is a co-driver that reads the car, streams it to the pit wall in ~1.5 s, talks back in your language, doubles as the dashcam, and gets new features monthly. If a team already owns a Catalyst, they keep it — its session CSV imports into the OTTO portal today, so the archive comes with them.

Their data, our engineer

Every one of them is a walled garden. OTTO reads all of their exports.

Catalyst reads Catalyst files. RaceBox reads RaceBox. AiM reads AiM. A team that has run three loggers over five seasons has three archives that have never once been in the same room. OTTO's importer reads the CSV export from every one of them today — one export click in the vendor's own software, no re-logging — so the day a team signs, years of their own history become the baseline the coach benchmarks against.

What they read

Their own format. That's the list.

Garmin Catalyst — its own sessions, reviewed on the unit.
RaceBox, Apex Pro — the app opens its own logger's files and nothing else's.
AiM, VBOX, MoTeC — the desktop software will take a CSV in, but the unit and the app read only their own.
Phone apps — a few CSV layouts, none of the loggers above.
Switching products means leaving your history behind, so nobody switches.

What OTTO reads

Every export the team already has

CSV exports from MoTeC i2, AiM RaceStudio, RaceBox / RaceBox Pro, VBOX Circuit Tools and Garmin Catalyst, and plain CSV from anything else — delimiter and header detected, channels found by name, laps split when the file carries a lap count. It's live in the demo.
Native logger files (.ld, .xrk, .drk) come across through the vendor's export-to-CSV — a click in software the team already owns, not a re-log.
Setup sheets, tyre and fuel notes and rosters come over in founding-program onboarding — handed to us, not dropped in the importer.
It stays yours. Export all of it any time, delete it any time; nothing identifying is ever shared between teams.

Why this matters to an investor: switching cost runs the other way. Every competitor's customer can move to OTTO on day one with their logged history intact — and the coach is fluent in their cars by the first debrief. Drop a sample RaceBox file into the demo importer →

The full matrix

Everything on the market does one third of the job

Green is a shipping capability. Amber is partial — it can be done with add-ons, a pro-tier unit, or offline in desktop software, and the note says which. Red is a flat no. Blue is OTTO's roadmap and is labelled as such.

Capability	Garmin Catalyststandalone coach	RaceBox Mini / ProGPS puck + app	AiM Solo 2 DLdash logger	VBOX Sport / HD2logger + video	Apex ProLED coach + app	Phone appsHarry's, TrackAddict	DashcamBlackVue etc.	OTTOPaddock · OTTO 1
The bottom line
A full race-engineering team, in your handrace engineer, data engineer, driver coach and pit wall — in one system that talks	Noa lap timer that talks	Noa GPS logger	Noa data logger	Noa data logger	Noa grip meter	Noa lap timer	Noa camera	Yesthe whole pit wall — reading the car, thinking, and talking back — from one install
Data
Lap & sector timingGPS position and rate	Yes10 Hz	Yes25 Hz	Yes10–25 Hz	Yes20 Hz	Yes	Partialphone GPS, or an external puck	Partial1 Hz speed stamp	Yesdual-antenna GNSS fused with wheel speed
Vehicle dataRPM, throttle, brake, temps, fuel	No	No	YesECU / OBD	PartialCAN on HD2-class units	PartialOBD-II adapter	Partialwith an OBD dongle	No	YesOBD / CAN, read-only
Tire, brake & fuel on the pit walllive, every car	No	No	Partialadd-on sensors, on the unit	Partialadd-on sensors, on the unit	No	No	No	Yesstreamed on the same uplink as the video
Measured slip angledrift, not guessed from yaw	No	No	No	Partialdual-antenna 3i, pro tier	No	No	No	Yesdual antenna, standard
Engine health & pre-code warnings	No	No	No	No	No	Partialcode reader with a dongle	No	Yes
Coaching
Live voice coachingand whether it thinks, or plays a script	Partialscripted cues — a fixed set of lines triggered by GPS	No	No	No	PartialLED grip bar + app audio	No	No	Yes — it thinksan AI co-driver reasoning over the live car data, in plain language, like a person on the radio — not a script
Talks backask it why, get a reasoned answer	No	No	No	No	No	No	No	Yes
Corner references computedbrake distance, entry & apex speed from the circuit's elevation	Partialoptimal-lap targets from your own laps	No	No	No	No	No	No	Yessolved per circuit
Driver vs driver, corner by corner	Partialyour own laps, on the unit	Partialin the app	YesRaceStudio, offline	YesCircuit Tools, offline	Partialin the app	Partialin the app	No	Yeslive, across every car in the program
Class-rules modelog-and-debrief when live aids are banned	Partialcoaching can be muted	n/a	n/a	n/a	PartialLEDs off	n/a	n/a	Yesswitches per session
Team
Live pit wall, every running car	No	No	Partialtelemetry radio option, pro tier	Partialtelemetry option, pro tier	No	No	No	Yes
Onboard video to the pit wallbefore the broadcast	No	No	No	No	No	No	No	Yes~1.5 s on a bonded LTE uplink
Reads every other product's exportsbring the sessions you already logged	NoCatalyst files only	NoRaceBox files only	PartialCSV into RaceStudio on a PC; the unit reads AiM only	PartialCSV into Circuit Tools on a PC; the unit reads VBOX only	NoApex files only	Partialsome CSV, no other apps' logs	No	YesCSV from Catalyst, RaceBox, AiM, VBOX, MoTeC and anything else — native files via the vendor's own CSV export
Exports all of your data, any timeit stays yours	Partialsession CSV	YesCSV	Partialproprietary + CSV	YesCSV	Partialapp export	YesCSV	Partialvideo files	Yeseverything, on demand — and you can delete it
Learns from your archivebenchmarks against your own history	No	No	No	No	No	No	No	Yes
Car & video
Video with data overlay	Yesone front camera	Partialphone video in the app	PartialSmartyCam add-on	YesHD2	Partialphone video	Yesphone camera	Partialspeed stamp only	Yesfront and rear pods
Daily dashcam & Sentryparked, it still watches	No	No	No	No	No	No	Yes	Yes
Looks like it came with the car	Suction pod	Puck on the dash	Dash mount	Dash mount	Dash mount	Phone cradle	Wire down the glass	Built per chassispods on a primed bracket, box under the seat
Radar threat integration	No	No	No	No	No	No	No	Yescompatible detector required
Auto-edited clips for socials	No	No	No	No	No	No	No	Yes
Trust
Trackside sector beaconsground-truth timing at every corner	No	No	No	No	No	No	No	In developmentOTTO Beacons — founding programs first
Gets better after you buy it	Partialfirmware fixes	Partialapp updates	Partialfirmware fixes	Partialfirmware fixes	Partialapp updates	Yesapp updates	Partialfirmware fixes	Monthly OTAnew capabilities, not just fixes

Scroll the table sideways for the OTTO column →

YesshippingPartialadd-on, pro tier, or offline onlyNonot thereIn developmentOTTO roadmap, labelled honestly

Read the tally the way an investor would: every other column is a single instrument. The OTTO column is a race engineer, a data engineer, a driver coach and a pit wall — a full race-engineering team within the reach of your hand, for teams that will never afford one and for the ones that already have one and want it sharper.

None of which means a team has to pick a side on day one — the portal reads all of their exports, so they can run whatever they own today and still get the engineer. Try the import with a sample file →

Fail-proof data

No single sensor is ever trusted alone

A GPS-only product has one source of truth and it lives in the sky. OTTO cross-checks every lap five ways — and the fifth one is bolted to the track.

OTTO Beacons In development · founding programs first

Sensors around the track: a timestamp at every corner, so a sector time can never lie

Puck-sized, battery-powered beacons zip-tied to the cones or the armco at each corner and sector line. Every car that passes gets stamped to the millisecond on the same uplink that carries the video — under the bridge, in the tree line, in the canyon where GNSS drops out. The beacon has the truth, the GNSS has the shape, and the two are reconciled on the pit wall before anyone sees a number.

01GNSS

Dual-antenna position and heading at rate — the shape of the lap and the measured slip angle.

02Wheel speed & IMU

From the car, not the sky. Fills the gaps GNSS leaves and catches the moment it drifts.

03OBD / CAN

RPM, throttle, brake and temps — so a "fast sector" that came from a missed brake point is labelled as one.

04Beacons

A hard timestamp at every corner. The one input a satellite outage can't touch. Also stamps the video, so the clip and the number agree.

What "fail-proof" means here: five independent inputs, reconciled per lap. If any one disagrees with the other four, the number on the wall is flagged rather than shown. Beacons are on the roadmap, not in a shipping box today — they're listed in the matrix in blue for exactly that reason, and founding programs get them first.

Check it yourself

Bring the file from whatever you own. It imports in seconds.

The fastest way to settle "is it better than X" is to drop X's export into the portal and ask Otto about a corner.

Open the team portal demo → Talk to the team desk The full race program