Not an emulator.Real firmware, virtualized.
The phone's own operating system, booted from official OEM firmware on virtual hardware. Plus digital twins of the real devices you test against.
Build a device image once and launch as many identical devices as you need. Test live in the browser, connect over ADB, automate with an API and webhooks. In our cloud, your cloud or your data center.
Camera, modem and hardware security chip are virtual. Every image lists its limitations in the catalog.
Ask for a device. Get it running.
A developer, a tester or a product owner asks for the phone they need. DeviceOps boots it on virtual hardware in seconds, then the next one, and the next.
- Developerlaunch “Galaxy S24 Ultra”Running
- Testerlaunch “iPhone 15 Pro”Running
- Product ownerlaunch “Xiaomi 14”Running
Illustration. Brand names are used to describe compatible devices; DeviceOps is not affiliated with these companies.
Virtualize
Upload official firmware for the models you support. DeviceOps rebuilds it for virtual hardware, verifies it and adds it to your catalog. Open a device in seconds, as many as your plan allows.
Twin
Connect a real phone and capture its apps and settings. DeviceOps opens a virtual copy on the same model's firmware, ready to test, reset and clone.
From firmware to a testable device in three steps.
Upload firmware
Upload an official OEM package you are entitled to use. Its checksum is recorded and your rights declaration goes into the audit log.
Verify
Each image is tested for boot, ADB, display and touch. Results and limitations appear next to the image in the catalog.
Open, snapshot, clone
Launch devices from the catalog, save their state as a snapshot and start new, independent devices from the same point.
Test on a copy of the phone your user actually has.
Reproduce a bug on the exact app set and settings of a real device, without passing the device around.
Plug in a real phone
Connect it over ADB from your machine. DeviceOps identifies the model and finds its firmware in your catalog.
Capture apps and settings
The installed app list, APKs and selected system settings are captured and kept private to your organization.
Launch the twin
A virtual device on the same model's firmware starts with the captured setup. Snapshot it, reset it, clone it for the whole team.
Everything a test team uses every day.
Live screen in the browser
Low-latency video and touch. Access is granted per device; revoke it and the stream stops within seconds.
Secure ADB
Standard adb and Android Studio connect through a per-device, time-limited TLS tunnel. No open ports.
Snapshots and clones
Save disk state, roll back, or start independent devices from the same state.
API and webhooks
Versioned REST API with idempotent requests, operation records and signed webhook events.
Session recordings
Every live session is recorded as video and steps: who did what, on which device. Typed text is masked by default.
Firmware you can trust
Origin, integrity, signature and rights status are recorded for every image, along with what it does and does not emulate.
One product, three places to run it.
The code is the same. What changes is where it runs and who holds the data.
SaaS
Fastest startOn deviceops.ai, on managed Arm servers. Organizations are isolated from each other.
- First device in minutes
- Backups, monitoring and updates handled by us
- Quotas and plan limits per organization
Private Cloud
In your own AWS account, with your domain and your keys. Data never leaves your account.
- Your S3 bucket and IAM role
- Single tenant, dedicated servers
- Install and upgrade scripts
On-prem
In your data center, on Arm servers with KVM. Devices and data stay on your network.
- Your certificates and internal DNS
- Webhooks to receivers on your network
- Local backups under your policy
Every device in its own box.
An app running on a device cannot reach the host, other customers' devices or cloud credentials. We don't assume it; we measure it.
Network isolation
No access from a device to the host, the internal network or the metadata service; no device-to-device traffic.
Identity and roles
Organizations, roles and scoped, expiring API tokens. Every change lands in the audit log.
Revocable access
ADB tunnels and live sessions end the moment access is revoked; media flows only through our own TURN relay.
Encrypted and backed up
Encrypted disks and storage, nightly backups, restore drills, continuous monitoring and alerts.
Plans
Pricing depends on device count, concurrency and where DeviceOps runs. Tell us what you need.
Starter
For testers who need real phones on demand.
- 1
- devices running at once
- 1
- users
- 240 h
- device hours per month
- Live screen and touch in the browser
- Secure ADB and Android Studio
- Your own firmware catalog
- Digital twins of real phones
- Snapshots, restore and clones
- API v1 and signed webhooks
- Public device catalog
- Session recordings
Team
For QA teams and CI pipelines.
- 5
- devices running at once
- 5
- users
- 1,200 h
- device hours per month
- Everything in Starter
- Secure ADB and Android Studio
- Your own firmware catalog
- Digital twins of real phones
- Snapshots, restore and clones
- API v1 and signed webhooks
Enterprise
For organizations with their own rules.
- 20
- devices running at once
- 20
- users
- 4,800 h
- device hours per month
- Everything in Team
- Secure ADB and Android Studio
- Your own firmware catalog
- Digital twins of real phones
- Snapshots, restore and clones
- API v1 and signed webhooks
- Private Cloud or On-prem
- Dedicated servers
- Capacity planned with you
Questions teams ask about DeviceOps.
What is DeviceOps?
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, on Arm servers. It also creates digital twins of real devices, so test teams can open, snapshot and clone exact copies of the phones their users have.
How is DeviceOps different from an Android emulator?
An Android 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. Devices run natively on Arm64 servers (AWS Graviton in our cloud) with no x86 translation.
Which phones does DeviceOps support?
More than 100 catalog images are verified to boot, across Samsung Galaxy, Google Pixel, Xiaomi, ASUS and Nothing models. Each image is tested for boot, ADB, display and touch, and its limitations are listed next to it in the catalog. New models are added through family recipes.
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, rebuilds the firmware for virtual hardware, verifies it and adds it to your organization's private catalog.
What is a digital twin in DeviceOps?
A digital twin is a virtual copy of a specific real phone. You connect the phone over ADB; DeviceOps identifies the model, captures the installed apps, APKs and selected settings such as language, keyboard and display, and launches a virtual device on the same model's firmware with that setup. Personal data, accounts and hardware keys are not copied.
How do testers and CI tools connect to the devices?
Testers use the live screen and touch in the browser. Developers connect standard adb and Android Studio through a per-device, time-limited TLS tunnel. Automation uses the versioned REST API and signed webhooks. Every live session is recorded as video and steps.
Where can DeviceOps run?
In three places with the same code: as SaaS on deviceops.ai, as a private cloud installation in your own AWS account with your S3 bucket and IAM role, or on-prem on Arm servers with KVM in your data center.
What doesn't work on a virtual device?
The camera, cellular modem, sensors and 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. DeviceOps lists these limitations for every image.
Let's run your firmware as a virtual device.
Tell us which models you test and where you want DeviceOps to run.