virtual-android-farm
Virtual Android cloud phone farm — YAML batch queue for GeeLark-style phone pools, synchronizer, and RPA workflows.
pip install virtual-android-farm
phone-farm init && phone-farm validate .phone-farm/jobs.yaml
CLI: phone-farm · Python 3.10+
Coupon hubs:
SAAS50cloud phone — anti-detect.github.io · SaaSVerdict. Get latest codes. Affiliate disclosure.
Queue cloud phone farm jobs without USB racks — same scaling pattern as GeeLark phone farms and MoreLogin ARM cloud phones.
Problem
50–150 TikTok/Instagram profiles on physical phones fail on cost, space, and sync. Teams need a validated YAML queue before batch scripts — not another spreadsheet.
Install
pip install virtual-android-farm
Quick start
phone-farm init
phone-farm validate .phone-farm/jobs.yaml
phone-farm dry-run .phone-farm/jobs.yaml
When farms stall (playbook)
| Symptom | Likely cause | Next step |
|---|---|---|
| Mass bans same day | Shared emulator signatures | ad-phone audit per device YAML |
| Jobs never run | Bad script paths | phone-farm validate from farm dir |
| Vendor lock-in | GeeLark/MoreLogin export only | mobile-vendor-bridge parse → MLX |
Coupon hubs: anti-detect.github.io · SaaSVerdict
CLI
| Command | Description |
|---|---|
phone-farm init |
Create .phone-farm/jobs.yaml |
phone-farm validate |
Schema + script paths |
phone-farm list |
Tabular job list |
phone-farm dry-run |
Enabled jobs without execute |
phone-farm --show-deal |
Opt-in SAAS50 coupons |
Limitations
- Queue planner only — does not call GeeLark, MoreLogin, or MLX APIs.
- You execute child scripts (ADB/API) yourself.
Production
Scale on Multilogin Cloud Phone folders — code SAAS50. docs/AFFILIATE.md · phone-farm --show-deal
FAQ: docs/FAQ.md
Related tools (on PyPI)
| Package | CLI | Role |
|---|---|---|
| antidetect-phone-kit | ad-phone |
Device lint |
| app-warmup-phone | app-warmup |
App cadence |
| cloud-phone-kit | cloud-phone |
Launch readiness |
| automation-farm-runner | farm-runner |
Browser mlx-pool |
License
MIT
Partner: Multilogin Cloud Phone · SAAS50 · SaaSVerdict
Open-source SDK: github.com/multilogin-automation
Metadata
Release files for virtual-android-farm 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| virtual_android_farm-0.1.5.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| virtual_android_farm-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.9 kB
Release files / virtual_android_farm-0.1.5.tar.gz
| Download URL | virtual_android_farm-0.1.5.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2c28136146bfdfc3609c2f664d31273c7a0e252d12d36e91a28f3cf6aaff3e7
|
|
BLAKE2b-256 checksum How to use checksums |
d2bfbbb4e7e92821526e83768c13fc8025a17c13a899dbaf3306f737928e604d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / virtual_android_farm-0.1.5-py3-none-any.whl
| Download URL | virtual_android_farm-0.1.5-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bd8096fe971307fd18d1c8585d43b19aa0de7bafbedbd85fe70fbd35102f11d
|
|
BLAKE2b-256 checksum How to use checksums |
751c23670adc52072fb5115d2b7a0a20989cc164aeb3b01ff0decb3da9ca6242
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for virtual-android-farm 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.