Lakehouse architecture
Telematics and IoT data for insurers: usage-based insurance, loss prevention and claims on a streaming lakehouse
Telematics and IoT devices produce continuous data about driving, buildings and assets. On DataNature, StreamHouse ingests device events in real time into Iceberg tables, features such as harsh braking, night driving, water leaks or temperature alerts are computed continuously, and AI360 Studio uses them for usage-based pricing, loss prevention alerts and faster claims. DataNature Atlas governs location and behaviour data, which is highly sensitive, and keeps it in-country.
Published . Last updated
On this page
Connected cars, smart home sensors and industrial IoT give insurers a live view of risk instead of a yearly snapshot. The challenge is volume, speed and sensitivity: millions of events per day, value that fades within minutes for alerts, and location data that must be protected. A streaming lakehouse handles all three.
What can insurers do with device data?
| Use case | Data | Outcome |
|---|---|---|
| Usage-based motor insurance | Trips, mileage, speed, harsh braking, time of day | Pricing that reflects how and how much people drive |
| Crash detection and FNOL | Impact events, location | Faster help and claims started automatically |
| Connected home loss prevention | Water leak, temperature, smoke and power sensors | Alerts before small problems become large claims |
| Commercial property and equipment | Vibration, temperature, machine status | Risk engineering insight and fewer breakdown claims |
| Fleet insurance | Vehicle and driver behaviour across fleets | Coaching programs and fleet-level pricing |
How does the architecture work?
- Ingest: devices or telematics providers send events to StreamHouse, which writes them exactly once into Bronze Iceberg tables.
- Process: streaming jobs clean events and compute features in short windows (harsh events per 100 km, night-driving share, leak alerts).
- Store: trips and daily aggregates land in Silver and Gold for pricing and analysis; raw location is kept only as long as needed.
- Score: AI360 Studio scores driving behaviour or property risk; alerts fire in real time.
- Act: customers get alerts and feedback in the app; claims start automatically after a detected crash; pricing teams use aggregated features.
How do you protect location and behaviour data?
- Collect only with clear consent, and explain what is measured and why.
- Aggregate early: pricing usually needs trip scores, not raw GPS trails.
- Mask or truncate location for most users in DataNature Atlas, and restrict raw data to a small, logged group.
- Apply retention rules that delete raw traces after a set period.
- Keep all device data in your jurisdiction.
How does this connect to claims and pricing?
Telematics features join the same governed tables as policies and claims, so actuaries can test whether they predict losses, claims teams can see crash data at FNOL, and fraud models can check whether a reported accident matches device data. See AI in insurance claims.
Frequently asked questions
Do we need to build our own devices or apps?
No. Many insurers use telematics providers or smartphone SDKs; DataNature ingests their event streams.
How much data is involved?
It depends on sampling rates and portfolio size. Storing raw events in open Iceberg tables on object storage keeps cost manageable, and aggregation reduces what analysts query.
Sources
How does DataNature Atlas keep this secure and compliant?
Governance is part of the architecture, not a separate tool bolted on later. DataNature Atlas is the platform's governance module:
- Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.
These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.
Platform components in this article
Learn more about each DataNature product and module mentioned here.
Products
See it on your own data.
Book a demoDemos and quotes are handled by Dlytica, the company behind DataNature.