dispatch.online·postgres-backed · HMAC-signed

ticks
don't
miss._

Durable HTTP scheduling, delays, and queues. Your POST /v1/schedules is written to Postgres before the API returns, then dispatched on time, retried on failure, and kept in a dead-letter queue if it never succeeds.

Postgres
persisted before we ack
nothing lost on a crash
Every 60s
dispatch tick
catches up if one runs late
SHA-256
signed webhooks
verify every delivery
Auto-retry
with backoff, then DLQ
failures kept, never dropped
/v1/primitives

Three ways
to fire.

Same durable log, same delivery guarantees — pick how your message gets into it.

schedules
cron · tz-aware · next ±60s
*/5 * * * *
delays
one-shot · after duration
+2h30m
queues
FIFO · rate-limited · DLQ
concurrency:5
the message lifecycle

Six states. Zero lost.

01PUBLISHED
POST hits /v1. Written to Postgres log before ack.
02PENDING
Awaiting next dispatch tick. Indexed by fire_at.
03CLAIMED
Dispatcher locked via SKIP LOCKED + 90s lease.
04IN_FLIGHT
HTTP request out. HMAC-signed. Awaiting response.
05DELIVERED
2xx received. Attempt logged. Terminal state.
06DEAD
Retries exhausted. Preserved in DLQ forever.
* self-heal: claimed → pending on lease expiry · failed → pending on retry with backoff

Pricing

No credit card required for the free tier
Free
$0
500/day
15-min interval
popular
Starter
$12/mo
100k/mo
1-min interval
Pro
$39/mo
1M/mo
1-min interval
Business
$149/mo
10M/mo
1-min interval