Marathon Cloud vs Gradle Managed Devices
Gradle Managed Devices provisions Android emulators on the build machine, restores clean state with snapshots and can shard device profiles within that machine’s resources. Marathon Cloud provisions Android emulators and iOS simulators for each run, sizes the pool from suite history and retries failed tests on a different device.
Where tests run
Parallelism
Gradle Managed Devices
Shards per device profile via android.experimental.androidTest.numManagedDeviceShards; total instances = devices × shards; docs warn provisioning can time out when the machine lacks resources.
sourceRetries and reruns
Clean state
Platforms
Price
CI without GPU
Getting started
Competitor facts verified 2026-09-29 from the vendor's public pages.
A Gradle Managed Devices alternative when one CI machine is no longer enough
Gradle Managed Devices provisions Android emulators and shards on the build machine, with provisioning bounded by that machine’s resources. Marathon Cloud provisions Android emulators and iOS simulators per run and sizes the device pool from suite history to target 15 minutes.
Choose Gradle Managed Devices when
- Your suite fits comfortably on one CI machine and you only ship Android.
- You want zero external services in the build.
Choose Marathon Cloud when
- Shards on one machine hit the provisioning timeout or the machine's core count.
- You also run XCUITest or Maestro on iOS.
What a run costs on Marathon Cloud
A suite with 120 minutes of total test time runs on 8 devices for about 15 minutes: 2 device-hours, $4.00 on Android or $6.00 on iOS.