Hammerhead Karoo
Head unit
Finish on your Karoo and the ride lands here by itself — the original FIT file, every field it recorded.
Integrations
See what connects, what syncs, and how to bring your history across.
Head unit
Finish on your Karoo and the ride lands here by itself — the original FIT file, every field it recorded.
Head unit
Roll in off your ELEMNT and the ride is already here waiting for you.
Head unit
Activities, daily health, and workouts from your COROS account. Data provided by COROS.
Cloud service
Completed rides come in with their original file, and planned workouts go back to the calendar.
Cloud service
Routes you already have on Ride with GPS land in the planner, and routes you draw here can be sent back.
Cloud service
Indoor rides come in from ROUVY, and planned workouts go back to that calendar.
Wearable
Recovery, strain, sleep, and body measurements land here after you connect.
Wearable
Exercises, daily activity, and physical info from Polar Flow land here after you connect.
Wearable
Sleep, heart rate, workouts, and weight from the NeverChill iOS app after you grant Health permissions.
Wearable
Sleep, heart rate, workouts, and weight from Health Connect on Android. This is not Google Fit and not cloud OAuth.
Head unit
Your iGPSPORT rides, collected for you — no cable, no export, no fuss.
Head unit
Your Bryton rides, collected for you — no cable, no export, no fuss.
Wearable
Readiness, sleep, activity load, and workouts land here after you connect your ring.
Wearable
A Withings scale and sleep tracker: weight, body composition, sleep, and resting heart rate.
Head unit
Edge, Forerunner, Fenix — every Garmin ride landing here on its own, with nothing to press.
| Device | Availability | Rides in | Health in | Routes out | Workouts out |
|---|---|---|---|---|---|
Hammerhead Karoo | Ready to connect | automatic | Not supported | automatic | automatic |
Wahoo | Ready to connect | automatic | Not supported | automatic | automatic |
COROS | Ready to connect | on sync | on sync | Not supported | automatic |
intervals.icu | Ready to connect | automatic | Not supported | Not supported | automatic |
Ride with GPS | Ready to connect | automatic | Not supported | automatic | Not supported |
ROUVY | Ready to connect | automatic | Not supported | Not supported | automatic |
WHOOP | Pro | Not supported | automatic | Not supported | Not supported |
Polar | Pro | automatic | automatic | Not supported | Not supported |
Apple Health | Pro | Not supported | automatic | Not supported | Not supported |
Health Connect | Pro | Not supported | automatic | Not supported | Not supported |
iGPSPORT | Coming soon | Sync details will be available when this integration is ready. | |||
Bryton | Coming soon | Sync details will be available when this integration is ready. | |||
Oura | Coming soon | Sync details will be available when this integration is ready. | |||
Withings | Coming soon | Sync details will be available when this integration is ready. | |||
Garmin | On hold | This integration is not available to connect. | |||

Already have years somewhere else?
Every platform owes you an export of your own data. Ask for the archive, upload the zip, and you arrive with your history rather than starting again at zero.
Ask Strava for the data export they are obliged to give you, then upload the zip here. Activities and their original files, photos and videos with their captions, your bikes and their component lists, your goals and your saved routes all come across - and each ride keeps the visibility it had over there.
We never touch Strava's servers to do it - it is your file, handed over by you, and we never ask for your Strava password. Multi-gigabyte archives are fine, and running it again later only adds what is new.
A move, not a connection. An archive is a snapshot of the day you export it; from then on, rides arrive through a connected device or an upload.
Device not listed?
Every head unit ever made writes a .fit, .gpx or .tcx. Drag it in and it gets the same maps, power curve and climb detection. A connection saves you a step; it does not unlock anything.
.fit, .gpx and .tcx all welcome
No. Every head unit worth owning writes a .fit, .gpx or .tcx file, and an uploaded file is analyzed exactly like one that synced itself - same maps, same power curve, same climbs. A direct connection saves you the upload; it does not buy you a better ride page.
On sync means we fetch your rides whenever our next check comes round. Auto means the maker tells us the moment one exists, so it is here in a minute instead. Both are listed per device, because not every maker offers the second.
No. An archive import is a one-time move, not a connection - it brings across what exists on the day you upload it and then it is done. Run it again later and it adds what is new; it never rewrites a ride you have already edited here.
No. A ride is matched first by the provider's own activity id, then by the file's content hash, and only then by a fingerprint of start time, elapsed time and distance. So a reconnect re-links the rides you already have instead of making second copies of them - and that record is what lets you tell, years later, which bike computer captured which era of your riding.
Yes, and only you can. Once the provider is disconnected, a separate action behind a typed confirmation erases everything it brought in. It is never a side effect of anything else, and disconnecting on its own stops new data immediately without deleting a ride.
Connecting a bike computer is on the free tier. Wearables - recovery, sleep and strain - are a Pro feature.
Connect a head unit, bring an old platform over, or drag in a single file. Your history gets here; it is yours to keep.