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.

Handler's answer:

Handler is currently early, so we are not publishing customer names yet. The product is built for app founders, consumer app teams, growth marketers, and agencies working on TikTok-based app growth.

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.

Handler's answer:

Handler is focused on TikTok research for app growth, not generic social media management. It helps marketers move faster from “what should we post?” to clear creative direction based on real winning TikToks.

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.

Handler's answer:

Handler is made for app founders, growth marketers, mobile app teams, indie app builders, and agencies that use TikTok to grow consumer apps.

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.

Handler's answer:

Handler was created because app teams spend too much time manually scrolling TikTok trying to understand what content works. We built it to make TikTok research faster, clearer, and more repeatable for app marketers.

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.

Handler's answer:

Handler uses AI analysis, TikTok content research, video metadata extraction, creative pattern detection, and a web-based dashboard to help app marketers find and understand winning TikToks.

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.

Handler's answer:

Handler is built specifically for app marketers who want to find what is already working on TikTok. Instead of guessing content ideas, Handler helps teams discover outlier TikToks, understand winning patterns, and decide what to test next.