Proxy · MITM

Charles-style capture for everything that isn't an iPhone

Android phones, desktop browsers, backend jobs — point them at one PAC URL and their decrypted HTTPS lands in the same live feed as every other source. Full MITM power, zero per-client ceremony.

An Android phone, a browser and a backend server stream traffic into a central proxy hexagon on port 8888; one stream passes a block-and-script rule gate and comes out transformed, then one live stream flows on into a dashboard feed with green status codes. A globe marks upstream proxy routing. android browser server {} rules :8888 upstream live 200 201 200
Point any client at the proxy
bash
# Any client — point it at your per-device PAC URL:
http://<port>.busymate.net/

# Android:  Wi-Fi → Proxy → Auto-config  →  paste the URL
# Desktop:  System proxy → Automatic     →  paste the URL
# Then trust the Busymate CA once, and decrypted traffic
# streams straight into the shared live feed.

Why the proxy

The only capture path for everything off-iPhone

A per-device Charles-style MITM for Android, browsers and your own backends — with the same block/mock/script enforcement and the same live feed as every other source.

One PAC URL, any client

No SDKs, no agents to install. Anything that can talk to a proxy — a phone, a browser, a cron job — configures itself from one auto-config URL and starts streaming.

Every device keeps its identity

Each device gets its own subdomain and port, so a whole team's traffic stays cleanly attributed side by side. No more guessing whose requests those are.

Rules run at the wire

Block, mock and drop rules — and the same sandboxed JS scripting engine — run inline in the proxy itself, identical to iOS and Chrome capture. One rule set, enforced everywhere your traffic flows.

Route egress anywhere

Chain any device through an upstream or regional proxy — by country or an explicit host — straight from the dashboard. Test geo-gated behaviour without leaving your chair.

Operable without SSH

The proxy daemon reports its live build and status, streams its logs to the dashboard, and can be restarted or updated remotely. You may never open a terminal on that box again.

Related: the real-time traffic dashboardself-hosted device farmMCP server for AI agents

Connect a device in a minute

Grab your per-device PAC URL, trust the CA once, and watch decrypted traffic from any client land in the shared dashboard feed.