// glossary

Request inspector

A request inspector captures incoming HTTP requests in a UI so you can see body, headers, status, and latency in real time.

Tunnel services with request inspectors (lrok, ngrok) capture every request that passes through the tunnel and surface it in a dashboard. You can see exactly what Stripe sent, click to view full body, replay it against your local handler.

Without an inspector, you'd be relying on print debugging in your handler — which doesn't help if the request never reaches your handler (signature failed, body parse error before logging, etc.).

lrok captures the last 100 requests per tunnel in memory. They evict on tunnel close. Never persisted to disk — keeps the privacy footprint small for webhook bodies that often contain PII.

// shipping?

lrok gives your localhost a public HTTPS URL with a reserved subdomain on the free plan. Useful when this term comes up in a real integration:

$ curl -fsSL https://lrok.io/install.sh | sh
$ lrok http 3000

← all glossary terms