---
title: BMW moved its connected vehicle platform to Graviton: 57 percent less ingress CPU
type: Architecture
date: Oct 29, 2026
point: BMW Group migrated the platform behind more than 24.5 million connected vehicles from x86 to Arm-based AWS Graviton without service disruption. The recipe was platform-first, not big-bang: Karpenter for flexible node pools, dual build pipelines producing multi-architecture images, and dedicated Graviton node pools that workloads opt into with taints and tolerations, so any team could roll back to x86 with no rebuild.
time_saved: Original ~12 min → 25 sec here
---
title: BMW moved its connected vehicle platform to Graviton: 57 percent less ingress CPU
type: Architecture
date: Oct 29, 2026
point: BMW Group migrated the platform behind more than 24.5 million connected vehicles from x86 to Arm-based AWS Graviton without service disruption. The recipe was platform-first, not big-bang: Karpenter for flexible node pools, dual build pipelines producing multi-architecture images, and dedicated Graviton node pools that workloads opt into with taints and tolerations, so any team could roll back to x86 with no rebuild.
time_saved: Original ~12 min → 25 sec here
---
Load the full post
Why it matters
A clean pattern for any large x86 to Arm migration: make both architectures first-class, let teams adopt at their own pace, keep rollback free.
Key details
- NGINX ingress CPU consumption dropped about 57 percent, and price-performance improved about 40 percent
- About $600,000 in annualized infrastructure savings; more than 65 percent of the platform now runs on Graviton
- The platform runs over 130,000 builds and deployments a day, which continued through the migration