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.

RelayFox

Capture webhooks & replay to localhost — no tunnel needed

Capture webhooks & replay to localhost — no tunnel needed