Vehicle data collection
Standardize and collect driving and status data from vehicle devices.
Trip records that show who was driving
Combines trip data with driver verification to produce explainable driving scores and trip records that are hard to tamper with.
What makes it different
Binds in-vehicle trip data to driver verification, turns it into scores and records, and seals them so insurers, operators and contracting agencies can cross-check them directly.
Three pillars and expansion areas
Records who drove, when and how in a form others can check. Trip data from in-vehicle devices is bound to driver verification and sealed, so insurers, operators and contracting agencies can cross-check it themselves.
Public brands
Vehicle data collection
Standardize and collect driving and status data from vehicle devices.
Driver verification
Verifies the driver with the government mobile driver's licence and attributes the score to that driver.
Explainable driving score
The same input gives the same score, and the reason for each score can be explained.
Sealing and third-party verification
Scores and trip summaries are sealed on a blockchain so third parties can cross-check them.
Insurance and mutual-aid links
Serves as basis data for usage-based insurance (UBI) and mutual-aid contribution talks.
Manage fleet control and safety with data.
Design usage-based insurance products from driving data.
Benefits that return as carefully driven miles add up.
We confirm operating scale, region, and integration targets, then define the rollout scope together.
Receive an invitation and review real operating screens with sample data.
Start real operations in a small scope and check field fit.
Use pilot data to expand regions, routes, and operators step by step.
We start mainly with corporate and commercial vehicles equipped with devices.
The data belongs to the client. We disclose what is collected and why, and process data only within the consent given.
Scoring is designed to be explainable, so drivers can see the reasons behind their own score.
Map the service axis, public brands, and operating workflows that should launch first.