Overview
SpawnDroid runs real Android devices in the cloud and streams them into a browser, for hands on testing and automated CI test runs.
SpawnDroid runs real Android devices in the cloud and streams them into a browser. Upload an APK, a device boots on ARM64 hardware, and the running app appears on screen within seconds. From there you can interact with it, read the live log stream, or hand the same device to a CI pipeline for automated Appium tests.
There is nothing to install, no emulator to configure, and no phone in a drawer.
Two ways to work
Manual runs. Upload a build and the console boots a device for you. You drive the real app with touch and keyboard, exactly as a user would, and read its logs while it runs.
Automated CI runs. A pipeline posts a build and requests a hosted Android runner. SpawnDroid boots the device, installs the build, exposes an Appium and WebDriver endpoint, and records the outcome, the logcat capture and a screen recording when the run finishes.
Both paths share the same workspace, the same artifacts and the same device fleet, so a manual run and a CI run can point at the very same build.
The core loop
upload an APK → live device in the browser → run it by hand → debug with Logcat → automate in CIWhy it feels like a real device
Most cloud Android offerings wrap an emulator, which models a device in software and runs your app against a translation layer. SpawnDroid runs Android as a container on ARM64 server silicon, the same instruction set a modern phone uses. Your APK links against real arm64-v8a native libraries, and there is no device model and no hypervisor in the path.
The result boots like a device and behaves like a device, including native libraries, the package manager and the Android framework services your app depends on.
What you can do with a running app
- Interact in the browser. Touch, typing and scrolling are forwarded to the device, so you can reproduce a bug rather than describe it.
- Read the logs while it runs. A live logcat stream with level filters and search, plus an optional AI summary of a capture.
- Control the device. Home, Back, Recents, rotation and screenshots sit right next to the screen.
- Choose a device. Android 12, 13 and 14 on a phone or a tablet screen, with Android 14 as the default profile.
- Test in CI. Hosted Appium runners that your existing WebDriver test suite can drive without changes.
The platform at a glance
SpawnDroid is three surfaces behind one brand.
| Surface | Address | Purpose |
|---|---|---|
| Marketing | spawndroid.io | Product overview, pricing and the early access waitlist |
| Console | app.spawndroid.io | Upload, run, debug and manage CI sessions |
| Documentation | docs.spawndroid.io | Guides, API reference and integration notes |
Everything inside the console and the API is scoped to a workspace, which SpawnDroid models as an organisation. Artifacts, runners, API keys, members and sessions belong to the workspace, never to an individual account. You can switch workspaces without signing out, and a member only ever sees the workspaces they are invited to.
Plans at a glance
The Free plan is available today and includes one parallel runner. Paid tiers add more parallel runners, more seats and longer history. Concurrency, not time, is the limit that governs your day to day work. See Plans and limits for the full breakdown.
Where to go next
- Quickstart: from an APK to a running device in a few minutes.
- Core concepts: the vocabulary the rest of these docs use.
- API reference: upload builds and manage runners programmatically.
- CI tests: drive a hosted Appium runner from your pipeline.