Technology
Firmware that is
already hardened.
The core components run in production today, with years of field hardening, component-level testing and crash-dump tooling under each one. Take the full platform or only the parts you are missing — they run on small MCUs and embedded Linux alike.
01 — Firmware platform
A stable base with fast release cycles
Modem connectivity, firmware updates and debug logging are the parts every device needs and every team underestimates. Ours have years of production hardening behind them.
Heavy component-level testing catches regressions before they reach a device. When something does go wrong in the field, detailed crash dumps and trace logs come back remotely, so you debug from the desk, not the vehicle.
- Hardening
- Years in production · component-level tests
- Remote debug
- Crash dumps · debug & trace logging
- Connectivity
- Optimised, faster modem connectivity
- Updates
- Optimised, faster firmware updates
- Toolchain
- Open source · Windows, macOS, Linux · no proprietary compiler
02 — CAN stack
Reads most vehicles, fits almost anywhere
<30 KB
flash for the full stack
1 KB
RAM minimum
0
heap, threads or timers
2010+
most vehicles built after 2010
The CAN stack covers most vehicles built after 2010 with ISO-TP diagnostics, raw frames and broadcast traffic.
It needs no heap, no threads and no timers, so it drops into a small MCU without reshaping your firmware — and runs just as well on embedded Linux.
- Protocols
- ISO-TP (UDS/KWP2000) · raw · broadcast
- Targets
- Small MCUs · embedded Linux
- Next
- VW TP2 In development
- Next
- CAN scan In development
03 — CAN parameter library
The parameters, not just the protocol
Vast parameter collection
A stack that speaks CAN is only useful if it knows what to ask for. The library maps the parameters that matter across private cars, vans and trucks.
Cars · light commercial vehicles · trucks
Kept current
Collaborations with leading diagnostics tool vendors keep the library up to date as new vehicles reach the road.
Data collaborations · new models added continuously
Remote reverse engineering
In development When the CAN scan feature is production-ready, remote reverse engineering and diagnostics support in-depth parameters for any vehicle.
Remote scan · diagnostics · any vehicle
04 — IMU
Calibration that holds, events you can trust
IMU calibration & safety events
Calibration combines accelerometer, gyroscope and GNSS speed, and recalibrates automatically to handle drift. It works across different IMUs, so harsh-driving and safety events stay reliable when the hardware changes.
Accelerometer + gyroscope + GNSS speed
Trip start/stop without an ignition wire
In development Live IMU data detects when a trip starts and stops. No ignition wire means easier installation and simpler cabling.
Live IMU streaming · no ignition wire
05 — AI crash detection
Crash classification on par with market leaders
The device detects a candidate crash; a trained AI model in the cloud decides what it was.
The model is device-agnostic, so it also works on the devices you already have in the field — no hardware change needed to add crash detection to an existing fleet.
- Step 1 · device Detects a candidate crash
- Step 2 · uplink Sends the event to the cloud
- Step 3 · cloud Trained model classifies it
06 — GNSS filtering
Clean tracks from one generic filter
GNSS outliers are removed by cross-checking every fix against IMU data.
One generic filter replaces a pile of per-corner-case workarounds, so there is less code to write, test and maintain.
- Input
- GNSS fixes + IMU data
- Method
- Cross-check · reject outliers
- Maintenance
- 1 filter · no per-case rules
Go deeper with our engineers
Send us your target hardware and use case. We will walk your team through the components that fit.
Talk to an engineer