Queuey — The async queue for your API: webhooks, jobs and events

Let your API be an API. Queuey takes care of delivery. Webhooks and events land in Queuey first. Queuey acknowledges them as soon as they are durably stored, then delivers them to your API at the pace you set — with retries, ordering, replay and recovery built in. No Redis, SQS or RabbitMQ to operate. No retry logic or DLQ infrastructure to build.

Your webhook has seconds; your processing doesn't. Shopify expects an answer within 5 seconds, GitHub 10 and Sanity 30, and Stripe asks for one quickly, before any complex logic. All four tell you to put a queue in front of your handler. Queuey is that queue: accept first, deliver when ready.

A queue stores the message. Queuey operates the delivery. When your API answers 429, the queue waits as long as Retry-After says, then resumes on its own. A 502, 503 or 504 opens the circuit breaker, and one probe at a time checks whether the API is back. A timeout is not retried blindly, because the request may already have been processed: the queue holds until you confirm once that the endpoint is idempotent. A 401 or 403 stops retries and marks the destination as requiring action. A 400 or 422 goes to the dead-letter queue, ready to replay once the cause is fixed.

Set up with your coding agent: one prompt to read the repository, configure the queue and receiver address, connect the application and verify delivery. Setup is complete when an event reaches the intended receiver; if verification is blocked, the agent reports what is missing.

Get email or Slack alerts when issues match your notification settings. Connect your agent through MCP to investigate delivery evidence and record its findings. Where agent alerts are enabled, a signed webhook or Claude Code routine can start the investigation. Verify the fix before resuming held events; required production approvals stay with you.

Built for events that matter: a 202 only once the event is stored, HMAC verification at ingress and HMAC-signed deliveries, OAuth2 client credentials to authenticate with your API, a rate limit per destination, FIFO or best-effort ordering, deduplication on the producer's Idempotency-Key, evidence for every attempt, an audit trail, a GDPR Article 28 DPA and single-region hosting in Azure Norway East.

Webhooks are the way in, not the limit: the same delivery works from your app to a partner API, from a device to a cloud API with Queuey Edge, and from an ERP to an external system.