Guide · 8 min read

BYOD vs rented devices — the economics of a mobile test fleet

Rented device fleets are easy to spin up, expensive to keep running, and silently lossy on the bugs that matter. BYOD is harder to set up and cheaper to operate. The right answer is usually a mix — here's the math.

The per-minute meter adds up fast

A typical rental device farm charges around $0.25 per minute while you hold the device. A single smoke spec that holds the device for 6 minutes is $1.50. Run it on 8 device classes, 3 times a day, 5 days a week, and you're at $360/week just for smoke. Add perf specs, regression, rejection suite — a mid-size team hits $15-30k/month in rental alone.

BYOD, for the same coverage, costs the amortized price of the devices (usually around $3-5k per device over three years) plus the orchestrator ($299/month on Anvil's Team plan). A 20-device BYOD fleet breaks even against $18k/month rental in about two months.

Fidelity: the bugs rental farms miss

Rental farms virtualize aggressively. They share GPU resources, reset the device between sessions in ways that don't match a real user's cadence, and often strip features that would compromise isolation (carrier billing, AppAttest, DeviceCheck, certain Bluetooth and AR paths). Bugs that live in those features never surface on rented devices.

BYOD is a real device with a real SoC, a real carrier SIM, a real battery, a real thermal envelope. Performance numbers converge with what your users see. Regulatory-sensitive paths (payment, identity, health data) are testable.

When to rent

Three cases justify rental, even for BYOD-heavy teams. First: the long tail of devices you don't own — that specific Xiaomi skin, an iPad Pro 12.9 with M4, a first-gen Apple Vision Pro. Second: capacity spikes during release crunch. Third: one-off adversarial specs that require a specific OS minor you can't install on your BYOD units without bricking them.

Anvil treats rental as a flag, not a migration —--device-source=rental on any run. Your specs, your CLI, your dashboard. You pay per run, not per minute.

The on-call side

BYOD comes with a chore: somebody has to keep the devices plugged in, awake, and rebooted weekly. For a fleet under 30 devices, this is about 15 minutes a week. For 100+ it starts looking like a part-time ops role — at which point teams often colo a device lab with a remote-hands provider.

Anvil's dashboard surfaces device health inline — you see which device has been offline longest, which has thermal-throttled most often this week, which is pulling old OS versions. The chore is visible, so it gets done.

Recommended starting fleet

For a team shipping to iOS + Android: one current-gen flagship per platform (iPhone 16 Pro, Pixel 9 Pro), one mid-tier from last year (iPhone 15, Pixel 8a), one older device still widely deployed (iPhone 12 mini, Pixel 6), and one tablet (iPad 10, any 11" Android). Six devices covers ~80% of the observable perf surface. Rent the rest on demand.

Scale up when a specific device class starts generating repeat bug reports. Don't scale up preemptively — the devices sitting on the shelf are a sunk cost, the ones driving specs are an investment.

Ready to try it?

Free for 100 runs/month. No credit card.

Start free Install

Anvil