About Jitterflow
Quick answer: Jitterflow is webhook delivery infrastructure — it sits between your app and the webhooks it sends, spacing bursts across a computed jitter window so receivers don't rate-limit you, retrying failures with backoff, and routing anything that still fails to a hosted, replayable dead-letter queue.
What we build
Sending a lot of webhooks to the same destination at once looks like abuse to that receiver's own rate limiter, which responds with 429s. Jitterflow spreads those bursts out automatically, retries what fails with backoff, and — instead of letting an exhausted delivery vanish into a log line nobody reads — puts it in a dead-letter queue you can inspect and replay. See how Jitterflow works for the full technical picture.
Where we are today
Jitterflow is an early-stage product, built and operated in the open rather than behind a large support or compliance org. We don't yet hold formal third-party certifications like SOC 2 — the Security section of our legal page describes the actual measures in place (encryption at rest and in transit, SSRF-safe destination validation, per-destination isolation) rather than a compliance program. The full list of subprocessors we rely on — Stripe, Resend, Hetzner, Cloudflare — is on the same page.
Where to find us
Code and issues live on GitHub. For anything else, see Contact.