Industry · IT & Security
Security testing on real phone models.
Install your build on a real phone model, inspect it over ADB, and keep the logs and crashes of every run, with access opened only when you need it.
01 · What you can run
What security teams run.
Pre-release checks
Install each build and review how it behaves before release.
Log review
Logcat and crash reports collected from every run.
Permission checks
See which permissions the app asks for, and when.
Access audit
Every ADB session and API call is tied to a key or a person.
02 · Get started
Two ways in. Live in minutes.
For developers
API, SDK or MCP.
- Get a key. Sign up, open API & MCP and copy your
cl_live_key. - Connect.
pip install clousd, or add the MCP server to Claude Code, Codex or Cursor. - Run. Ask your agent: “Install this APK and list the permissions it requests”
No code
The dashboard.
- Create a phone. Devices → New device, pick a model and an Android version.
- Open it. See the screen live and control it with your mouse and keyboard.
- Install your app. Upload an APK or pick one from the catalog.
Questions, answered.
Can I test apps that are not released yet?
Yes. Install any APK from the dashboard, the API or ADB.
Is ADB open to the internet?
No. You open it per phone for the IP addresses you list and for a set time.
Who can reach a phone?
Only people on your team with access to it, and API keys you scope to it.