Webhook infrastructure. Less drama.

Your events.
Delivered.
Even on a bad day.

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.

ONE EVENT’S JOURNEYTimed example
{ }Your apporder.completed
POST event
PayloadPuffinReceiving event
Signed request
↗Your customerWaiting
Store202 ACKScheduleDeliverReceived
→
Your producer sends one event.

The payload travels to PayloadPuffin. No consumer request yet.

evt_demo_01 · same event throughoutBefore delivery
Retry waits shortened for demo.
Your delivery stack, handled

Durable storage Fan-out Signed requests Automatic retries Replay

01Emit

You built a product.
Then webhooks became one.

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.

POST/v1/eventsapplication/json
1{
2  "type": "customer.created",
3  "payload": { "id": "cus_8fK2", "plan": "pro" }
4}
Example request. Press send.

02Accept

202 means
it’s ours now.

The payload is durably stored and its deliveries are queued before we answer. From there, the event keeps its ID through every attempt.

  • At-least-once delivery
  • Independent retries per destination
  • No mystery about what happened

03Fan out

One event.
Everywhere it needs to go.

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.

  • Customer APIcustomer-a.com/webhooks200 · 190ms
  • Slack#signups200 · 102ms
  • CRM synccrm.internal/hooks503 · 1.82sretry · +5s200 · 183ms
Example: one customer.created event is delivered to three destinations. CRM sync answers 503 on the first attempt and 200 on the retry.

04Retry

A 503 shouldn’t be
the end of the story.

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.

RETRY QUEUE
evt_01a10c7a…21b7
  1. +5s
  2. +5m
  3. +30m
  4. +2h
  5. +5h
  6. +10h
  7. +10h
Example: a delivery that failed with 503 waits in the retry queue, and attempt 2, five seconds later, returns 200. Retries follow the default schedule of 5 seconds, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours and 10 hours.

05Ingest

Their webhooks.
Your rules.

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.

Stripeinvoice.paid
signature verified
transform()
Your appacme.dev/hooks/stripe
200 · 74ms
Example: an invoice.paid webhook from Stripe is verified, transformed and delivered to your app.

06Inspect

“Where’s my event?”
Glad you asked.

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.

Events

last 5 minutes · all destinations
Deliveredinvoice.paidevt_01a10c7b…9e2facme.dev/hooks/stripe20074ms1
Deliveredcustomer.createdevt_01a10c7a…21b7crm.internal/hooks200183ms2 retried
Attempt 114:32:07.412POST https://crm.internal/hooks5031.82sretry scheduled · +5s
Attempt 214:32:12.430POST https://crm.internal/hooks200183ms
Deliveredcustomer.createdevt_01a10c7a…21b7slack · #signups20096ms1
Deliveredcustomer.createdevt_01a10c7a…21b7customer-a.com/webhooks200182ms1
Deliveredcustomer.updatedevt_01a10c78…c4d1customer-a.com/webhooks200164ms1
Example event log: five delivered events. customer.created to crm.internal/hooks failed with 503 on attempt 1 and was delivered with 200 on attempt 2, five seconds later.
Original payload. Every attempt.

The full picture.

Track event volume, success rates, latency, and destination health. Find the bottleneck before it becomes a support ticket.

Analytics + destination health

A signature, not a guess.

Every destination has its own signing secret. HMAC-SHA256 signatures let receivers verify who sent the request.

Signed webhook delivery

Fits the way you build.

A straightforward HTTP API, a TypeScript SDK, and test tooling. Send your events without adopting a whole new stack.

API + TypeScript SDK

A few good questions

Clear answers.
No fine-print safari.

What exactly is PayloadPuffin?

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.

What happens when a delivery fails?

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.

Are events delivered exactly once, and in order?

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.

When can I use it? What will it cost?

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 events. Delivered.

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.