Frequently asked questions

Three composable pieces of telematics infrastructure: Sampark, a native iOS/Android SDK that detects phone use, hard braking, and rapid acceleration; Bodha Drive, a free consumer app built on Sampark; and Hastle Free, the multi-tenant backend that powers both. Most customers 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.

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. The products are shaped by what broke in those programs, not by what looks good in a demo.

India, Colombia, Israel, South Africa, Southeast Asia, and the US. Sastram Labs is headquartered in Bengaluru, Karnataka.

No. Sampark is the core — most companies integrate it into their own app and backend. Bodha Drive and Hastle Free exist for teams that want to move faster without building an app or backend from scratch, and either one can be dropped later without touching the others.

A native iOS and Android telematics SDK, sharing a Rust core, that measures phone distraction, hard braking, and rapid acceleration per trip for commercial fleets and insurance programs.

Sampark is tested and optimized for the budget OEM Android devices real fleets actually run — not just flagship phones — so background detection stays active despite aggressive OEM battery optimization. See the device matrix for the tier-by-tier breakdown.

Sampark uses a persistent foreground service plus geofence and activity-recognition transition wake-ups to recover within 30–90 seconds of the next motion event, even after a hard kill. This is the single most common failure mode for other SDKs, which is why we test against it first, not last.

One init call, same API surface on iOS and Android. Teams that have integrated CMT or Zendrive before are typically productive within an afternoon.

Yes — free to download on iOS and Android, no subscription required.

A per-trip score broken down by phone use, braking, and acceleration, plus trip history and post-trip nudges — nothing averaged away or hidden behind a single number.

Yes. Bodha Drive runs as an sdk_pilot tenant on the same Hastle Free backend that also runs insurance UBI/BBI tenants — it’s our own proof that the stack works end to end before we ship it to a customer.

A multi-tenant backend that runs insurance UBI/BBI programs and SDK pilots like Bodha Drive from a single codebase, with schema-per-tenant isolation and config-driven onboarding.

No. Onboarding means writing configuration — feature flags, coverage rules, webhook adapters — not forking the codebase. Each tenant runs in its own isolated database schema.

Yes, where a program needs it — see Data Residency for how self-hosted and regionally pinned deployments work.

On-device, by default, after the trip ends. The phone does the detection and scoring work; the backend is for upload and reporting. Full detail on our Data Residency page.

No, and we don’t use it to serve advertising. See our Privacy Policy for the full breakdown of what we collect and why.

Email hello@sastram.in. If your trips are scored through a fleet or insurer’s program, that customer usually holds the underlying consent relationship, so we’ll route the request to the right place.

Sampark SDK and Hastle Free are priced per commercial agreement based on your fleet size and scope, so we don’t publish a number here. Bodha Drive is free with no subscription.

30 minutes with the engineer who’d own your integration — bring your device list, geography, and timeline. We’ll tell you exactly what to expect on your fleet, including where the SDK will degrade, or refer you to someone better suited. No follow-up sequence.

A four-stage calibration loop against your fleet, geography, and driver mix before any policy goes live — see how the loop works for the full stage-by-stage breakdown.