Agent Device
CLI to control iOS and Android devices for AI agents
Expensify uses agent-device for bug evidence. Its usage story covers collecting evidence from mobile apps and profiling.
Testing utilities in our open-source toolkit for checking React Native behavior.
What you get
Agents, runners, and devices inside your network; code and data never leave.
The QA stack in your AWS, GCP, or Azure account, under your IAM and controls.
Managed environments when speed matters more than residency.
Sensitive suites on-prem, scale workloads in the cloud, one orchestration layer.
QA agents backed by self-hosted LLMs where external inference is off the table.
Identical checks and reporting regardless of where execution lands.
Scope → Build → Scale
We select a product workflow, define where agents act, and agree the controls and success measures.
We connect context, agents, and verification to your tools, then run the workflow on your product backlog.
We document the workflow, transfer ownership, and extend it across teams and products based on results.
Case studies




On-Prem & Cloud QA Execution
On-prem, cloud, or hybrid: same agents, same evidence, your rules.
Their engineers proved to be a crucial part of our mobile app relaunch project.

We’ll connect you with the right expert within 24 hours.
Still have questions?
On-prem: nothing - code, devices, and inference stay inside. Private cloud: everything stays in your account. Hosted: build artifacts and test traffic, under the retention terms you approve.
Largely, yes. With self-hosted models and an internal device lab, the stack operates without external calls; the trade-off is model capability versus the hosted frontier.
On-prem trades subscription spend for hardware and setup; it wins at sustained scale. We model both against your test volume before you commit.
You own it after handover, with runbooks and optional maintenance agents. Most teams run it with a fraction of one engineer's time.
No. One orchestration layer routes suites by policy and merges results into a single view, wherever they executed.
Yes. The stack is the same in every mode, so starting hosted and moving on-prem - or the reverse - is a routing change, not a rebuild.