Sastram (शास्त्र) means a systematic body of knowledge. Here's why that's the right name for a company trying to change driver behavior with data, not just measure it.
Sastram is a Sanskrit word — शास्त्र — that means something close to “a systematic body of knowledge.” Not a myth, not a slogan: a discipline. A set of rules derived from repeated observation, refined over time, meant to be tested against reality rather than taken on faith.
That’s an odd word to put on a telematics company. Most SDK vendors name themselves after speed, safety, or some abstraction of trust. We picked a word that means “the discipline of knowing,” because that’s closer to the actual problem we’re solving.
Every telematics vendor can tell you a phone accelerated hard at 14:32 on a Tuesday. That part is comparatively easy — accelerometers are cheap and everywhere. The hard part is turning that one data point into something a fleet manager, an insurer, or a driver can actually act on: was that hard stop defensive braking that avoided a collision, or a driver who was following too close and got lucky? Was that phone-motion event the driver texting, or a passenger using the phone while the car was stationary at a light?
Answering that reliably — across the budget Android devices real fleets actually run, not just flagship test phones, and across the OS-level battery optimizations that kill background services without warning — is a systematic problem, not a one-off engineering trick. It needs the same thing a shastra needs: rules built from repeated observation, tested against edge cases, revised when they break.
Sastram Labs was founded by an operator who ran telematics programs — UBI pricing, fleet safety, claims — across Colombia, Israel, South Africa, Southeast Asia, and the US for eight years before building a vendor. That matters more than it sounds: most of what breaks a telematics program isn’t visible in a demo. It shows up eighteen months in, when a claims team asks why a “safe” driver just had an accident, or when a fleet rolls out to a new city and the phone-placement detection starts misfiring on a device nobody tested against.
Sampark, Bodha Drive, and Hastle Free are shaped by what broke in those programs, not by what looks good in a pitch deck. That’s the shastra part — a body of knowledge built from running the thing, not from reading about it.
A discipline is a set of rules you keep testing against reality. That’s the bar we’re holding the SDK, the app, and the backend to — not the bar of “does it work in the demo.”
In practice, it means three composable pieces instead of one black box: Sampark, the native iOS/Android SDK that does the actual detection work; Bodha Drive, a free consumer app that proves the SDK end to end on real devices, not just test rigs; and Hastle Free, the multi-tenant backend that runs insurance UBI/BBI programs and SDK pilots from the same codebase, config-driven rather than forked per customer.
None of that is glamorous. It’s closer to what the word actually means — a discipline, kept honest by testing it against the same conditions that broke the last generation of telematics programs.