
HookReplay.dev
hookVM
Webhook.site
ngrok
Hooklistener
Webhooks.cc
RequestBin
Webhook Relay
GitPrime
Waydev
LinearB
Haystack Analytics
CodeClimate
Swarmia
OKAY HQ
SonarQube
HookReplay.dev
GitPrimeGitPrime is recommended for engineering managers, team leads, and project managers who are looking for data-driven insights to understand and enhance the productivity of their software development teams. It's particularly useful for medium to large teams where it's critical to evaluate performance metrics objectively and address inefficiencies proactively.
No HookReplay.dev videos yet. You could help us improve this page by suggesting one.
HookReplay.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.
Waydev - Waydev analyzes your codebase from Github, Gitlab, Azure DevOps & Bitbucket to help you bring out the best in your engineers work.
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.
LinearB - LinearB delivers software leaders the insights they need to make their engineering teams better through a real-time SaaS platform. Visibility into key metrics paired with automated improvement actions enables software leaders to deliver more.
ngrok - ngrok enables secure introspectable tunnels to localhost webhook development tool and debugging tool.
Haystack Analytics - Software Delivery Analytics Tool for Engineering Teams. Deliver Software Faster, Better, and more Predictably.