Trova la richiesta che fallisce. Verifica la correzione.
Ogni dispositivo in un’unica tabella live. Metti in pausa una richiesta, rispondi con un finto o riproducila.
Find it.
Filtra fino alla richiesta che ti interessa, poi modificala o riproducila.
Il firehose live
Ogni richiesta entra in una tabella ordinabile nell’istante in cui arriva. Nessun pulsante di ricarica.
Mocka qualsiasi cosa
Rispondi a una richiesta corrispondente con status, header e body tuoi — o scartala.
Scripta il filo
Gli hook JS riscrivono header e body dal vivo, con un tester dry-run perché uno script rotto non fermi mai la cattura.
Breakpoint
Metti in pausa il traffico corrispondente, modifica l’HTTP grezzo, continua o rinvia.
Diff tra funzionante e rotto
Fissa le entry e confronta richieste e risposte grezze fianco a fianco.
Esporta, programma, decodifica
Esporta HAR, pianifica snapshot, decodifica protobuf e gRPC.
Device to dashboard,
No upload step and no poll loop — capture writes a row, Realtime fans it out, and control flows back down the same wire.
- 01
Every source writes the same row
iPhone tunnel, Android VpnService, the MITM proxy, Chrome over CDP, farm phones — each captured request becomes one identical entry row the moment it completes. One shape, every platform, no importer.
- 02
Realtime pushes it to the feed
The dashboard holds a WebSocket subscription to your workspace's broadcast channel; a committed entry lands in the live table without a refresh or a poll loop.
- 03
Control rides the same wire back
Hold a matching request at a breakpoint, edit the raw HTTP, continue or abort — or resend a past request. The capturing device answers over its own Realtime channel in seconds.
- 04
Settings save once, apply everywhere
SSL lists, block and mock rules, and rewrite scripts push live to every affected device — globally, per service group, or per device. No redeploys, no app updates.
More than
The feed is the front door; the same workspace carries explorers, boards and device controls for the whole stack.
- Capture sources
- iOS · Android · MITM proxy · Chrome (CDP) · device farm
- Feed transport
- Push in tempo reale su un WebSocket persistente — una voce compare nell'istante in cui viene registrata, mai con un timer di polling
- Volume sostenuto
- 205,000 richieste catturate — circa 8.81 GiB di traffico — attraversano il feed live ogni giorno (flotta di produzione, misurato a luglio 2026)
- Workspace model
- Per-user tabs with saved filters; Devices, Services and Domains panels scope the feed
- Interception
- breakpoints · mocks · block rules · JS rewrite scripts
- API explorers
- MCP · REST · WS — self-documenting in-app consoles
- Team boards
- todo · roadmap · farm · tester
- Device control
- Live screen share with saved recordings, remote VPN toggles, renames and health — per device
- Access control
- Role-based permissions and workspace scoping, enforced by the database itself (row-level security)
Dashboard questions,
Do I need to install anything to use the dashboard?
No. It's a web app — sign in and the live feed starts the moment any paired device or proxy client captures traffic. Capture happens on the devices; the dashboard is the control room.
How fast do entries show up?
Entries stream over a persistent WebSocket as rows commit — the feed updates in real time, with no refresh button and no polling interval to tune.
Can my whole team watch the same traffic?
Yes. The feed is workspace-scoped, so every member sees the same devices side by side, while tabs and filters stay per-user and role-based access control decides who may view or change what.
Can AI agents work with the same data?
Yes — every dashboard read and write is mirrored by the MCP server, the REST surface and the WS channels, so an agent can search entries, flip settings or continue a breakpoint with the same permissions you have.
See your traffic
Guarda le richieste arrivare da ogni dispositivo connesso — poi restringi, filtra, interrompi e mocka.