ダッシュボード

失敗したリクエストを見つけ、修正を検証。

すべてのデバイスを 1 つのライブテーブルに。リクエストを止める、偽のレスポンスを返す、リプレイする。

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