Relay Webhooks Locally.
Keep Provider Acknowledgments Fast.
Catchhook captures and responds to the provider first, then the CLI delivers the same request to your local handler. Debug locally and recover retained requests after a monitored relay reconnects without putting localhost in the provider request path.
Faster Feedback, Fewer Deploys
Fast-ack local relay lets you test webhook behavior where you're writing code while Catchhook remains responsible for the provider response.
One Command to Connect
Run the tunnel CLI and your local port is reachable by Catchhook in seconds. No config files needed.
Test Locally, Ship Confidently
Validate parsing, authentication, side effects, and logging on your own machine before anything goes live.
Real Provider Traffic, Safely
Receive actual webhook deliveries from Stripe, GitHub, Shopify, and others -- without exposing your machine publicly.
How Fast-Ack Relay Works
Two visible outcomes: the response Catchhook returned to the provider, then the local delivery result reported by the CLI.
Open a relay session
Run the Catchhook CLI to create a secure connection from your endpoint to your local port.
Point your provider to Catchhook
Catchhook captures the request and returns its configured response without waiting on localhost.
Debug the local delivery
The CLI delivers the captured request to your handler and reports its status and timing separately.
Reconnect with context
If traffic arrives while a monitored relay is disconnected, review the delivery gap and deliberately recover retained requests when you reconnect.
Common Questions
Does my local machine stay private?
Yes. Traffic is routed through CatchHook's tunnel infrastructure while your machine stays behind your firewall.
Can I test signature verification locally?
Yes. Tunnel traffic preserves all original headers and request data, so signature logic works as expected.
Does the provider receive my local response?
No. Catchhook returns its configured response before local delivery completes. The CLI reports local status and timing as separate evidence.
What happens when my tunnel disconnects?
CatchHook keeps capturing incoming webhooks. For monitored permanent endpoints, traffic that misses localhost creates one delivery gap with a notification and a deliberate recovery path when the CLI reconnects.
Can I combine tunneling with replay?
Yes. Save an eligible local response as a tunnel Replay Case to repeat it on the same named CLI client and check its response status. CatchHook does not make a server-side request to localhost.
Relay Real Webhooks to Local Code
Keep development fast with local testing that does not delay the provider acknowledgment.