Mobile SDK to embed telematics into your app

The DriveKit SDK has been designed to transform your mobile application into a driving analysis solution.

Why is DriveKit the best choice?

The DriveKit SDK turns any mobile app into a telematics solution to collect driving data from smartphone's sensors (accelerometer, inertial unit, GPS).

DriveKit allows insurers to assess the real road risk of their driving community based on three driving scores: the safety score, the distraction score and the eco-driving score.

DriveKit also gives insurance companies the tools to promote safer driving through connected services such as driving challenges and driving coaching.

Our crash detection service alerts insurers if a driver is involved in a road accident. Operators can then proactively dispatch emergency services or roadside assistance depending on the severity of the impact detected by our service.

DriveKit is also unique as all the graphical interfaces can be integrated into your mobile application as independent, combinable components.

More on our driving scores

Data collection and analysis

Open source UI components

Automatic trip detection

Engage with drivers

Crash detection & connected assistance

Illustration of the Driving tips of DriveQuant.

Connect your policyholders with smartphones

The DriveKit SDK collects driving data to analyse the driving behavior of every policyholder.

It uses the GPS sensor sampled at 1 Hz for the analysis of vehicle dynamics, and the energy consumption analysis. The motion sensors (accelerometer and gyrometer), sampled at 100Hz, are used for crash detection purposes.

Visit our FAQ page

Use our graphic libraries to save time

The DriveKit SDK is unique because it contains a free graphical library that insurers can freely used.

The objective is to provide insurers and users with the best driving indicators combined with clear visualisations.

Browse our technical documentation

No driver intervention needed

The SDK runs in the background and automatically detects the start and the end of a trip, without any action required from the driver. The solution has been designed to avoid disturbing policyholders while driving and ensure they only focus on the road.

The DriveKit SDK uses the smartphone's sensors to collect driving data. The data is then processed to be transformed into objective driving indicators. The SDK can be combined with a beacon for ensuring vehicle identification in Pay-As-You-Drive programs.

Discover our driving scores

Build customer loyalty

Once installed, the DriveKit SDK transforms the data collected by smartphone sensors into reliable driving scores, and driving indicators.

The insights are displayed in maps and visualizations to highlight areas for driving improvement.

Beyond our driving scores, the SDK contains connected services such as driving challenges to engage in road prevention and make drivers safer on the road.

Discover driving challenges results

Protect your community

With our best-in-class crash detection service, assistance operators are alerted within seconds of a road accident. Operators can then dispatch emergency services in case of severe collision or send out breakdown services.

The driver also gets a notification asking him to confirm their state of health.

Our service also generates reports with driving data before, during and after the impact to help understand the conditions of the accident and accelerate claim management.

How does crash detection work?

Benefits of DriveKit

Low battery drain

The SDK runs in the background and only uses the GPS sensor when it detects a trip. Our automatic trip detection system is the most performant and power-efficient solution on the market.

Low data usage

The data exchange volume has been minimized to ensure that the SDK consumes a minimal amount of mobile data.

Quick setup

Installing the DriveKit SDK is a straightforward process, facilitated by our publicly available documentation. The integration can be completed in a single work day.

Compatibility and accuracy

The DriveKit SDK is compatible with all iOS and Android devices. We conduct rigorous and scientific assessments of sensors and data quality to produce reliable driving indicators.

Work offline

The SDK works both online and offline. It synchronises the data with our servers even if the user changes smartphones or uses multiple devices.

Combine with beacons

The DriveKit SDK uses the smartphone sensors to detect trips but it can also be combined with beacons for Pay-As-You-Drive programs.

The essential guide for comparing telematics SDKs

The guide highlights three essential technical criteria and describes the internal test method we use to benchmark our SDK against its main competitors.

Read the guide

Integrate our SDK into a mobile app

Make an informed decision

What types of mobility can DriveKit detect?

DriveKit can identify 10 different modes of mobility: car, walking, cycling, motorcycle, train, plane, boat, truck, bus, and skiing.

Which cross‑platform technologies are officially supported by DriveKit?

DriveKit offers two cross‑platform integrations: Flutter and React Native. Integration guides are available in the documentation.

What features are included in the SDK?

Our SDK DriveKit includes all of our driving analysis services including trips details, scoring, driving summaries, driving challenges, automatic road crash detection, coaching, eco-driving, mileage tracking, fuel consumption estimation, estimation of tire/brake wear.

How is driving data collected?

Our driving analysis service uses phone sensors (GPS, accelerometer, inertial unit and gyroscope) to collect driving data and measure more than 200 indicators including hard accelerations, harsh brakings, limits of adherence and even detect road crashes.

Does DriveKit perform local calculations (edge computing)?

Driving indicators are calculated on the DriveQuant platform, not directly within the SDK. While edge computing — analyzing driving data locally on the smartphone — may sound appealing in theory, it comes with fundamental limitations that make it unsuitable for connected insurance programs:

Updates: a bug in the SDK remains active until users update their app.

Fragmentation: multiple SDK versions coexist in production, complicating support and long‑term maintenance.

Battery drain: local processing heavily uses the CPU, leading to higher battery consumption.

SDK size: embedding heavy libraries (e.g., TensorFlow) significantly increases the app’s weight.

Raw data access: insurers need raw data to build their own scoring models.

Maintenance: without access to raw data, diagnosing or correcting calculation errors is nearly impossible.

In short, backend data processing is the most reliable, scalable, and compliant solution for connected insurance programs.

Can I activate only certain services?

Yes. You have the choice to include in your application only the services you want to offer to your users.

Do users have to manually trigger the driving analysis service before each trip?

No. The driving analysis service runs in the background on the phone. There's no required action from the driver.

What applications is the SDK compatible with?

Our DriveKit SDK is compatible with all mobile applications, on both iOS and Android platforms. We offer comprehensive documentation that provides detailed technical instructions, along with one demo app to deliver a smooth onboarding process. Our SDK is also designed to integrate seamlessly with most cross-platform frameworks. Additionally, we provide specific gateways for React technology, ensuring compatibility and ease of integration.

How to integrate the SDK DriveKit?

To streamline the integration of the SDK into your application, we have developed a comprehensive public documentation. This resource empowers you to seamlessly integrate the SDK within a work day. In the event that you encounter any challenges during the integration process, our team is available to provide support.

How can I consult the driving data of my users?

We have designed a web Dashboard where you can access all your users' driving data including their driving scores, their rankings, and optionally, detailed trip information. For a more detailed overview of the web Dashboard's functionalities, visit the dedicated page.
Alternatively, you have the option to retrieve the data directly on your backend through API or set up an automated push system to receive the data seamlessly.

Is driving data analysis tailored to the vehicle being used?

When the app is launched for the first time, the driver enters details about their vehicle — type (SUV, city car, sedan…), brand, model, and powertrain (combustion, fully electric, plug‑in hybrid, non‑plug‑in hybrid, or diesel). DriveKit’s data processing algorithms then adapt based on this information.

Is DriveKit compatible with electric vehicles?

During onboarding, users are asked to add their vehicle to the app by specifying its type (SUV, city car, sedan…), brand, model, and powertrain (combustion, fully electric, plug‑in hybrid, non‑plug‑in hybrid or diesel). The driving data analysis is adjusted accordingly.

If the user indicates they drive an electric vehicle, the algorithms are automatically adapted to reflect this.

What happens if a trip is made without an internet connection?

Lack of connectivity does not result in data loss. Whether online or offline, the SDK records driving data whenever it detects a trip. The data is stored on the phone and automatically sent to the backend for analysis once the device reconnects to the network.

What information is available when a support request is submitted?

When a driver submits a support request, logs from the past two months are automatically attached to help resolve the issue. These include: phone make and model, OS version, installed DriveKit SDK version, granted permissions, mobile network status, and the event log. With this information, the support team can quickly identify the root cause and provide a solution.

Can misconfigured phones be identified to speed up support?

Yes. In the app’s “Settings” menu, the “App Diagnostics” section allows users to detect configuration issues and fix them easily by clicking “Learn more.”

What happens if the user runs out of battery or turns off their phone during a trip?

Trip data collected by the SDK is saved to the smartphone every 30 seconds. If the phone shuts down due to low battery or is manually turned off, the portion of the trip already captured will be sent to the backend once the device reconnects to the internet. The trip will be labeled “interrupted” to indicate partial recording.

Latest insights

Connected Insurance featured

How to Choose the Right Telematics Partner: 6 Criteria That Really Matter in 2026