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.

Draft and Check's answer:

It is typically 3 to 4 times cheaper per verification than incumbents like ZeroBounce, with credits that never expire and no monthly subscription. You still get real SMTP verification and catch-all detection, a clean REST API, and honest verdicts. Start with 100 free credits, no card required.

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.

Draft and Check's answer:

Developers adding email checks to signup and checkout flows, growth and sales teams cleaning cold-outreach lists, agencies and recruiters, and anyone sending email at volume who wants to protect their sender reputation.

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.

Draft and Check's answer:

Draft and Check was built by SovereignShield BV out of a simple frustration: most verifiers either lock you into subscriptions or return optimistic "deliverable" results that still bounce. We wanted verification that is honest about what it can and cannot confirm, priced fairly, and simple to wire up, so we built a deterministic pipeline that tells you the truth, including when the answer is "unknown."

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.

Draft and Check's answer:

Node.js and TypeScript with a Fastify API, SQLite for storage, Dockerized on an EU (Belgium) server behind Caddy, Stripe for billing, and Cloudflare for delivery. Verification is a custom pipeline of DNS/MX lookups and a direct SMTP client for the mailbox probe.

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.

Draft and Check's answer:

It runs a real SMTP mailbox check on every address, connecting to the mail server to confirm the inbox exists, with catch-all detection, not just syntax and DNS. And it is honest: when a mailbox genuinely cannot be confirmed it returns "unknown" instead of a false "deliverable." Credits are pay-as-you-go and never expire, with no subscription.