Skip to main content
Comparison

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 and 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.

Trusted by teams at

Eudonet GEODIS WoodWing Optery Alteos ActiveAnts Apizee

The Short Answer

Hook0 and Requeue solve adjacent problems from opposite directions. Requeue is an inbound dead-letter inbox. You point a Stripe or Clerk webhook at its relay URL, or post failed cron and worker jobs to it, and it keeps whatever your app failed to process so you can inspect it and replay it. Hook0 is outbound webhooks-as-a-service. It sends webhooks to your own users and owns that delivery, with every attempt logged, up to 24 free retries within 8 days, HMAC signatures, and replay from the dashboard or API. Choose Requeue to catch inbound failures on a small team; choose Hook0 to deliver webhooks to your customers, EU-hosted and open source. Hook0 does not offer a production inbound dead-letter today, and Requeue's own FAQ says it does not replace outbound webhooks-as-a-service.

What Each One Does

Key Differences

Catching Inbound vs Sending Outbound

Requeue sits in front of traffic coming in. Its relay URL takes a provider's webhook, forwards the raw body and signature headers to your app with a 10-second timeout, and stores the request if your app errors or times out. 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.

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 with its status code and response, Hook0 retries up to 24 times within 8 days by default, and when the last retry fails the attempt stays in failed so you can replay the event from the dashboard or the API. See what happens to a webhook after its last retry.

EU Residency and GDPR by Default

Hook0 is published by a French company with no US parent, subsidiary or establishment, and its managed cloud runs in the EU by default with HMAC signatures and TLS. Requeue's core runs on Cloudflare Workers and Cloudflare D1, and its public material does not state where the hosted instance stores data. If you need EU residency with Requeue, you deploy the Worker on your own Cloudflare account and choose the location there.

Open Source, Free Retries, Public Pricing

Hook0's server is open source under SSPL-1.0 (source-available, not OSI-approved) and its 11 client SDKs are MIT. Retries are free, HMAC signing is built in, there is no per-endpoint billing, and pricing is public with a free Developer plan. Requeue's core and JavaScript SDK are MIT, version 0.1.0 as of October 2026, and hosted keys come from a waitlist with no public pricing yet.

Side by Side

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
Inbound relay URL No (the CLI tunnel is for local development) Yes, forwards once to your app and keeps failures
Replay Per event, from the dashboard or API One click, payload edit per delivery, bulk replay up to 50 events
Per-attempt logs Yes, status code and response body Failed events with headers, payload and reason
Signatures HMAC-SHA256 on every request + TLS HMAC-SHA256 on replays when the endpoint has a secret
Automatic retries Up to 24 within 8 days (3 s to 10 h apart), free Queued replays: 1, 2, 4, 8, 16 min, then marked failed
Subscriber portal Embeddable Not applicable (not an outbound sender)
Hosting Managed EU cloud (Clever Cloud, France) + self-host Cloudflare Workers + D1; hosted region not stated
Source Server SSPL-1.0, 11 SDKs MIT Core and JS SDK MIT (v0.1.0)
Pricing Public, free Developer plan Not stated (hosted keys by waitlist)
Typical user Teams emitting webhooks to their customers Indie and small teams (2 to 5)

Where Requeue Fits Better

  • Stripe, Clerk or Resend send you webhooks and you want a copy of every request your app failed to process, ready to replay once the bug is fixed. That is Requeue's relay URL, and Hook0 does not do it.
  • Your nightly crons and queue workers drop payloads after their last retry, and you want them all in one inbox with the error reason attached.
  • You are a solo founder or a team of two to five, already on Cloudflare, and you are fine running a 0.1.0 MIT Worker yourself.

Need an inbound gateway with its own retry pipeline instead of an inbox? See Hook0 vs Hookdeck.

FAQ

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, that is Requeue's focus.

Does Requeue send webhooks to my customers?

No. Requeue's FAQ says it does not transform or fan out events and does not replace outbound webhooks-as-a-service. Its relay forwards one provider's webhook to one target URL in your app. Sending events to many customer endpoints, with signatures, retries and a portal where customers manage their subscriptions, is what Hook0 does.

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 and that tunnel is meant for local development only.

Can I replay failed webhooks with Hook0?

Yes, on the sending side. Every delivery attempt is logged with its status code and response. Hook0 retries a failed delivery up to 24 times within 8 days by default, and once retries are exhausted the last attempt stays in failed status. You then replay the event from the dashboard or with POST /events/{event_id}/replay, which sends it again to every matching subscription.

Where does Requeue run?

According to its README, the Requeue core is a Cloudflare Worker that stores events in Cloudflare D1, and the hosted API runs at api.getrequeue.com. Its public material does not state the hosted data region. Hook0 Cloud runs in the EU, hosted in France by default, and the Hook0 server can be self-hosted on Docker or Kubernetes.

Is Requeue open source?

Yes. The Requeue core API and its JavaScript SDK are published under the MIT licence on GitHub, at version 0.1.0 as of October 2026. 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, 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. Some teams need both, one for each side of the pipe.

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.

Methodology

How we compared, and our sources

This page compares the role, relay, replay, retries, signatures, hosting, licence and pricing of Hook0 and Requeue. Requeue facts come from its public home page, the README and FAQ of its GitHub repository, and its JavaScript SDK repository, all read on the date shown. Hook0 facts come from the Hook0 documentation and pricing page.

Sources

This is an independent comparison. Hook0 is not affiliated with, endorsed by, or sponsored by Requeue. Product names and trademarks belong to their respective owners, and every competitor figure links to a public source with the date we checked it.
Last reviewed 2026-10-22.

You have better things to build

Stop building webhook infrastructure. Start shipping features. Get started in minutes.

No credit card required
Setup in 5 minutes
Cancel anytime