A programmatic browser instance manager — with a live viewer and local dashboard

Damru gives developers a code-first browser instance manager: spin up and orchestrate pools of real Android browser instances with DamruPool, watch and drive any one of them live with Damru View, and run the whole environment from the local Damru UI dashboard.

Where GUI antidetect tools (Multilogin, GoLogin, AdsPower) put instance management behind a point-and-click panel, Damru keeps it in your codebase — every instance is defined, launched, and scaled from Python, then observed through an optional local UI. Built for web scraping within terms, automation/QA testing, and anti-bot research.

What is a browser instance manager?

A browser instance manager is the layer that creates, tracks, scales, and shuts down isolated browser sessions so each one carries its own identity and state.

In commercial antidetect tools this is a GUI that stores "profiles." In Damru, an instance is a real Android browser inside a Redroid container, and the manager is your code: DamruPool maintains the containers, rotates per-worker proxies, and hands you a Playwright BrowserContext from pool.session().

from damru import DamruPool

async with DamruPool(mode="auto", max_devices=10) as pool:
    async with pool.session() as ctx:          # one isolated Android instance
        page = await ctx.new_page()
        await page.goto("https://example.com")

How do I watch and control a running instance? (Damru View)

Damru View opens a live scrcpy stream of any running worker, so you can watch automation in real time or take manual control.

Run python -m damru view --serial <worker> to drive the device, or add --no-control for a watch-only stream that is safe to leave open during an automation run. It is the developer equivalent of "open this profile's browser window" in a GUI tool — except it is a genuine Android screen, not a desktop Chromium window.

# Watch + control a worker
python -m damru view --serial wsl:127.0.0.1:5600

# Watch-only (safe during a live run)
python -m damru view --serial wsl:127.0.0.1:5600 --no-control

What is the Damru UI dashboard?

Damru UI is a local-only web dashboard (http://127.0.0.1:<port>) for setting up, running, and inspecting your instances without writing throwaway scripts.

Launch it with python -m damru ui. It runs on an allowlisted backend and never exposes the environment to the network by default.

python -m damru ui   # opens the local dashboard

The UI is for setup, debugging, and manual inspection — production automation should still run through AsyncDamru / DamruPool.

Code-first instance management vs GUI antidetect tools — an honest comparison

Damru and tools like Multilogin, GoLogin, and AdsPower solve overlapping problems with opposite philosophies: Damru manages instances in code and adds an optional local UI; they manage profiles in a GUI and add an optional API. Neither is "better" universally — pick by workflow.

If your team is non-technical and needs durable, shareable profiles with a managed cloud, a GUI tool is the pragmatic choice — Damru is for teams who want the instance layer in code, owned end to end. For developers who already script with Playwright, the migration cost is near zero because pool.session() returns a standard BrowserContext.

FAQ

Related: how it works · device profiles · full comparison · docs.