Cockpit domain software
The full stack on a cockpit domain controller: hypervisor configuration, guest OS bring-up, display and audio routing, and the boot choreography that decides what the driver sees first.
Business line B
The cabin is now the product. We build the software layer that makes a car feel like it was designed by people who ship consumer devices.
Driver cluster
Safety-isolated partition. Never blocked by an app.
Centre stack
Primary interaction surface. Two-level menu depth, hard ceiling.
Passenger display
Independent session. Content policy tied to vehicle state.
Ambient line
DOT Signal light grammar across dash and door.
Position
Vehicle programmes have absorbed consumer expectations without absorbing consumer engineering practice. The result is a 12-inch screen running a menu tree from 2014. Our cockpit practice brings handset-grade interaction and release discipline into a safety-governed environment — without pretending the safety requirements are optional.
Capabilities
The full stack on a cockpit domain controller: hypervisor configuration, guest OS bring-up, display and audio routing, and the boot choreography that decides what the driver sees first.
AAOS integration done properly — Vehicle HAL implementation against the real signal set, app framework policy, and a Google-services path where the programme requires one.
Cluster, centre stack, passenger display and head-up display treated as one composition with one state model — not four teams shipping four design languages into one cabin.
Wake-word and natural-language control, in-cabin camera pipelines for driver monitoring and occupant classification, with on-device inference as the default rather than the upsell.
Cluster and safety-relevant indicators developed under an ISO 26262 process, isolated from the infotainment partition, with a documented argument for why the isolation holds.
ISO/SAE 21434 process alignment, secure boot and a signed OTA chain built for UN R155 / R156 type-approval evidence rather than retrofitted before the audit.
DOT Link
Continuity is where our two business lines stop being a coincidence. The handset team and the cockpit team share a runtime, so the handover is an internal API call rather than an integration project between two vendors who have never met.
Bring us the programme you already have in flight.
Business line B · Intelligent Cockpit
Next — DOT OS Platform