Damru — Android-Native Stealth Browser Automation

What does this agent do, and when should you use it?

Damru is an open-source stealth browser automation framework whose core idea is to avoid injecting any JavaScript into the page. Instead it boots a full Android system (Redroid) inside Docker and drives Chrome through Playwright over the Chrome DevTools Protocol. Spoofing happens at the OS, binary and protocol layers: resetprop rewrites build.prop values, Vulkan/GLES .so drivers are patched for GPU identity, libfakemem.so intercepts sysinfo via LD_PRELOAD, and wm size/density plus iptables shape display, WebRTC and IPv6 behaviour. The project bundles 155 real Android device profiles, Chrome/WebView version rotation and roughly 184 TLS/JA3 variants, and exposes AsyncDamru, Damru and DamruPool Python entry points plus a python -m damru CLI. It requires Ubuntu 24.04 or WSL2 with a bundled kernel, Docker and binderfs support, explicitly refuses physical phones, and describes itself as Beta.

At runtime Damru connects to a Redroid container over ADB, applies the selected device profile through resetprop (ro.product.model, ro.build.fingerprint, SDK level) and sets screen geometry with wm size and wm density. It patches the Vulkan/GLES driver binaries so the container reports an Adreno or Mali GPU instead of SwiftShader, loads libfakemem.so via LD_PRELOAD to intercept sysinfo/sysconf for RAM and CPU, and installs iptables rules that block WebRTC private-IP leaks and disable IPv6. Chrome-side behaviour is shaped through CDP calls such as Emulation.setHardwareConcurrencyOverride and Target.setAutoAttach so workers inherit overrides, plus Preferences/flag patching, TLS cipher rotation and DoH disablement so DNS resolves through the proxy ISP. Timezone and locale are derived from the proxy exit at session start. Users then interact through AsyncDamru/Damru page objects or CLI commands such as setup, check preflight, force-profile, stealth-open-url, benchmark, screenshot, record and ui.

1. Scraping teams that must get past Cloudflare Turnstile, DataDome or similar WAFs and want a genuine Android fingerprint rather than a desktop one.
2. Anti-bot and fingerprinting researchers who need to compare detection logic across 155 device profiles and switchable TLS/JA3 configurations.
3. Mobile QA teams that want to run end-to-end Playwright scripts against a real Android runtime instead of a desktop viewport emulation.
4. Automation engineers running several independent Android identities concurrently via DamruPool across two or three containers.
5. Researchers who want to watch or manually drive a worker through the local python -m damru ui dashboard or an optional scrcpy viewer.

How do you install or deploy this agent?

Start from Ubuntu 24.04 (or WSL2 where you accept Damru's bundled kernel), install ADB and a Python virtual environment, then install from Git and bootstrap:

sudo apt update && sudo apt upgrade -y
sudo apt install adb wget curl git jq python3-venv -y
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -U pip setuptools wheel
pip install git+https://github.com/akwin1234/damru.git

Then install host dependencies and the pre-baked Redroid image, and verify the environment:

python -m damru install-deps -y
python -m damru install-image
python -m damru check-env

The baked image is fetched from https://dl.damru.dev/assets/damru-baked.tar.gz; if you have no local tarball, use python -m damru install-image --download. The ~3.3 GB chrome-apks.zip bundle (python -m damru install-apks --download) is only needed when baking or running raw Redroid yourself.

How do you use this agent?

The smallest programmatic invocation opens a page through AsyncDamru:

from damru import AsyncDamru

async def main():
    async with AsyncDamru(chrome_apk="/home/damru/chrome-apks/145.0.7632.75") as browser:
        page = await browser.new_page()
        await page.goto("https://example.com")

if __name__ == "__main__":
    import asyncio
    asyncio.run(main())

On the CLI side, run the read-only preflight first, then apply a profile or open a URL with full stealth:

python -m damru check preflight --json
python -m damru force-profile --serial 127.0.0.1:5600 --device pixel_8_pro
python -m damru stealth-open-url --serial 127.0.0.1:5600 --url https://example.com
python -m damru ui

Proxy, timezone and locale are set in damru/config.py; when TIMEZONE and LOCALE are left as None, they are inferred from the proxy exit at session start.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ