VMOS Automotive VMOS AutomotiveANDROID VIRTUALIZATION
Android Virtualization for Automotive · Full-Scenario App Ecosystem

The app ecosystem,
in every car

Whatever runs on a phone runs in the car. Apps live inside an isolated virtualization layer — never touching the underlying system, never interfering with driving. That is what makes truly opening up third-party apps possible, on new models and OTA upgrades alike.

Explore Solutions

Solutions

Multiple paths into the car

The phone app ecosystem, brought in-car as-is. One in-house virtualization engine in multiple forms: compute in the cloud or inside the head unit — choose by vehicle hardware, cost and market.

Cloud Android System

AutoCloud: the cockpit's ceiling moves to the cloud

Apps run natively on cloud ARM instances and stream into the car in milliseconds — the head unit only renders and interacts, so even aging vehicles stay fresh.

Compute lives in the cloud Apps burn cloud compute — near-zero CPU and RAM on the head unit
Complete passthrough GPS, audio focus, keys and mic — feels local
Heavy apps on low-spec units Cloud compute scales elastically; entry hardware runs big apps smoothly
Always fresh Compute and OS upgrade in the cloud — never ages with the car
AutoCloud app desktop, live client
Real shot · App desktop · ready to tap
AutoCloud live client, cloud app running
Real shot · Running · <70ms · Ultra
VMOS SDK: searching and downloading apps inside the in-car VM
Real shot · fullscreen · downloading apps in-VM
VMOS SDK floating window, live Real shot · floating window
Local Virtual Machine

VMOS SDK: phone apps, in-car without modification

A complete Android virtual machine installed as a single app — fully isolated from the host system, with the open ecosystem instantly available.

Deeply fused with the car Voice, maps, media, keys and peripherals interoperate with in-VM apps
Local & offline Apps run on local compute — no network or data plan needed
Two window modes Free-floating window with rotation, or auto-fit fullscreen
Voice AI control Voice jumps into features; see-and-say simulates taps
App Sandbox · Going Global

VMOS Lite: a featherweight sandbox for the overseas ecosystem

A featherweight, install-free app sandbox with emulated Google services — official apps like Disney+, YouTube and Waze go straight into the car.

Featherweight Minimal footprint, install-free; Android 9+ qualifies
GMS alternative Emulated Google APIs; location, accounts and verification re-implemented
Official app ecosystem Official builds, compliance-reviewed per region
Fully local Data never leaves the car or touches a cloud
Disney+
Disney+REAL SHOT
YouTube
YouTubeREAL SHOT
Waze
WazeREAL SHOT
Yandex Music
Yandex MusicREAL SHOT

Compare

A diverse lineup, covering every scenario

Start with compute: which path fits your head unit Entry-tier cockpitFlagship cockpit
SA6155 or an equivalent entry-tier SoC AutoCloud

All compute stays in the cloud; the car only runs a streaming client — heavy apps on low-spec models

<200MB RAM · <100MB storage
SA8155 or an equivalent mid-tier SoC VMOS Lite

Framework-level sandbox, the lightest local option — retrofit older head units, GMS parity for overseas models

<200MB RAM · <150MB storage
SA8295 / 8797 or an equivalent flagship SoC VMOS SDK

A full local VM with no network dependency — for local interaction and deep hardware integration

<1GB RAM · <1GB storage

Footprint figures are upper bounds under typical workloads; final numbers come from joint testing on the target model.

AutoCloudVMOS SDKVMOS Lite
In one line Cloud Android system, streamed into the car Local Android VM integrated as an SDK Featherweight install-free app sandbox
Apps run on Cloud instance In-car · full VM In-car · sandbox
Isolation Physical isolation · apps never touch the car Kernel-level full isolation · standalone VM Framework-level sandbox · per-app
Network Online (apps run in the cloud) Runs locally Runs locally
Head-unit needs Android 9+ · low compute is fine Android 12+ · needs local compute Android 9+ · minimal footprint
Recommended SoC SA6155 or equivalent entry tier SA8295 / 8797 or equivalent SA8155 or equivalent
RAM / storage <200MB RAM / <100MB storage <1GB RAM / <1GB storage <200MB RAM / <150MB storage
App ecosystem Full phone ecosystem · centrally distributed Full phone ecosystem · runs locally Allowlisted official apps · overseas GMS ecosystem
Markets Domestic · overseas Domestic · overseas Domestic · overseas
Best for OTA for cars on the road; low-spec models New models wanting local, offline experience Export models; aging head units

Not sure which path fits?

Core Advantage

Kernel to ROM, built in-house

Built on years of Android virtualization expertise: while others patch compatibility at the app layer, we cut through the Linux kernel, HAL simulation and custom ROM.

3rd-party apps
VMOS virtualization layer
isolated
Car OS · driving functions stable
01

Kernel-level virtualization

Apps run entirely inside the virtualization layer, fully isolated from the car OS — never touching the underlying system or driving stability. That is what makes opening third-party apps safe.

  • File · Binder · network triple isolation
  • No root, no reboot, no reflash
  • Multi-instance with data isolation
  • Zero interference with driving functions
Play Integrity check: Basic / Device / Strong all green
TB Checker: real-device fingerprint, Play integrity all pass
Real shots · all green + device fingerprint
02

HAL hardware simulation

A full set of virtual hardware — camera, sensors, SIM, audio, positioning — simulated to behave like real silicon, so apps never notice they run in a virtual environment.

  • Parameter library of 1,000+ real devices, simulated in one tap
  • Google Play Integrity: all three tiers passed
  • Virtual location · sensors · SIM
Android images, self-owned
Android 10 10 Android 11 11 Android 12 12 Android 13 13 Android 14 14 Android 15 15 Android 16 16 Android 17 17
03

Deep ROM customization

Our own images across Android 10–17, trimmed and customized for automotive compliance, centrally managed in the cloud.

  • Full-version system images, self-owned
  • Automotive compliance & brand tailoring
  • Centralized image management & staged rollout
Local · Light
VMOS LiteVMOS Lite
VMOS SDKVMOS SDK
AutoCloudAutoCloud
Cloud · Full
04

Full-scenario coverage

From local to cloud, light to full — app sandbox, local VM and cloud Android share one engine and combine freely by vehicle and scenario.

  • Multiple forms · one engine
  • Local and cloud combine freely
  • Choose by vehicle compute and target market

Business · Official channels

Drive the app ecosystem into your next vehicle

Solution consulting / ecosystem partnership / distribution