HookReplay.dev
hookVM
Webhook.site
ngrok
Hooklistener
Webhooks.cc
RequestBin
Webhook Relay
Getwebstack
MarsX
Getwebstack is for development teams that implement a lot of different projects. It can help outsourcing companies, accelerators, freelancers, or dev studios to develop fast. It is also for individuals that want to test a technology or an idea for a startup with a quick setup and deployment. Getwebstack provides a complete solution that covers all the technical aspects of a web app. It has an affordable monthly subscription instead of an expensive one-time payment.
HookReplay.dev GetwebstackHookReplay.dev's answer
Still early โ just launched. Currently used by indie developers and small teams debugging Stripe and Shopify integrations. No big logos yet. Focused on building a great product first.
HookReplay.dev's answer
With ngrok, every code change means triggering another webhook. Add a log? Trigger again. Set a breakpoint? Too late, it timed out. Trigger again. With HookReplay, you trigger once. Then replay 100 times while you debug. Same webhook. Same payload. Unlimited attempts to get your code right. That's not a small difference โ it's hours saved per debugging session.
HookReplay.dev's answer
Developers who integrate third-party webhooks Stripe, Shopify, GitHub, Twilio, Paddle, etc. Basically anyone who's ever clicked "Send test webhook" more times than they'd like to admit.
HookReplay.dev's answer
11pm on a Sunday. A customer's Stripe payment went through, but their subscription wasn't created. I needed to debug the webhook handler. Set up ngrok. Triggered a test payment. Added a log statement. Triggered again. Set a breakpoint โ webhook timed out before I could step through. Triggered again. Changed the URL in Stripe because ngrok restarted. Triggered again. Three hours later, I found a typo in my event type check. I remember thinking: I just re-triggered the same webhook 40+ times. Why can't I just capture it once and replay it until I find the bug? That's the moment HookReplay was born. The tool I wished existed that night.
HookReplay.dev's answer
ASP.NET Core for the backend, PostgreSQL for storage, WebSockets for real-time forwarding to the CLI. The CLI is built in .NET and distributed via npm โ runs on macOS, Windows, and Linux. Nothing fancy. Boring tech that works.
HookReplay.dev's answer
Three things most webhook tools don't do: 1- Replay the same webhook unlimited times 2- Edit payloads before replaying (test edge cases) 3- Keep a full history of every webhook received HookReplay does all three, plus real-time forwarding like ngrok.
hookVM - Receive, deliver, and debug webhooks with reliability, observability, and developer-first tooling.
MarsX - MarsX leverages the power of AI to help users build mobile and web applications using code and no-code technology. MarsX is highly accessible, allowing even non-developers and those with zero building and coding experience to create their own mobile
Webhook.site - Instantly generate a free, unique URL and email address to test, inspect, and automate (with a visual workflow editor and scripts) incoming HTTP requests and emails.
ngrok - ngrok enables secure introspectable tunnels to localhost webhook development tool and debugging tool.
Hooklistener - The developer-friendly webhook inspector with real-time team collaboration, request replay, and permanent history.
Webhooks.cc - Capture and inspect webhooks in real time. Send signed provider test webhooks, forward to localhost with the CLI, test in CI with the SDK, and debug faster with MCP.
