Vehicle OS
An OEM's full software platform for its vehicles — OS kernels, middleware, APIs and cloud — such as MB.OS, Pleos or VW's CARIAD stack.
“Vehicle OS” describes an OEM’s complete software platform for its vehicles: the operating systems on the central computers, the middleware and APIs above them, the development toolchain, and usually the connected cloud backend. Mercedes-Benz’s MB.OS, Hyundai Motor Group’s Pleos, Volkswagen’s CARIAD stack and comparable programs at Toyota (Arene), NIO (SkyOS) and others all compete in this category.
A vehicle OS is not a single kernel. Under the brand name sits a mixed stack: QNX or Linux for safety and application domains, often Android Automotive OS for infotainment, AUTOSAR components, hypervisors separating criticality levels, and proprietary glue.
The strategic weight comes from control points. Whoever owns the vehicle OS defines the APIs third parties build on, controls the update pipeline and the customer relationship it enables, and decides which suppliers become interchangeable. That is why OEMs invest billions in owning it — and why partnerships and retreats in vehicle OS programs are among the sector’s biggest stories.
Related: AUTOSAR Adaptive · Central compute / HPC · Middleware (automotive) · Software-defined vehicle (SDV)