Finde die fehlerhafte Anfrage. Teste die Korrektur.
Jedes Gerät in einer Live-Tabelle. Halte eine Anfrage an, sende eine gefälschte Antwort zurück oder wiederhole sie.
Find it.
Filtere bis zur Anfrage, die zählt — dann ändere oder wiederhole sie.
Der Live-Firehose
Jede Anfrage streamt in eine sortierbare Tabelle, sobald sie eintrifft. Kein Aktualisieren-Button.
Alles mocken
Beantworte eine passende Anfrage mit eigenem Status, Headern und Body — oder verwirf sie.
Die Leitung skripten
JS-Hooks schreiben Header und Bodies live um — mit Dry-Run-Tester, damit ein kaputtes Skript nie die Erfassung lahmlegt.
Haltepunkte
Halte passenden Traffic an, bearbeite das rohe HTTP, lass weiterlaufen oder sende erneut.
Funktionierend gegen kaputt diffen
Pinne Einträge an und vergleiche rohe Anfragen und Antworten Seite an Seite.
Exportieren, planen, dekodieren
Exportiere HAR, plane Snapshots, dekodiere protobuf und 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
- Live-Push über einen persistenten WebSocket — ein Eintrag erscheint in dem Moment, in dem er gespeichert ist, nie über einen Polling-Timer
- Dauerlast
- 205,000 erfasste Anfragen — rund 8.81 GiB Traffic — fließen jeden Tag durch den Live-Feed (Produktionsflotte, gemessen im Juli 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
Sieh zu, wie Anfragen von jedem verbundenen Gerät hereinströmen — dann eingrenzen, filtern, anhalten und mocken.