Webhook tools compared, categories first
Most comparison pages start with a feature table and a winner already chosen. The truth about webhook tooling is duller: request bins, inspectors, gateways and tunnels solve different problems, and the right choice depends on which problem you actually have.
The four categories
A request bin (webhook.site, RequestBin descendants) gives you a URL that records whatever hits it. Perfect for a five-minute check on any HTTP traffic; it knows nothing about your platform.
An inspector is a bin that understands its domain. CommerceHook is one: it registers the webhooks with your store, labels every event, verifies signatures, links deliveries back to the order or product, and replays them at your handler. It sits out of your delivery path, which is what keeps it simple and cheap.
A gateway (Hookdeck, EventDock, Svix Ingest) sits in the delivery path between the platform and your handler, and takes responsibility for delivery: queues, retries with backoff, transformations, alerting. That responsibility is why gateways cost what they cost.
A tunnel (ngrok and friends) exposes your local machine to the internet so a webhook can reach it. Nothing is captured; the tunnel is the product.
One category note in passing: Svix, often named alongside these, is mainly outbound webhook infrastructure, for products that send webhooks to their own customers. Different market; their receiving product (Svix Ingest) is an enterprise-priced gateway. We have not written a page against them because most readers weighing CommerceHook are not weighing Svix.
The comparisons
CommerceHook vs doing nothing
Platform dashboards, the Stripe CLI, and when you do not need a webhook tool at all. The page nobody else writes.
CommerceHook vs webhook.site
The generic request bin everyone has used. Where it is enough, and where a commerce-native inspector earns its keep.
CommerceHook vs ngrok and tunnels
Tunnels expose your laptop; an inspector captures the delivery. Different jobs that overlap on exactly one workflow.
CommerceHook vs Hookdeck
A serious event gateway that sits in your delivery path. If you need guaranteed delivery, use them. If you need to see and debug, read on.
CommerceHook vs EventDock
A younger gateway with an inspector attached. The category difference matters more than the feature table.
Or skip the reading: point a webhook at a free endpoint and see whether it earns its place.