Cars increasingly compete on something owners never see under the hood: the speed and quality of the software-development process. Volvo Cars is now making a significant change behind the scenes, migrating its global Android Automotive Operating System development environment to Horizon, an open-source platform created by Google Cloud and Accenture.
Volvo will serve as Horizon’s lead automotive industry partner, giving its engineers cloud-based development tools, virtual testing environments and AI-assisted workflows. The move builds on nearly a decade of collaboration between Volvo and Google, but its importance stretches beyond infotainment. As vehicles become more dependent on software that can be updated throughout their lives, the race is shifting toward automakers that can build, test and release reliable code faster — without requiring every engineering task to wait for physical prototype hardware.
A Development Shift, Not Just a Hosting Change
The most important detail in Volvo’s announcement is its scope. Volvo Cars is migrating its global Android Automotive OS, or AAOS, software-development environment to Horizon. The platform itself runs on Google Cloud and combines the infrastructure and tooling needed to build, test and deploy automotive software. Volvo has also been named the lead industry partner, meaning it will do more than simply consume a finished product.
That distinction matters because this should not be interpreted as every piece of Volvo vehicle software suddenly moving into Google Cloud. The announced migration specifically covers its AAOS development environment. Volvo engineers will work with Google Cloud and Accenture as Horizon evolves, with lessons from Volvo’s engineering challenges helping refine the platform. Gregor Zetsche, Volvo Cars’ head of connected experience, described modern cars as some of the most complex products being built today. Horizon is intended to reduce some of the engineering friction surrounding that complexity before software reaches a production vehicle.
Horizon Turns the Toolchain Into a Shared Cloud Platform
Automotive software development can involve a surprisingly fragmented collection of tools. Engineers need environments for managing source code, compiling enormous Android builds, running compatibility checks, creating virtual vehicles and validating software on physical hardware. Horizon attempts to bring those stages into a more standardized cloud-based system rather than leaving individual teams to maintain separate development setups.
The open-source project describes itself as an AI-native toolchain covering code, build, test and release activities. It can be deployed inside an organization’s Google Cloud environment using infrastructure technologies including Terraform and Argo CD. Earlier Horizon releases included Gerrit for Android source management, Jenkins-based build pipelines and support for virtual Android devices. More recent releases have added Android 15 capabilities and AI-assisted analysis of failed builds and test results. For Volvo, the attraction is therefore broader than renting additional computing power. The company is adopting an environment designed specifically around the repetitive engineering work required to develop increasingly software-heavy vehicles.
Virtual Cars Can Replace Some Waiting for Physical Hardware
One of Horizon’s most consequential features is its use of virtual Android Automotive environments. The platform relies on Cuttlefish, Google’s configurable virtual Android device technology, to create software representations that developers can run remotely and in parallel. Google’s own Android documentation says Cuttlefish is intended partly to reduce developers’ dependence on physical hardware while maintaining close alignment with the behaviour of real Android devices.
That can change a familiar bottleneck in automotive development. Traditionally, an engineer testing an infotainment change might need access to a development bench, an electronic control unit or even a prototype vehicle. Those resources are expensive, limited and often located thousands of kilometres from part of a global software team. Virtual environments cannot replace every real-car validation step, especially where physical hardware and safety-critical behaviour are involved. They can, however, allow far more routine development and automated regression testing to begin earlier. Horizon’s developers say virtual instances can also be scaled in large numbers, allowing many tests to run simultaneously instead of waiting for one scarce test bench.
Build and Test Cycles Are the Main Target
For software engineers, a two-hour build can turn a small code change into most of an afternoon. Horizon is designed specifically to attack that type of lost time. Google Cloud and Accenture say intelligent caching and optimized pipelines can bring feedback that previously took as long as two hours down to minutes. The partners also claim testing can be up to nine times faster with virtual Cuttlefish-based AAOS environments.
Those figures should be understood as performance claims from the companies developing the platform rather than independent industry benchmarks. Still, earlier Horizon deployments provide additional context. Google Cloud reported in 2025 that initial work with roughly half a dozen automotive partners had produced developer feedback between 10 and 50 times faster in certain workflows. Its Android Build File System integration was also designed to drastically reduce repeated build work through caching. For Volvo, even less dramatic improvements could matter. Thousands of shortened build-and-test cycles accumulated across global engineering teams can translate into considerably more engineering time spent fixing problems and developing customer-facing features.
Global Engineering Teams Could Feel the Difference Daily
Cloud-based automotive development becomes especially useful when engineers are spread across countries and time zones. Horizon provides remote access to both virtual environments and physical device farms, allowing developers to validate software without necessarily being beside the hardware being tested. According to Google Cloud and Accenture, virtual workbenches can also be created rapidly instead of requiring specialized physical equipment to be shipped and configured.
Google Cloud Workstations follows the same philosophy. Administrators can define reproducible development environments that engineers access through a browser, local development software or secure connections. That reduces the risk that one developer has a slightly different configuration from another — the classic software problem where code works perfectly on one machine and inexplicably fails elsewhere. For an automaker operating globally, consistency can be just as valuable as raw computing speed. A developer joining a Volvo software team in one region can theoretically begin with an environment much closer to the one used by colleagues elsewhere instead of spending days rebuilding an elaborate local setup from scratch.
Open Source Gives Automakers More Room to Adapt
Horizon is not being positioned as a completely closed Google product. Its source code is publicly available under an Apache 2.0 licence, and its architecture is designed to be modular. Organizations can adopt individual components rather than replacing an entire engineering organization’s tooling at once. The project currently encompasses Android Automotive development while also expanding toward other parts of the software-defined vehicle stack.
That openness is significant in an industry where manufacturers are cautious about allowing a single technology company to control too much of their vehicle architecture. Horizon can be deployed within a company’s own Google Cloud project and customized around existing systems. There is also an important caveat: Horizon’s GitHub documentation explicitly states that the open-source project is not an officially supported Google product. That does not contradict Volvo’s partnership with Google Cloud and Accenture, but it illustrates the platform’s hybrid character. It is simultaneously an open development initiative and the foundation for enterprise automotive implementations being built with major industry partners.
Volvo and Google Have Been Moving Toward This for Years
The Horizon decision makes more sense when viewed as the latest stage in a relationship that began long before today’s software-defined vehicle boom. Volvo and Google announced their Android-based infotainment partnership in 2017. By 2019, Volvo was preparing the electric XC40 with Android Automotive OS, Google Maps, Google Assistant and Google Play integrated directly into the vehicle rather than requiring a connected smartphone.
The relationship deepened again in May 2025 when Volvo became one of Google’s reference hardware platforms for future automotive Android development. That gave Google an opportunity to test upcoming Android features using Volvo vehicles before those changes entered the broader Android codebase. In April 2026, Volvo also began rolling out Google Gemini to eligible vehicles, extending the partnership into generative AI. Horizon shifts the collaboration farther upstream. Instead of concentrating only on what the driver sees on the centre display, Google technology is becoming increasingly involved in the development machinery Volvo engineers use to create and validate those experiences in the first place.
OTA Scale Makes Development Speed Matter to Existing Owners
Faster software development has little customer value if improvements cannot leave the engineering department quickly. Volvo has spent years building the other half of that equation: over-the-air updates. In March 2026, the company launched what it described as its largest OTA software update, sending the redesigned Volvo Car UX to approximately 2.5 million vehicles across 85 countries.
The particularly notable part was the age of some vehicles receiving it. Compatible Volvo models with Google built-in dating back to 2020 were included, allowing cars already several years old to gain a redesigned interface without visiting a dealership. That turns software-development efficiency into something existing owners can potentially notice. If Horizon helps teams find bugs earlier, validate releases faster and shorten feature-development cycles, Volvo has a large installed fleet capable of receiving at least some of those improvements. The traditional automotive cycle — where major technology changes effectively waited for a new model year — is steadily giving way to a model in which part of the ownership experience continues evolving after delivery.
Cloud Tools Still Cannot Erase Hardware Limits
The move toward virtual development and OTA updates does not mean hardware has stopped mattering. Volvo’s EX90 provides a useful example. Owners of 2025-model-year EX90s are being offered a complimentary upgrade to a more powerful dual-NVIDIA DRIVE AGX Orin core computer. Volvo says the upgraded configuration provides additional processing capacity for new and improved functionality and is required for software that the original configuration cannot support.
The 2026 EX90’s dual-Orin setup provides up to 500 trillion operations per second of computing capability, according to Volvo. Because the associated software depends on the additional processing power, that particular upgrade requires a physical workshop visit rather than an OTA installation. It is a reminder that software-defined vehicles remain physical machines with finite computing resources. Cloud development can make engineers more productive, and virtual vehicles can reduce dependence on prototype equipment during development, but the production car eventually has to execute that code safely and reliably. Hardware, software and cloud infrastructure therefore have to advance together rather than replacing one another.
The Timing Fits Volvo’s Bigger Product Push
Volvo’s Horizon migration arrives while the company is preparing an unusually ambitious product expansion. In September 2026, Volvo said it intends to introduce 13 new models by the end of 2030 — six aimed at China and seven at Western markets — while pursuing a long-term profitability target above 8%. Western-market vehicles are expected to share two principal Volvo platforms as the company tries to reduce development and investment costs.
Software reuse and standardized development infrastructure fit naturally into that strategy. More models normally mean more combinations of displays, processors, vehicle functions and market-specific requirements to support. If every program develops software through different processes, complexity can rise almost as quickly as the model count. Horizon represents an attempt to standardize more of that invisible engineering foundation while Volvo differentiates the vehicles themselves through design, safety, features and driving experience. The broader automotive race is increasingly about scale: not simply how many cars an automaker can manufacture, but how efficiently it can develop, test and continuously improve the software running across an expanding global fleet.
