We score phone use, hard braking, and rapid acceleration — then close the loop with coaching that changes what happens next trip. Battle-tested on the budget Android hardware real fleets run. Built by an operator who’s run programs in five markets.
Sastram Labs is a telematics infrastructure company — the SDK that detects driving behavior, the app that shows drivers their own pattern, and the backend that runs the program. We build technology that changes how people drive, not just technology that measures it.
8 years running telematics programs — usage-based insurance (UBI) pricing, fleet safety, claims — across Colombia, Israel, South Africa, Southeast Asia, and the US. We built the stack we wished we’d had.
Every vendor scores trips. The score goes to a dashboard. The driver never sees it. The behavior never changes.
The score is only valuable if something happens because of it.
Phone use, hard braking, rapid acceleration — captured on-device, every trip. No driver input. No manual tagging.
A single hard brake is noise. A driver who hard-brakes in the top 20%, uses their phone on six trips out of ten, and accelerates aggressively after every stop — that is a risk profile. Built across trips, not just per trip.
The profile surfaces in the fleet manager’s dashboard: ranked by driver, broken down by behavior. Not a raw score — something to act on.
After every trip, Bodha Drive shows the driver their own pattern — phone use, where the hard brakes happened, week over week. A driver who sees their pattern changes it.
Most companies start with Sampark and bring their own app and backend. Some take all three because it’s the fastest path from pilot to live program. Take what you need. Replace it later if you outgrow it.
Native iOS and Android, shared Rust core. Detects trips even after force-kill — the failure mode every other SDK has and won’t tell you about. Battle-tested across the full spread of Android hardware in real fleets, not just flagship phones. The rest is optional.
Score dashboard, trip history, and post-trip nudges. Use it to launch in weeks, or drop it when your in-house app is ready.
One backend for every partner: drivers, policies, scoring, and notifications out to your own systems. Self-host if data residency requires it. Connects Sampark or any other SDK.
A live UBI or BBI policy needs four things to work. The SDK is one of them. We do all four — because we’ve been the customer of an SDK that did only one, and watched the program stall.
UBI, BBI, fleet safety, claims — each implies a different scoring model and consent flow. We start with the regulator’s spec.
Permission flows, workarounds for phone makers that aggressively kill background apps, and recovery when they do anyway — the part nobody writes about, which is the part that breaks programs in production.
Thresholds calibrated against your pilot fleet — your devices, your geography, your drivers. Not a synthetic test set.
The first 90 days of a program are operational, not technical — and we run them with you.
Most telematics pitches lead with one accuracy number. We don’t — because that number is meaningless without your devices, your geography, your drivers. Here’s what we’ll actually tell you on the first call.
Logged on the OEMs whose process killers break most SDKs in production. We name where any SDK degrades — and recalibrate against your pilot before a policy goes live.
We tune for low impact; heavy commuters see more. We’ll show you the exact envelope on the first call — not the number that looked best on a slide.
We commit a date once we understand your stack — and we put the engineer who’ll do the work on the call that commits it.
One entry point. Configure it with your tenant key and trips start flowing within the first drive. If your team has integrated CMT or Zendrive before, you’ll be productive in an afternoon.
// One initialisation. Same shape on iOS and Android. import Sampark let sampark = Sampark.configure( tenant: "acme-insurance", region: .in_south, onTripStart: { trip in analytics.log("trip.start", trip.id) }, onTripEnd: { trip in backend.submit(trip) } ) // On user login. sampark.setUser(id: currentDriver.id) sampark.start() // That's it. Trips detect, score, upload — even after force-kill.
I’ve been on both sides of this — running telematics programs as the operator, and building the SDKs they ran on. Most telematics tools are built by engineers who’ve never had a fleet client call them at 11 pm because trips are missing. We built Sampark having run those programs first, in five markets, for insurers and fleet operators with real money on the line.Saunak · Founder, Sastram Labs Connect on LinkedIn
That’s not a longer pedigree. It’s a different one.
“Sastram took over backend infrastructure end-to-end. The engineering judgment was a tier we don’t see often.”Ituran Group
30 minutes with the engineer who’d own your integration. We’ll tell you exactly what to expect on your fleet — or refer you to someone better suited. No follow-up sequence.
Engineer on the call · Your devices · Your geography · Your timeline