HookStead sits between your providers and your app: it records every webhook, forwards it with signatures and retries, and shows you exactly what happened at every attempt.
10,000 events a month free. No card needed. We email you at 80% and 100%; at the cap new webhooks get a 429, which providers retry, so upgrading lets them through.
The provider sends a webhook, HookStead verifies and stores it. The first delivery attempt fails with a 503, HookStead waits with backoff, and the second attempt succeeds.
POST /in/k3mP…Qz invoice.paid
Verified signatures for these providers, and any HTTP sender
Stripe
GitHub
Shopify
PayPal
Clerk
Supabase
Linear
Vercel
HubSpot
GitLab
01 / How it works
Three steps to webhooks you can trust
01
Point your provider at HookStead
Create a source and paste its URL into Stripe, GitHub, Shopify or your own app. Signatures are verified on arrival, so forgeries never get in.
02
Connect your endpoint
Add a destination. Every event is forwarded byte-for-byte, signed with your own secret, and retried with backoff until your endpoint says yes.
03
See, fix, replay
Every request and every attempt is on record. When something breaks, find it, fix your endpoint, and retry or replay any event within your plan's retention.
02 / When delivery fails
Every attempt on record, every failure recoverable
Click an event to see its attempts. The Shopify one ran out of tries: retry it.
Delivery history · sample data
invoice.paid → api.yourapp.com/webhooks
2 of 8 attempts
Attempt 1503312 ms · 14:02:11
{"error":"service unavailable"}
↻ retry in 14 s · backoff + jitter
Attempt 220091 ms · 14:02:25
{"received":true}
Retried automatically
5xx, 408, 429 and timeouts are retried with exponential backoff and jitter, honoring Retry-After. Other 4xx answers are final unless you turn on retrying them.
3
attempts · Free
8
attempts · Pro
15
attempts · Team
Then it ends one of two ways
Delivered: your endpoint answered 2xx.
Failed: out of attempts. You get an alert, and the event stays stored for your plan's retention.
Retry or replay?
Retry
Another attempt of the same delivery, same webhook-id. Free.
Replay
New deliveries of the stored event, with new webhook-ids, to the destinations you choose. Counts toward your monthly events.
03 / Features
Built for the day something breaks
Webhooks fail quietly. HookStead makes them loud, visible and recoverable.
Stored before we say 200
Every event is written to the database before your provider gets its 2xx, and deliveries are retried from there, not from memory, so a Redis outage or crashed worker doesn't drop them. Events are kept for your plan's retention period.
Signed deliveries
Standard Webhooks signatures on every attempt, secret rotation with an overlap window, and a stable webhook-id so you can dedupe.
Search everything
Find events by text, header, JSON path, source, time or delivery outcome. Open any delivery to see each attempt's request, response and timing.
Retry, replay, bulk retry
One click, or a thousand failed deliveries at once. Idempotency keys mean a double click never sends twice.
Alerts that don't spam
Failure rate, failures in a row, failed deliveries, quiet sources. One email when it breaks and one when it recovers, with a quiet period for flapping.
Private by default
Secrets and raw payloads are encrypted at rest, sensitive fields are redacted for display, and every view of an original request is audit-logged.
04 / Trust
Where your webhooks live, and who can see them
Webhooks carry customer data. Here is exactly how HookStead handles it.
Hosted in Germany
The application and database run on a server in Düsseldorf. The only sub-processors are Hostinger (server and email) and Stripe (payments).
Original payloads and signing secrets are encrypted with AES-256-GCM. The dashboard shows redacted copies; opening an original is for admins only, and every view is logged. All traffic uses HTTPS.
Verified on arrival
Turn on signature verification for a source and forged requests are rejected before they're stored, so they never reach your app. Every delivery to you is signed with Standard Webhooks.
Events are deleted automatically after your plan's retention (3, 14, 30 days). Deleting a workspace deletes its webhook data right away.
GDPR paperwork included
A data processing agreement under Art. 28 GDPR is part of the terms, so there is nothing to negotiate or sign separately. Privacy policy in English and German.
Your endpoint checks one signature, in any language, with any Standard Webhooks library or ten lines of code. Example receivers for Node, Python and Go are tested against real deliveries.
HookStead keeps the event and retries with exponential backoff and jitter, honoring Retry-After, up to your destination's attempt limit. Then the delivery is marked failed, an alert can email you, and you retry it once you're back.
Do I still need to verify the provider's signature?
No: HookStead verifies it on arrival and rejects anything forged. Verify HookStead's own webhook-signature instead. It's fresh on every attempt, unlike provider signatures, which expire after a few minutes.
Can I self-host it?
Yes. It ships as Docker images with a production compose file. With billing turned off, every organization gets one plan's limits and nothing talks to Stripe.
What counts toward my monthly events?
Each webhook received, and each replayed delivery. Retries of the same delivery are free. Usage resets on the 1st of each month (UTC).
Your next webhook outage, solved in minutes.
Set up in five minutes. Free up to 10,000 events a month.