◆ Gentoo Logic · Modeling Warehouse

Architecture comparison

Cruise vs Waymo

Cruise runs closer to the foundational model (Native (own / self-hosted weights)) than Waymo (Native (own / self-hosted weights)). Shared foundation: proprietary / self-built models (highlighted).

Cruise

Autonomous

Proximity
Native (own / self-hosted weights)
Models
proprietary / self-built models
Cloud · datastore
GCPown
Compliance
SOC 2
Architecture

GM self-driving running its own perception/planning ML; restructured toward personal-vehicle autonomy.

Waymo

Autonomous

Proximity
Native (own / self-hosted weights)
Models
proprietary / self-built models
Cloud · datastore
GCPBigtableSpannerGoogle Cloud StorageProprietary in-vehicle data stores
Compliance
ISO 27001 (inferred via Alphabet/Google Cloud hosting)[4]SOC 2 (inferred via Alphabet/Google Cloud ecosystem)[4]Automotive safety and validation frameworks for AVs, including systematic safety case construction[1][8]
Architecture

Waymo’s production driver uses a modular six-layer stack (sensor processing, perception, world modeling, prediction, planning, control) integrated with HD maps, simulation, and a foundation-model-based end-to-end driving architecture that fuses camera, lidar, and radar into a unified world representation.[1][2][8][9][10] Training, evaluation, and large-scale data handling run on Google/Alphabet’s internal and Google Cloud infrastructure, with closed-source models and tooling.[1][4][5][8][10]

← Full orbit map · Score your own stack →