Every photo sorter is gated by one of two things: the machine in front of you, or your upload. Local apps can only go as fast as your laptop. Cloud apps make you push every full-size RAW up the wire. RaceLabs is built to dodge both: you upload about 1% of the bytes, your originals never leave your disk to be sorted, and the heavy work runs on datacenter GPUs. A full trackday lands in minutes.
A local sorter is capped by your hardware; a cloud sorter that uploads your files is capped by your bandwidth. RaceLabs builds a lightweight preview of each photo, roughly 1% of the original size, and sends only that to datacenter GPUs, while your full-resolution originals stay on your disk. So your internet stops being the bottleneck, the heavy identity work never touches your laptop, and a card that would take hours to upload as RAWs is on its way in minutes.
"Thousands of photos in minutes" sounds the same on every website. What it never says is where the time actually goes, and that's decided by architecture, not marketing. There are only three ways to build this, and two of them put the wall on you.
| Local desktop toolsrun on your machine | Cloud tools that upload originalsprocess on their servers | RaceLabscompress here, process in the cloud | |
|---|---|---|---|
| Heavy work runs on | your laptop / PC | their servers | datacenter GPUs |
| You're gated by | → your CPU / GPU | → your upload bandwidth | ✓ neither |
| Bytes you upload | none | 100%, every full RAW | ~1%, a small preview |
| Originals leave your disk to sort | no | ✕ yes | ✓ no |
| Scales past your own machine | ✕ no | ✓ yes | ✓ yes |
A local tool can never beat the silicon in your bag, and the paddock is not where your workstation is. An upload-everything cloud tool can never beat your venue wifi. RaceLabs is the only column that doesn't hand you the wall.
Each ~50 MB original becomes a compact preview of roughly a quarter of a megabyte before anything is sent, about 1% of the size, and the entire difference between a half-day upload and a coffee break. Building those previews flies from JPEG or RAW+JPEG (~300/s); RAW-only is slower to develop, which we're straight about below. Here's the upload, both ways, on the same connection.
Same 10,000-photo day, same 200 Mbps connection. The RaceLabs bar really is that thin, it's not drawn to scale because at scale you wouldn't see it. And the gap is connection-proof: halve your speed and both bars simply double, uploading 1% of the bytes is ~100× faster than uploading all of them on any line. After upload, the sort runs on datacenter GPUs, not the laptop in your bag.
Compress — 10,000 JPEGs (or RAW+JPEG) at ≈300/s: about 30 seconds.
Upload — ~2.5 GB of previews on a 200 Mbps connection: about 100 seconds.
Sort — on datacenter GPUs at ≈7,000/min: about 1.5 minutes.
Under four minutes, shutter to gallery — while the upload-everything route is still hours from finishing.
RAW-only? Developing RAWs is slow by design (~5/s), so local prep on a 10k-card is nearer 30 minutes, shoot RAW+JPEG to keep the fast path. Upload and GPU sort are identical either way.
RaceLabs doesn't stop at stills. Footage is processed fast enough that per-rider video clips land alongside the photos instead of holding up delivery — a session with video isn't a second, slower job, it's part of the same ten-minute turn.
The number that pays you isn't engine throughput, it's how fast a session becomes a gallery you can sell. Tiny uploads plus datacenter GPUs collapse that window to minutes, so riders can buy before they've left the paddock, while they still have the lap in their veins.
The identity work, the genuinely heavy part, runs in the datacenter, not on your machine, so a modest laptop handles the sort and you're not lugging a tower to the circuit. (Local preview prep is light for JPEG; RAW-only adds develop time, see the timeline.)
Only the lightweight preview is sent for the sort, full-resolution RAWs never leave your disk to be analysed. The cloud sends back a sort map, which is applied to your local files. Full-size images upload only if you choose to publish a public gallery, never for the sort itself.
A 2,000-photo club round and a 20,000-photo national weekend take the same shape: small upload, GPU sort, results back. The work scales on our side, so a bigger event doesn't mean a slower laptop or a longer night.
Two things worth putting on the table, because a skeptic will ask, and they're both fine once you understand them.
A skeptic will say "four minutes hides a manual pile." Two honest things: genuinely ambiguous frames go to a small Unclear bin for a two-second glance, and when our published recall dips, that's not photos in a reject pile, it's a rider occasionally split across two folders (head-on vs from behind) that merge in one click, often automatically by race number. Precision stays 99.6%, so the leftover work is merging, not re-tagging. Full numbers on the research page.
A fair question: if you only upload 1%, does the sort suffer? No, identity is read from appearance, which survives downscaling, and our published mAP of 0.99+ is measured on this very pipeline, not on untouched RAWs. You get the small upload and the accuracy, not a trade between them.
The fast part was never the AI. It's that you never had to upload the heavy files in the first place.
The whole idea, in one sentenceBring a full day. Time it end to end, shutter to a gallery you'd hand a client. That's the only benchmark that's about your shooting, and it's the one we want you to run.