The full picture.
Track event volume, success rates, latency, and destination health. Find the bottleneck before it becomes a support ticket.
Analytics + destination healthWebhook infrastructure. Less drama.
Send and receive webhooks without building the plumbing. PayloadPuffin handles delivery, retries, and replay, so a failed request doesn’t become your next project.
Early access. No credit card. Just a heads-up when we’re ready.
The payload travels to PayloadPuffin. No consumer request yet.
Durable storage Fan-out Signed requests Automatic retries Replay
01Emit
It starts with a POST request. Then come the timeouts, the retry queue, the signing secrets, and the customer asking where their event went.
That’s a whole delivery system hiding inside your feature. Let the puffin carry it. Emit the event and keep moving; your application doesn’t wait on anyone’s destination.
1{
2 "type": "customer.created",
3 "payload": { "id": "cus_8fK2", "plan": "pro" }
4}02Accept
202 meansThe payload is durably stored and its deliveries are queued before we answer. From there, the event keeps its ID through every attempt.
03Fan out
Fan one event out to as many destinations as need it. Each one gets its own signed request, its own retries, and, when the shape has to change, its own sandboxed JavaScript transform.
04Retry
Timeouts, network errors and non-2xx responses go to the retry queue. Up to eight attempts over roughly 28 hours, with the original payload every time.
One unavailable destination never holds up the rest. When retries run out, the event stays inspectable and replayable.
05Ingest
Point Stripe, GitHub or any provider at PayloadPuffin. We verify the signature with your source’s secret, store the event, transform it if you like, and deliver it to your own services.
06Inspect
Follow an event from acceptance to delivery. Every attempt, request and response is in a searchable history. Fixed the destination? Replay the original event without asking a customer to trigger it again.
Track event volume, success rates, latency, and destination health. Find the bottleneck before it becomes a support ticket.
Analytics + destination healthEvery destination has its own signing secret. HMAC-SHA256 signatures let receivers verify who sent the request.
Signed webhook deliveryA straightforward HTTP API, a TypeScript SDK, and test tooling. Send your events without adopting a whole new stack.
API + TypeScript SDKA few good questions
Managed event and webhook delivery infrastructure. Send events from your application through our API, or receive incoming webhooks from external providers. We store the event, fan it out to every destination whose filters match, optionally transform it, and deliver signed HTTP requests. You get retries, searchable history, analytics, and replay in one place.
Timeouts, network errors, and non-2xx responses trigger automatic retries. The default policy makes up to eight attempts over roughly 28 hours. After retries are exhausted, the delivery is marked failed and stays inspectable for manual replay. A failing destination doesn’t block deliveries to other destinations.
Delivery is at-least-once, so receivers should handle duplicate event IDs. Deliveries run in parallel with independent retries; strict FIFO ordering is not part of the initial release. A 202 response means the event has been durably stored and queued, not that the receiving application has already processed it.
PayloadPuffin is in development. Join the waitlist and we’ll email you when early access is available. Pricing is still being finalized; we’ll share the plans before you commit. Joining the waitlist is free and doesn’t require a credit card.
Your next feature isn’t a retry queue. Be among the first to put PayloadPuffin to work; join the waitlist for early access.
Early access. No credit card. Just a heads-up when we’re ready.