Anbox Cloud on C4A metal: Android, at scale, without friction

If you’ve spent even a small portion of time working with Android development at scale, you’ve likely encountered some pinch points. The platform was built for Arm-based devices, mobile physical hardware, and tightly controlled system environments. Cloud platforms, on the other hand, are optimized for abstraction, elasticity, and shared infrastructure. Anbox Cloud has already bridged this gap, enabling Android developers to scale virtual instances in the cloud efficiently. Yet, even with this flexibility, some use cases and workloads, like system-level Android development or large-scale Cuttlefish farms, call for native Arm performance and direct hardware access.

For years, developers had to choose between genuine Android execution with physical device labs and cloud efficiency. With the launch of Google Cloud’s new Axion-based bare-metal instance, C4A metal, that trade-off starts to disappear. C4A-metal brings native Arm hardware directly into the cloud, without the performance limitations or complexity of nested virtualization. For Android workloads, this is a big deal. And it’s the perfect fit with Anbox Cloud.

Anbox Cloud is Canonical’s platform for running Android at scale in cloud environments. It was built to manage, scale, and stream large numbers of Android instances reliably, whether for testing, CI/CD integration, automation, or interactive remote access. On C4A metal, Anbox Cloud can run and orchestrate large fleets of Android systems directly on Arm hardware. There’s nothing special to configure, no alternative workflows to learn. You provision C4A metal, deploy Anbox Cloud, and Android workloads run exactly as you would expect, only now with native performance and cloud elasticity.

“Anbox Cloud’s support for fully virtualized Android provides an execution environment that closely matches the assumptions of AOSP and reference platforms such as Cuttlefish,” says Alistair Delva from Google’s Cloud Android team.