Meet WireRiftA small binary. A direct connection. Your infrastructure.InstallationNative binaries for your machine. No runtime to manage.Run your own serverThe public edge belongs to you.HTTP & WebSocket tunnelsShare web apps, receive webhooks, and keep WebSockets connected.TCP tunnelsA path for the protocols beyond HTTP.Security & accessLayer access controls around what you share.Traffic inspectorSee the request. Understand the response. Try it again.Under the wireOne connection. Many independent streams.Dashboard APIYour tunnels and traffic, programmatically.ConfigurationKeep your connections together in a readable config file.Docker deploymentGive your public edge a reproducible home.Local HTTPS developmentA trusted development edge, without a public domain.TroubleshootingGet back to a working connection.
Documentation, without the detour.ESC to close
Browse documentation
DOCUMENTATION / OPERATE

Traffic inspector

See the request. Understand the response. Try it again.

Capture traffic

Start an HTTP tunnel with --inspect, then open the dashboard on localhost:4040 and authenticate. Select the Inspector tab to see captured requests.

terminal
wirerift http 3000 --inspect --server tunnel.example.com:4443 --token YOUR_TOKEN

Look inside

Expand an entry to view request and response headers and syntax-highlighted JSON. Each entry includes its method, path, response status, duration and client IP. Inspection may capture sensitive payloads; keep dashboard access restricted.

Replay and export

Replay sends the captured request to your local service again. Use it to debug webhook handlers without recreating the upstream event. Copy a request as cURL when you need to reproduce it in your terminal. Replaying a request can repeat application side effects.

Use the capture API

Read captures with the authenticated API. Filter by tunnel when several services are running.

terminal
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "http://localhost:4040/api/requests?limit=50"