Emutize documentation
Cloud Android emulators: upload an APK, interact with it in the browser, embed it anywhere.
What Emutize is
Emutize runs Android emulators on cloud Linux boxes and streams them to the browser. Every session is an isolated, factory-fresh device that installs your app, auto-launches it, and is destroyed - storage and all - the moment the session ends.
The three pieces
| Piece | What it does |
|---|---|
| Dashboard | Upload APKs, keep an app library, launch and watch sessions. See Using Emutize online. |
| Service API | Everything the dashboard does, as Bearer-key REST calls from your backend. See the API reference. |
| Embeds | Login-free player pages designed for iframes, plus a tiny JS SDK. See the embedding guide. |
Session lifecycle
Create → a fresh device container boots (seconds) → your APK installs and launches → the browser streams the screen and sends input → the session ends (you stop it, or it idles out after 15 minutes) → the device is wiped.
A session URL is a capability link: the token inside it is the only
credential, and it dies with the session. Share it as freely as the session deserves.
Next steps
Getting started - your first session in two minutes.
Embedding guide - put live previews inside your product.