Global teams at scale rarely pick one tool. They run cloud phones for app trust and Multilogin (or peers) for web identity. Failure happens when layers share credentials, proxies, or operators without a map.
Reference architecture
┌─────────────────────────────────────────────────────────┐
│ Account (client_id) │
├──────────────────────┬──────────────────────────────────┤
│ MOBILE LAYER │ WEB LAYER │
│ Cloud phone device │ Multilogin profile (Mimic) │
│ Mobile / 4G proxy │ Sticky residential proxy │
│ TikTok / IG app │ Meta BM / Ads / Seller web │
│ ADB ops (optional) │ Playwright CDP automation │
└──────────────────────┴──────────────────────────────────┘
│ │
└──────── CMDB row ───────┘
geo, tier, ban_status
CMDB fields per account
| Field | Example | Why |
|---|---|---|
client_id | acme_eu | Agency boundary |
cloud_device_id | geelark-8842 | Mobile identity |
mlx_profile_id | uuid-… | Web identity |
geo | DE | Both layers aligned |
mobile_proxy | resi-de-mobile-03 | App layer only |
web_proxy | resi-de-sticky-11 | Browser layer only |
tier | warm | prod | burn | Automation routing |
Automation boundaries
- Never automate Meta BM login from cloud phone browser WebView
- Never share cookies exported from Multilogin into mobile app
- Queue jobs by layer — separate workers for ADB vs CDP (scaling)
- Observability — ban rate per device AND per profile, not global average
Implementation recipes
ADB (mobile ops)
Playwright (web ops)
Ban recovery runbook
Profile pool manager
Hybrid architecture (VI)
Platform playbooks
Disclosure: MLX-MMO affiliated with Multilogin. Architecture is vendor-agnostic for cloud phones.