Find, reach, and inspect services locally.

Inspect HTTP, gRPC, WebSocket, SSE and Cap’n Proto. Find ports, trace a network path, or manage a download. A local Go app does the work; your browser provides the interface.

Local-first. No account.

Nightly: the latest workspace, local AI agents and easy updates.

Keep your place across tools, use command search, and connect your own agent through MCP or the JSON CLI. Nightly follows branch builds; stable remains v0.6.1.

ProtoPeek edge workbench with persistent side navigation and six task destinations
Actual edge build · 7 September 2026. Stable installs remain on v0.6.1.

Start with a question.

Pick the thing you are trying to understand. ProtoPeek keeps the evidence together.

Can I reach this service?

Call gRPC or HTTP and see exactly what came back.

Choose gRPC or HTTP

Why is this request slow?

Check DNS, routes, hops, and timing in one path.

Trace the path

What can I verify about this public website?

See DNS, TLS, and response-header evidence when you ask.

See website evidence

What is happening on this device?

Network workspace: listeners, connections, IPs, and bounded speed evidence.

Preview This Device

Can I manage this download locally?

Queue, pause, resume, and verify HTTP(S) transfers.

Meet Downloader

Follow one connected map through every feature, its evidence, and its limits.

Explore all features

One workbench. Real evidence.

Requests, routes, listeners, certificates, downloads, and timing stay together.

ProtoPeek edge Home workspace at 390 by 844 with responsive task cards and a navigation menu
Edge · responsive Home
ProtoPeek edge desktop workspace with six persistent destinations, grouped tools and local task shortcuts
Edge · persistent desktop navigation

Ready when you are.

Install once, then run pp to open the local workbench in your browser.

Other install optionsDownload a release archive
Operating system

Installs ProtoPeek. Homebrew supplies aria2; Linux release archives use installed aria2.

Your machine stays yours.

ProtoPeek opens locally. External checks run only when you ask. The interface is served by the app on your machine; there is no hosted account to sign into.

Why a Browser User Interface?
  • No account
  • No ProtoPeek cloud sync
  • Clear consent before external checks