Local Android devices
Persistent AOSP Android 15 virtual devices with separate apps, data, settings, and lifecycle.
- Multiple local devices
- Start, stop, reboot, wipe
- Persistent app data
Anfleet handles the Android tooling so the customer only installs one desktop product. Devices, apps, proxies, and disks stay on the host computer.
The beta concentrates the essential Android fleet actions in one Windows or Linux application.
Persistent AOSP Android 15 virtual devices with separate apps, data, settings, and lifecycle.
Assign an approved HTTP or HTTPS proxy to an individual local device or use the direct connection.
Open Android emulator windows and control lifecycle actions from the Anfleet desktop dashboard.
Choose and install customer-authorized APK files through ADB without using Android Studio.
Anfleet downloads and configures the official Android Emulator, platform tools, and AOSP image inside the app.
Device disks, fleet settings, and activity records remain in the Anfleet application data on the host computer.
The interface is isolated from Node.js, external navigation is restricted, and archive extraction blocks traversal paths.
Use the same Anfleet workflow on Windows x64 or Linux x86-64 with the host acceleration available on each system.
Anfleet 0.1.0 uses vanilla AOSP Android 15 through the official Android Emulator. There is no Google Play, proprietary Google services, hosted devices, physical phones, remote browser streaming, or bundled proxy access.