대시보드

실패한 요청을 찾고 수정 사항을 테스트하세요.

모든 기기가 하나의 라이브 테이블에. 요청을 멈추고, 가짜 응답을 돌려주고, 재생하세요.

A three-pane dashboard: device rail, live request feed with status codes and detail pane. One row is lifted out on a paused breakpoint badge being edited, another returns a mocked 500, and two pinned rows connect to a side-by-side diff card whose changed lines carry red minus and green plus markers. POST GET 200 paused GET 200 GET MOCK 500 PUT 201 { } - +

트래픽 작업대

Find it. Fix it.

중요한 요청까지 필터링한 다음, 바꾸거나 재생하세요.

라이브 소방호스

모든 요청이 도착하는 순간 정렬 가능한 테이블로 흘러듭니다. 새로고침 버튼은 없습니다.

무엇이든 모킹

일치하는 요청에 원하는 상태·헤더·본문으로 응답하세요 — 또는 떨어뜨리세요.

와이어를 스크립팅

JS 훅이 헤더와 본문을 실시간으로 재작성합니다. dry-run 테스터 덕분에 고장 난 스크립트가 캡처를 중단시키는 일은 없습니다.

브레이크포인트

일치하는 트래픽을 멈추고, 원시 HTTP를 수정하고, 계속하거나 다시 보내세요.

정상과 비정상을 디프

항목을 고정하고 원시 요청과 응답을 나란히 비교하세요.

내보내고, 예약하고, 디코딩

HAR 내보내기, 스냅샷 예약, protobuf와 gRPC 디코딩까지.

How it works

Device to dashboard, one hop

No upload step and no poll loop — capture writes a row, Realtime fans it out, and control flows back down the same wire.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

The surface

More than a feed

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
지속 WebSocket을 통한 라이브 푸시 — 항목은 커밋되는 순간 나타나며, 폴링 타이머에 의존하지 않습니다
지속 처리량
매일 205,000건의 캡처된 요청 — 약 8.81 GiB의 트래픽 — 이 라이브 피드를 통과합니다 (프로덕션 플릿, 2026년 7월 측정)
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)

FAQ

Dashboard questions, answered

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 live

연결된 모든 기기에서 요청이 흘러드는 것을 보세요 — 그리고 좁히고, 필터링하고, 멈추고, 모킹하세요.

Ask your mate