Are Webhooks ready for “as-a-Service” treatment?

Webhooks have become the glue holding modern SaaS together. Stripe, GitHub, Shopify, Slack — they all rely on them.

But once you’ve built webhook delivery at scale, you realize it’s not “just a POST request”:

• Retries & exponential backoff

• Dead-letter queues

• Signature verification & replay protection

• Monitoring & observability

• Customer support when events go missing

We just published a deep dive into the idea of Webhook-as-a-Service (WaaS) — what it is, why teams are adopting it, and whether it deserves to be a standard developer primitive like storage, queues, or databases.

👉 Read the full guide

Curious to hear from this community:

1. Have you built webhook infra in-house?

2. Would you trust a 3rd-party WaaS provider?

3. Or do you think this is still too niche to become “infra-as-a-service”?