Platform

One system. Two halves that need each other.

A custom edge-compute node reads the chassis bus directly; a real-time routing engine turns that stream into decisions a shop and a driver can both act on.

Close-up of an automotive CAN bus connector and wiring
Layer 01 · the bus

We start where the data actually is.

Not the restricted OBD-II port — the chassis bus itself, intercepted with a 26-pin harness that installs without splicing a single wire.

Interactive deep-dive

Inspect either half.

Toggle between the physical intercept and edge-compute layer, and the platform and API architecture it feeds.

H · 01

Chassis CAN intercept

Custom Rev D gateway nodes and a 26-pin intercept harness bypass the restricted OBD-II port to read raw chassis telemetry directly off the bus.

MCUESP32-S3
InterfacesRS485 / CAN
Harness26-pin intercept
H · 02

Edge intelligence & processing

Low-latency firmware parses, filters, and structures high-frequency CAN bus streams on-device, then transmits securely over cellular or a local SoftAP link.

FirmwareC / C++ · FreeRTOS
ProcessingOn-device parse + filter
UplinkCellular / SoftAP
H · 03

Non-invasive deployment

Engineered for fast installation in customer vehicles with no wire splicing and no voided factory warranties — so a shop can roll units across its whole customer fleet.

InstallNo splicing
WarrantyNon-voiding by design
Scale unitPer customer vehicle
ESP32-S3FreeRTOS CAN protocol parsingRS485 26-pin intercept harnessEmbedded C / C++ SoftAP provisioningOpen hardware schematics
CAN bus connector kit and harness components
Harness & connector layer
Installation

Fifteen minutes, no splices, no warranty risk.

The intercept harness sits inline with the factory connector. Nothing is cut, nothing is soldered, and the vehicle returns to stock the moment the node is removed.

That matters commercially as much as technically: a shop can deploy across a customer fleet without asking anyone to accept a modification to their vehicle.