Idea checked
a webhook delivery service for small teams
There is clear demand for webhook reliability tooling, but this is a crowded space with several direct competitors already serving small teams.
Confidence: high — The signals include multiple recent HN launches, several existing products, and search snippets describing current feature sets and gaps. This is enough to judge competition and likely positioning, though not enough for hard market sizing.
- hackernews 23
- github 11
- tavily 8
Who is already building this From data
-
Svix is an established webhook-sending infrastructure product from a YC-backed founder, with hosted SaaS, EU hosting, and self-hosted options; it covers subscriptions, retries, signatures, and replay.
-
Hookdeck is positioned as a stronger general webhook infrastructure platform, with inbound event gateway plus outbound sending, observability, and lower per-event pricing than alternatives.
-
Webhook Relay already sells forwarding to any destination, with audit trail, RBAC, encryption, 99.99% SLA, 30-day retries, and self-hosting.
-
Several newer or smaller projects are explicitly focused on webhook delivery or reliability, including Vartiq, Zyra, HookTrials, and Relora.
What people actually say From data
-
Founders and users keep describing webhook delivery as deceptively complex, especially retries, backoff, handling non-2xx responses, monitoring, alerting, back-pressure, and signing.
-
People say webhooks are foundational to modern SaaS integrations, but teams still end up rebuilding retry queues, dead-letter queues, signature validation, replay protection, and monitoring.
-
A recurring complaint is the pain of production troubleshooting and missed deliveries; Hookdeck’s launch and later positioning both point to this being the core problem.
-
There is some interest in team workflows around webhooks: UnWebhook was pitched for analysis, replay, and fallback delivery between a personal machine and a shared staging environment.
Where the opening is From data
-
Some products still focus mostly on HTTPS delivery and do not cover broader destination types, transformations, FIFO, or throttling.
-
Webhook Relay emphasizes forwarding and reliability, but the snippet does not show advanced workflow logic like transformations or destination breadth beyond forwarding.
-
Several open-source tools are aimed at testing or local debugging rather than full production delivery, which leaves room for a simpler operational layer for small teams.
-
A likely gap is teams that want webhook delivery without buying a broad integration platform; the search results show focused products, but not many that are explicitly small-team-first and narrow in scope.
How big the market might be Model estimate
The model's read of the signals below — not something anyone measured.
-
I cannot size the market from these signals alone; there are no revenue, customer-count, or traffic numbers.
-
The demand signal looks real because multiple independent products exist and multiple HN posts over several years talk about the same delivery problem.
- hackernews Launch HN: Svix (YC W21) – Webhooks as a Service 2021-06-16
- hackernews Show HN: Vartiq – Webhook Infra for High-Velocity Dev Teams 2025-07-21
- hackernews Show HN: Webhook delivery as a Service (built by ex-YC founder/Stripe engineer) 2021-02-01
- hackernews Show HN: Open-Source Webhooks Gateway for Platform Engineers 2023-03-31
- hackernews Show HN: Hookdeck – An infrastructure to consume webhooks 2021-08-04
-
This feels like a niche B2B infrastructure market rather than a huge standalone category, with value concentrated in teams that send many events or support integrations.
-
The strongest near-term buyers are probably small SaaS teams that already know webhooks are failing them, not general-purpose developers looking for a nice-to-have tool.
What could go wrong Model estimate
The model's read of the signals below — not something anyone measured.
-
Competition is the biggest risk: Svix, Hookdeck, and Webhook Relay are already visible, credible options with real feature depth.
-
Feature creep is a risk because the problem space naturally expands into observability, retries, queues, replay, alerting, RBAC, self-hosting, and multi-destination delivery.
-
A narrow webhook delivery service may be hard to differentiate if it only does reliable sending, because several existing tools already claim that core value.
-
Operational reliability is table stakes in this category; the market already talks in terms of 99.99% SLA and 30-day retries.
What to do this week Model estimate
The model's read of the signals below — not something anyone measured.
-
Pick one narrow wedge that the bigger players do not emphasize, such as small-team simplicity, very fast setup, or a specific destination/workflow gap, rather than building a full webhook platform.
-
Talk to small SaaS teams that already have webhook incidents and ask what they built themselves: retries, queueing, dead-letter handling, signing, replay, or alerting.
-
Build a minimal product that proves one painful use case end to end, like reliable outbound delivery with visibility and replay for teams without platform engineers.
-
Validate whether the buyer wants hosted only, self-hosted only, or both, since the current market has examples of all three.