Open source · Hosted for indie SaaS

Catch failed webhooks & jobs. Replay them.

Requeue is a dead-letter inbox for webhooks, crons, and workers. When something dies at 2am, it lands here — inspect the payload, fix the bug, one-click replay.

Get early access View the core on GitHub

Self-host the OSS inbox or call the hosted API at api.getrequeue.com

Try the API

curl https://api.getrequeue.com/health

The problem

Failures go quiet. Customers don't.

Retries exhaust. Logs rotate. The Stripe event that 500'd is gone by the time someone mentions their invoice never updated.

Webhooks vanish after three retries

Stripe, Clerk, Resend — they try a few times, then stop. You find out from a support thread, not a dashboard.

Crons fail and leave no corpse

A nightly job times out. The next run overwrites the log. Context is gone before you open the laptop.

Workers retry into /dev/null

Queue libraries retry, then drop. The payload that would let you replay lives nowhere you can click.

You are not a platform team

Indie SaaS doesn't have an on-call rotation or a dead-letter service. You need an inbox, not another pager.

The solution

Catch. Inspect. Replay.

One inbox for every failed delivery. Open source if you want to self-host. Hosted if you want Maya to keep the lights on.

Catch

Failed webhooks, cron runs, and worker jobs land in one dead-letter inbox. Nothing silent. Nothing lost after the last retry.

Inspect

Headers, payload, stack, attempt count — the full corpse, not a one-line CloudWatch snippet. See why it died before you touch prod.

Replay

One click to re-deliver the same payload through your new code. Or edit the body and retry. That's the whole product.

How it works

From failure to replay in four steps.

Point webhooks at Requeue, wrap jobs with the SDK, or drop the OSS inbox next to your stack.

Connect

Install the JS SDK, forward a webhook URL, or run the open-source inbox beside your app.

Fail as usual

When a delivery 500s, times out, or a worker gives up, Requeue keeps the event instead of dropping it.

Read the inbox

Open the dead letter, read the body, see the status. Fix the handler. No log archaeology required.

Replay

Re-send with one click — locally against the OSS build, or against the hosted API at api.getrequeue.com.

Who it's for

Indie SaaS, not enterprise ops.

Built for people who ship the product and also get paged by it.

Solo founders

You wired Stripe last Tuesday. You don't have a reliability squad. You need failures to wait in an inbox until morning.

Small product teams

Two to five people, a pile of webhooks, and no budget for a full incident platform. Self-host or use the hosted API.

Anyone grepping logs at midnight

If you've reconstructed a missing Clerk webhook from memory, Requeue is for you.

Waitlist

Get early access to the inbox.

The core is public, and the hosted API is live at api.getrequeue.com. This form only opens your email client — no paid form SaaS, no tracking pixels.

Already have a key? Open the inbox and connect to api.getrequeue.com.

Maya Chen is building Requeue in the open at github.com/requeue-hq/requeue and the JS SDK.