About DroidFleet
A small team building the testing tool we wished we'd had ten years ago.
The problem
Mobile QA is broken. The market sells you exactly two options: rent virtual devices in the cloud (slow, expensive, doesn't catch real-hardware bugs), or set up a USB hub on your desk and pray ADB stays connected (fast, but only one developer at a time and only when the phone hasn't decided to disconnect itself for the seventeenth time today).
Both options ignore a simple truth: most mobile teams already have a fleet of real test phones — sitting in a drawer, on the office shelf, or in someone's backpack. They just don't have a way to use them as a coordinated test surface.
"My phones are 50 cm from my keyboard but I'm renting AWS Device Farm because I can't be bothered to set up another USB hub."
— a developer we talked to
What we built
DroidFleet turns any Android phone running our agent into a node on your test grid. The agent connects out over the internet (no port forwarding, no LAN gymnastics), pairs in 10 seconds with a stable identity, and exposes everything you need: install APKs, stream logs, capture screenshots, dump memory, record network traffic, report crashes — all from a single desktop UI or a single HTTP endpoint.
The core promise is mundane and important: your phones, your data, your control loop. No clouds you don't own. No quotas you didn't agree to. No "session expired" mid-test.
Design principles
- Phones first. Every feature must work without USB or rooted devices. If a workflow needs ADB, it's the wrong workflow.
- Boring tech. Plain HTTP, plain WebSockets, plain SQLite. We use one library where most teams use ten.
- Self-hostable. The Docker image is open and free. The cloud version is just convenience on top.
- No vendor lock-in. Every API is documented, every event has a webhook, every byte of your data is exportable.
- Pay for value, not for use. Free tier is generous; paid tiers unlock features, not arbitrary quotas.
Where we are
Public beta. The core product (pairing, install, logs, crashes, web UI, desktop wrapper) is stable and used in production by small teams. Cohorts, screenshot diffs, network recording, billing — newer; expect rough edges. Report any pain to support; we ship fixes daily.
The team
Tiny. Deliberately so. We answer support emails ourselves, write the code ourselves, and use the product ourselves. If you email us, you talk to the people building the thing.