Hook0 vs Requeue Opposite Directions, Same Problem
Requeue catches the webhooks you receive and the cron or worker jobs that fail, then replays them into your app. Hook0 does the reverse: it sends webhooks to your users and owns the delivery, with per-attempt logs, free retries, HMAC signing and replay. This page lays out which direction each one is built for, so you can tell at a glance which problem you actually have.
The Short Answer
Hook0 and Requeue solve adjacent problems from opposite directions. Requeue is an inbound dead-letter inbox: it catches the webhooks you receive from providers like Stripe or Clerk, plus failed cron and worker jobs, and lets you replay them to your app. Hook0 is outbound webhooks-as-a-service: it sends webhooks to your own users and owns that delivery, with every attempt logged, payloads you can inspect, configurable free retries, HMAC signatures, and replay from the dashboard or API. Choose Requeue to catch and replay inbound failures on a small team; choose Hook0 to deliver webhooks to your customers at scale, EU-hosted and open source. Hook0 does not offer a production inbound dead-letter today.
Key Differences
Catching Inbound vs Sending Outbound
Requeue is a dead-letter inbox for traffic coming in: the webhooks you receive from third parties and the background jobs that fail. Hook0 is the sender. It publishes your events and delivers them to your subscribers, so the failure it manages is a delivery out that did not land. Same reliability problem, opposite ends of the pipe.
Catch, Inspect, Replay on the Sending Side
The catch / inspect / replay story Requeue tells for inbound, Hook0 already runs for outbound: every delivery attempt is logged, you can inspect payloads and responses, find out why a delivery failed, and replay events from the dashboard or API. Events and responses are persisted, so a debugging trail is there when you need it.
EU Residency and GDPR by Default
Hook0 is published by a French company with no US entity, outside the reach of the US Cloud Act, and its managed cloud runs in the EU by default with HMAC signatures and TLS. Requeue ships a self-hostable core and a hosted API on a waitlist; its public material does not state where the hosted data lives, so EU residency is on you to self-host.
Open Source, Free Retries, No Per-Endpoint Billing
Hook0's server is open source under SSPL-1.0 (source-available, not OSI-approved) and its 11 client SDKs are MIT. Retries are included for free, HMAC signing is built in, and there is no per-endpoint billing. Requeue also publishes a self-hostable open-source core. Both let you run the software yourself; the fit comes down to which direction of traffic you need to make reliable.
What Each One Handles
| Feature | Hook0 | Requeue |
|---|---|---|
| Primary role | Outbound webhooks-as-a-service | Inbound dead-letter inbox |
| Webhook direction | Outbound (you send to your users) | Inbound (you receive from third parties) |
| What it captures | Your failed deliveries to subscribers | Incoming webhooks + failed cron / worker jobs |
| Replay | From the dashboard or API | One-click replay with payload editing, bulk replay |
| Per-attempt logs | Yes, inspect payloads and responses | Captured failures held in the inbox |
| Signatures | HMAC-SHA256 + TLS | Not stated |
| Subscriber portal | Embeddable | Not applicable (not an outbound sender) |
| Retries | Configurable 2-phase, free | Manual and bulk replay |
| Hosting | Managed EU cloud (Clever Cloud FR) + self-host | Self-hostable core, hosted API on waitlist |
| Source | Server SSPL-1.0, 11 SDKs MIT | Open-source core (self-hostable) |
| Typical user | Teams emitting webhooks to their customers | Indie and small teams (2 to 5) |
Common Questions
Is Hook0 an alternative to Requeue?
They solve adjacent problems in opposite directions, so it depends on what you need. Requeue catches and replays the webhooks you receive, plus failed cron and worker jobs. Hook0 sends webhooks to your own users and manages that delivery. If you need to deliver webhooks to your customers reliably, Hook0 is the fit. If you need an inbox for failed inbound webhooks today, that is Requeue's focus.
Does Hook0 do inbound webhook dead-letter?
Not as a product today. Hook0 is outbound webhooks-as-a-service. The Hook0 CLI can receive webhooks on localhost through a built-in tunnel for local development, but that is a developer tool, not a production inbound dead-letter inbox.
Can I replay failed webhooks with Hook0?
Yes, on the sending side. Every delivery attempt is logged, you can inspect the payload and the response, find out why a delivery failed, and replay events from the dashboard or the API. Retries are configurable in two phases and free.
Is Requeue open source?
Requeue ships a self-hostable open-source core, with a hosted API on a waitlist. Hook0's server is open source under SSPL-1.0, which is source-available and not OSI-approved, and its 11 client SDKs are MIT. Both let you self-host; the difference is the direction of traffic each one handles.
Which should I choose, Hook0 or Requeue?
Pick by direction. Sending webhooks to your own customers at scale, with signatures, per-attempt logs, free retries and a subscriber portal: Hook0. Catching and replaying webhooks you receive from third parties, plus failed cron and worker jobs, on a small team: Requeue. They sit on adjacent sides of the same reliability problem.
Is Hook0 affiliated with Requeue?
No. Requeue is a trademark of its respective owner, and Hook0 is independent and not affiliated with or endorsed by Requeue. This page is a factual comparison for teams evaluating both tools.
You have better things to build
Stop building webhook infrastructure. Start shipping features. Get started in minutes.