Volkswagen: OTA that stays under OEM authority
Case study. 1 page.
How Volkswagen Group cut the cloud egress cost of over-the-air updates to more than 10 million vehicles. DuoKey's key service was placed on edge servers at dealers, and signing stayed with the manufacturer. Reported results are a 95 percent cut in egress cost and a three-month payback. Get the one-page case study to see the architecture behind those numbers.

Get the download
Tell us where to send the link. A business email is required.
More than $2 billion a year in estimated cloud egress, just to deliver software updates. That was the bill Volkswagen Group faced for over-the-air updates of 500 MB to 5 GB to more than 10 million vehicles.
There were two constraints. Delivery costs grew with every vehicle and every package, and control of the signing keys had to stay with Volkswagen. One architecture solved both. Encrypted packages are cached at dealer edge servers, and DuoKey's MPC key service runs there rather than in the cloud provider's KMS.
The result was a 95 percent cut in egress cost, a three-month payback, and faster updates across the global fleet. Download the one-page case study to see how it fits together.
FAQ
What was the problem?
Update packages of 500 MB to 5 GB per vehicle were served from a central cloud. The estimated AWS egress cost was more than $2 billion a year.
What changed?
Encrypted packages were cached on edge servers at dealers and regional distribution points, with DuoKey's MPC key service running there.
What results are reported?
A 95 percent reduction in cloud egress cost, about $2 billion in annual savings, a three-month payback on the edge infrastructure, and TISAX-compliant key management.