PRODUCT · VIRTUALIZE
DeviceOps
Not an emulator. Real firmware, virtualized.
Virtual Android devices booted from official OEM firmware (Samsung One UI, Google Pixel, Xiaomi HyperOS, ASUS, Nothing OS) plus digital twins of real phones. SaaS, private cloud or on-prem.
- Who it is for
- Mobile test teams that need many identical devices on demand, and organizations that must keep devices and data on their own cloud account or in their own data center.
- Last updated
What it is
DeviceOps is a mobile device virtualization platform. It boots virtual Android devices from the official firmware of real phones, such as Samsung One UI, Google Pixel, Xiaomi HyperOS, ASUS and Nothing OS, natively on Arm servers, and creates digital twins of real devices so test teams can open, snapshot and clone exact copies of the phones their users have.
What it does
OEM firmware, virtual hardware
Upload official firmware you are entitled to use; DeviceOps rebuilds it for virtual hardware, verifies boot, ADB, display and touch and adds it to your private catalog.
Digital twins
Connect a real phone over ADB; DeviceOps captures its apps, APKs and selected settings and opens a virtual copy on the same model's firmware.
Snapshots and clones
Save disk state, roll back, or start independent devices from the same point, as many as your plan allows.
Live screen, ADB and API
Low-latency video and touch in the browser, standard adb and Android Studio through a per-device TLS tunnel, a versioned REST API and signed webhooks.
Every device in its own box
An app on a device cannot reach the host, other customers' devices or cloud credentials; ADB tunnels and live sessions end the moment access is revoked.
Audit and recordings
Every live session is recorded as video and steps with typed text masked; origin, integrity and rights status are recorded for every image.
How it works
- 01
Upload
An official OEM package you are entitled to use; its checksum and your rights declaration go into the audit log.
- 02
Verify
Each image is tested for boot, ADB, display and touch; results and limitations appear next to it in the catalog.
- 03
Launch
Open devices from the catalog, snapshot their state and start new, independent devices from the same point.
Where it sits in the lifecycle
DeviceOps is the device layer under the lifecycle: the virtual phones that RunningOps and TestingOps run mobile suites on, cloned per run from a known state.
Where it runs
SaaS on deviceops.ai on managed Arm servers; private cloud in your own AWS account with your S3 bucket, IAM role and keys; on-prem in your data center on Arm servers with KVM.
Works with
Standard adb and Android Studio, versioned REST API with idempotent requests, signed webhooks, RunningOps and TestingOps.
Frequently asked questions
- How is DeviceOps different from an Android emulator?
- An emulator runs a generic Android build. DeviceOps runs the phone maker's own system image, the same OEM interface, system apps and device identity, rebuilt for virtual hardware and run natively on Arm64 servers with no x86 translation.
- Which phones does DeviceOps support?
- More than 100 catalog images verified to boot, across Samsung Galaxy, Google Pixel, Xiaomi, ASUS and Nothing models; each image lists its limitations in the catalog.
- Do I need to provide the firmware?
- Yes, for phone-maker images. You upload official OEM firmware you are entitled to use; DeviceOps does not redistribute OEM firmware. The pipeline records the checksum and your rights declaration.
- What is a digital twin?
- A virtual copy of a specific real phone: model and firmware, installed apps and APKs, selected settings such as language, keyboard and display. Personal data, accounts, hardware keys and the secure element are not copied.
- What does not work on a virtual device?
- Camera, cellular modem, sensors and the hardware security chip are virtual. Features that depend on real secure hardware, such as Samsung Knox, mobile wallets and strong Play Integrity attestation, do not work; limitations are listed per image.
- Where can it run?
- As SaaS on deviceops.ai, as a private cloud installation in your own AWS account, or on-prem on Arm servers with KVM in your data center. The code is the same; what changes is where it runs and who holds the data.
Other products in the family
See it on your own stack.
A short call with the team: your setup, your volumes, where the product would run.