self-hosted job queue · http message queue
A self-hosted job queue that pushes — never polls
Most job queues make you run workers that pull from Redis or SQS. betterMQ is different: you enqueue over HTTP, it stores the job durably, and pushes a signed webhook to your endpoint.
HTTP job queue vs traditional queues
Serverless and small teams often want a background job queue over HTTP — fire a POST, forget about it, and let your existing API handle the work via webhook.
What you can enqueue
Named queues
Register a queue → fixed destination URL.
One-off publish
Deliver to any URL without creating a queue.
Fan-out groups
One publish → many webhooks, each with its own limits.
Batch ingest
Up to 100 messages per request when self-hosted.
Why self-host your message queue
- · Job payloads never leave your network
- · No per-message meter at high volume
- · Single Rust binary — no Redis cluster to babysit
- · OpenAPI docs, embedded panel, Prometheus metrics