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.

ThreadRecap's answer:

Generic AI assistants can summarize a chat you paste, but they hit token limits on long threads, ignore voice notes, and give you a different structure every time you ask. Chat statistics tools give you word clouds and message counts, which is not what you need when you are trying to prove what was agreed. ThreadRecap is built for the specific job of turning a full export into a structured, repeatable record. It works in six languages, needs no integration or account for the other participants, and you pay per analysis instead of subscribing.

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.

ThreadRecap's answer:

Solo professionals and individuals who need to establish what was actually agreed in a conversation. In practice: real estate agents, recruiters and HR, small business owners, freelancers dealing with clients, and people documenting a personal dispute over a rental, a partnership or a family matter. A second, lighter audience uses it to catch up on long work or family group chats. Buyers are spread across more than 20 countries, led by the UK, the US, Italy and Switzerland.

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.

ThreadRecap's answer:

It started as a personal tool. I kept receiving long voice notes and endless work threads, and wanted the main points without listening to everything again. I built the first version over a weekend and published it as a proof of concept, mostly to see whether anyone else cared. People did, but not for the reason I expected. Instead of catching up on chats, they were using it to document disputes, prove agreements and produce a record of what was said. That reframed the whole product, and the roadmap has followed the users ever since.

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.

ThreadRecap's answer:

Next.js and React with TypeScript, Tailwind CSS, Node.js on the backend, deployed on Vercel. Voice note transcription uses OpenAI Whisper, analysis runs on large language models, and payments go through Stripe.

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.

ThreadRecap's answer:

Most summarizers expect you to paste text. ThreadRecap takes the raw WhatsApp export, the .zip with thousands of messages and voice notes, and turns it into a timestamped record you can hand to someone else. Voice messages are transcribed and merged into the same timeline as the text, so a commitment made in a 4 minute audio at 11pm sits in date order next to everything else. The output is not a paragraph of prose. It is decisions, agreements, deadlines, responsibilities and quoted messages, in chronological order.