Service

Device Cloud & Private Labs

Real device coverage at the scale your traffic demands

500+
Real physical devices
40+
Carrier networks available
80%
User population coverage

What this service delivers

Emulators miss device-specific rendering bugs, hardware sensor failures, and carrier-network interactions. Our managed device cloud and private lab options give you access to hundreds of real physical devices, from flagship iOS to low-memory mid-tier Android, for manual, automated, and exploratory testing.

  • 500+ real physical devices: iOS 14–18 and Android 10–15
  • Low-memory device coverage (2GB RAM) for mid-tier Android accuracy
  • Carrier network simulation: 3G, 4G LTE, 5G, WiFi, and transitions
  • Private device reservation for sensitive data and financial compliance
  • Remote manual access with live device view for exploratory testing
Wall of real mobile devices in a professional device lab for comprehensive testing

Available in

FoundationGrowScaleEnterprise
Compare plans & pricing

Our approach

How we deliver device cloud & private labs

A structured, evidence-based methodology that produces findings your team can act on, not reports that sit in a folder.

1

Traffic-weighted device matrix selection

We analyse your app's analytics to extract the actual device model, OS version, screen resolution, and RAM configuration distribution of your user base. We construct a matrix that covers 80%+ of your population with the minimum number of devices, prioritising the models where crashes and ANRs appear disproportionately in your crash reporting rather than defaulting to the latest flagship.

2

Cloud vs. private lab configuration

For most teams, our managed device cloud provides cost-effective access to the full matrix without infrastructure overhead. For teams handling PCI, HIPAA, or sensitive financial data, we provision private device labs, dedicated physical hardware accessible only to your team, with full data wipe between sessions and compliance documentation for audit purposes.

3

Carrier network and connectivity testing

We deploy HeadSpin nodes co-located with major carrier networks to provide testing under authentic 4G and 5G signals, not simulated throttling. This is critical for apps with real-time features, geolocation, payment processing, and push notification delivery, where behaviour under carrier-specific network conditions differs from laboratory WiFi.

4

Remote access and exploratory sessions

Engineers and QA teams access live devices via high-fidelity remote sessions with sub-100ms latency for exploratory testing, manual reproducing of bug reports, and live debugging during development. Session recordings are retained for 30 days and available for defect evidence.

What you receive

Every engagement delivers a defined set of artefacts. No ambiguity about what you're buying.

Discuss scope
Deliverables included in Device Cloud & Private Labs
DeliverableDescription
Traffic-weighted device matrix
Recommended device list with OS versions, rationale based on your analytics, and expected population coverage percentage.
Lab setup documentation
Device inventory, access procedures, data management policy, and compliance documentation for private labs.
Carrier network test report
Connectivity behaviour under 3G, 4G, 5G, and WiFi-to-cellular handoff conditions per device.
Remote access configuration
Device cloud account setup, API credentials for CI integration, and team access provisioning.
Matrix optimisation review
Quarterly analytics-driven review of device matrix accuracy as your user demographics evolve.
Tools and technologies used in Device Cloud & Private Labs
ToolCategory
BrowserStack App LiveCloud devices
Sauce Labs Real DevicesCloud devices
KobitonAI-enhanced cloud
HeadSpinReal device + network
PerfectoEnterprise cloud

Tools & technologies

We use the tools your team already knows where possible, and introduce specialist tooling where it provides accuracy or coverage advantages you can't get otherwise.

Engagement phases

What the engagement looks like from brief to delivery, so your team can plan sprint integration points from day one.

Phase 1Days 1–2

Matrix design

  • Analytics data review
  • Device model and OS version prioritisation
  • Coverage percentage calculation
Phase 2Days 3–5

Lab provisioning

  • Cloud account configuration or private lab setup
  • Carrier network node provisioning
  • CI/CD integration
Phase 3Days 6–7

Validation

  • Access verification
  • Parallel execution test run
  • Remote session latency check
Phase 4Quarterly

Ongoing

  • Matrix optimisation review
  • Device refresh recommendations
  • Coverage gap analysis

Device Cloud & Private Labs, questions your team asks first

Emulators cannot replicate hardware-specific bugs, GPU rendering differences, thermal throttling, sensor behaviour, carrier network interactions, and the performance characteristics of specific RAM configurations found in real Android devices.

Discuss Device Cloud & Private Labs for your app

Talk to a test architect about your stack, release cadence, and the specific failure modes you're trying to prevent. We'll scope an engagement that fits your sprint cycle.