RelayFox
Capture webhooks & replay to localhost ā€” no tunnel needed
Start new thread
Roops

RelayFox - Capture webhooks & replay to localhost ā€” no tunnel needed

byā€¢
Testing webhooks means running ngrok ā€” a tunnel that dies when your laptop sleeps, dropping events you can't recover. RelayFox captures every webhook server-side. Paste your URL into Stripe, GitHub, or Shopify. Watch requests arrive live. Run `npx relayfox` to forward them to localhost. Replay any past event on demand. Free: 24-hour URLs, live inspector, CLI forwarding, share links. Pro ($9/mo): permanent URLs, 30-day history, team collaborators.

Add a comment

Replies

Best
Roops
Maker
šŸ“Œ
Hey PH! šŸ‘‹ I'm Roops, the solo dev behind RelayFox. The itch: every time I needed to test a Stripe webhook locally I'd boot ngrok, paste a new URL into the Stripe dashboard, and then pray my laptop didn't fall asleep and kill the tunnel before the event fired. It felt absurd ā€” webhooks are just HTTP POST requests. They should be storable. Replayable. Shareable with a teammate who isn't even at their desk yet. So I built RelayFox. The core insight: capture first, forward later. RelayFox receives and stores every webhook on the server, even when your local machine is off. When you're ready to work on your handler, run `npx relayfox` and the CLI streams events straight to your localhost ā€” no persistent tunnel required. What's free, forever: ā†’ Instant webhook URL (no account needed, 24h lifespan) ā†’ Live request inspector ā€” headers, body, query string ā†’ `npx relayfox` CLI forwarding to localhost ā†’ Read-only share links so teammates see exactly what you see Pro ($9/mo) adds permanent URLs, 30-day history, and team collaborators. Tested with Stripe, GitHub, Shopify, Slack, Twilio, Paddle, Clerk, and Linear out of the box ā€” but it works with any HTTP webhook. Would love to hear: what service's webhooks give you the most grief? And what would make RelayFox indispensable for your workflow? Happy to answer anything.