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.

Settilo's answer:

Settilo is built exclusively for buyers, with no listing revenue, no agent relationships, and no incentive to obscure unfavorable data. Competitors l target institutional and B2B customers at $125–400/month. Settilo makes the same depth of neighborhood intelligence accessible to individual buyers at a consumer price point, with a comparison interface built around the actual decision: which neighborhood fits my priorities.

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.

Settilo's answer:

Analysis-first home buyers — people relocating to an unfamiliar city, first-time buyers doing serious research, and anyone who wants to understand a neighborhood before committing to it. They're data-literate, often comparing 3–5 areas simultaneously, and frustrated by how scattered the relevant information is across government databases.

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.

Settilo's answer:

Settilo was built by a team that went through the home-buying process and noticed that every useful data point required a different government website, inconsistent formats, and hours of manual work. The property data was easy to find. The neighborhood data — the part that determines long-term quality of life — wasn't. Settilo launched in March 2026 to fix that.

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.

Settilo's answer:

Next.js, PostgreSQL with PostGIS for geospatial queries, US Census Bureau data (ACS), FBI UCR crime data, GreatSchools API, and Mapbox for geographic visualization.

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.

Settilo's answer:

Settilo analyzes the neighborhood, not the listing. While most real estate platforms focus on property details, Settilo surfaces the data that surrounds it — crime trends over time, school quality at the attendance-zone level, local economic trajectory, and housing value trends — pulled from authoritative public sources and presented in one place.