CommerceHook vs Hookdeck
Hookdeck is a proper piece of infrastructure. Put it between the platform and your handler and it queues deliveries, retries them with backoff, transforms them, alerts on failures, and holds the whole thing to an SLA on the higher tiers. If that is what you need, stop reading and go use it; nothing at $6/month replaces it.
In the path versus out of it
The gateway premium buys responsibility. Once Hookdeck is in your delivery path, its uptime is your uptime, its queue is your buffer, and its retries are the reason a blip in your handler does not lose an order. That is production plumbing, priced like production plumbing: the tier with 30-day retention starts at $499 a month.
CommerceHook takes the opposite bet. It never sits between the platform and production. You register webhooks to a CommerceHook endpoint to see them: while building an integration, while debugging one, while proving what a platform did or did not send. Being out of the path is what makes 90-day retention at $6 possible, and it is also why we cannot retry a delivery into your production handler on your behalf. Replay exists, but you press the button.
| Hookdeck | CommerceHook | |
|---|---|---|
| Category | Event gateway, in the delivery path | Inspector, out of the delivery path |
| Free tier | 10,000 events/month, 3-day retention, 1 user | 1 endpoint, 24-hour retention |
| Paid entry | Team from $39/month, 7-day retention | Pro $6/month, 90-day retention |
| 30-day retention costs | Growth, from $499/month | Included at $6/month (90 days) |
| Overage | From $3.00 per 100,000 events | No metered billing (rate-limited per endpoint) |
| Queues, retries, transformations | Yes, the core product | No, deliberately |
| Registers webhooks with your store | No (you point the platform at their URL) | BigCommerce, WooCommerce, Square, Shopify, Stripe |
| Commerce context (store links, platform signatures) | Generic | First-class |
| CLI and MCP server | Yes | Yes |
Prices and limits checked 26 August 2026 from public pricing pages. If a number here has rotted, tell us and we will fix it.
Choose plainly
- Use Hookdeck when webhooks are production-critical and you want delivery guaranteed by somebody else's queue: retries, alerting, SLAs, volume.
- Use CommerceHook when the job is building and debugging store integrations: register from a panel, read every payload, check the signature, jump to the order, replay at your dev handler.
- Using both is not silly: a gateway in production and an inspector endpoint beside it while you develop. They do not compete for the same webhook.
If your problem is seeing rather than delivering, this takes a minute to try.
Also compared: webhook.site , EventDock , ngrok and the platform tools .