The protocol for cars that talk first.
DriveLink is a three-layer system: an on-vehicle module, a low-latency message standard, and an intelligence layer for fleets and cities.
On-Vehicle Module
Lightweight hardware module + embedded software that reads bus telemetry and performs local trajectory prediction.
DriveLink Protocol
Intent-first V2V message standard. Compact payloads, gossip-friendly mesh, sub-50ms delivery between neighbors.
Intelligence Layer
Fleet & city analytics, conflict-zone detection, intent heatmaps, OEM-grade insight pipelines.
See the protocol drive traffic.
A real V2V traffic model running in your browser — car-following, negotiated lane changes, and an on-ramp merge gate. Toggle the mesh and watch cooperation appear.
Toggle V2V negotiation off to watch cooperation break down — cars demand larger gaps, merges stall at the gate, and average flow drops. Every decision (car-following, lane change, merge gate) runs client-side in your browser.
An intent packet, end to end.
Every DriveLink message is small enough to fit in a single UDP datagram. Here's the on-wire shape.
message Intent {
string vehicle_id = 1; // DRV-A1, OEM prefix optional
uint64 ts_us = 2; // monotonic since boot, μs
Pose pose = 3; // {x, y, heading, lane_id}
Motion motion = 4; // {speed, steer, accel}
Predict predict = 5; // 1.5 s probabilistic cone
Action intent = 6; // LANE_CHANGE | BRAKE | MERGE | HOLD
uint32 confidence = 7; // 0-100
bytes signature = 8; // node-signed
}Four early markets.
EV Fleets
Reduce brake-wave traffic, smooth dispatch, real-time conflict detection across the fleet.
OEM Vehicle Manufacturers
Add cooperative behavior on top of existing ADAS stacks. License per vehicle.
Smart Cities
Mesh nodes at intersections feed back intent heatmaps and conflict-zone insights.
Autonomous R&D Labs
Standardized intent layer for testbeds, simulation, and cross-OEM cooperation studies.
DriveLink vs. existing V2X.
How is DriveLink different from DSRC and C-V2X?
Those standards define the radio and transport. DriveLink is the intent layer above them: a compact, vendor-neutral message format for predicted trajectories and maneuvers, designed to run over any underlying V2X radio, WiFi mesh, or cellular link.
Does this require new hardware in every car?
The protocol is transport-agnostic. The reference module is a lightweight retrofit unit, but OEMs can implement drv-mesh on existing telematics hardware.
What happens when only some cars have DriveLink?
The protocol is designed for partial adoption. Equipped vehicles gain cooperative behavior with each other immediately; benefits scale with penetration rather than requiring it.
Is the protocol open?
The v0.1 spec and reference simulation are public on GitHub. Standardization with OEM partners is on the roadmap for v1.0.
Build the automotive AI backbone with us.
“Investors, OEMs, fleets, and mobility partners — let's set the standard for cooperative mobility.”