Comparisons

How WebhookVault compares

WebhookVault receives the webhooks your providers send you and keeps every one: searchable and replayable for up to a year, forwarded to your app with retries, with an alarm when an expected webhook stops arriving. Here it is next to the three products people most often weigh it against, each read from its own public pages on 5 October 2026. Where another product is stronger, the table says so.

At a glance

Prices are in USD per month, as each vendor publishes them.

AreaWebhookVaultHookdeckSvixwebhook.site
Built forReceiving webhooks and keeping every one: verify, forward, replay, watchReceiving, queueing and delivering inbound events at volumeSending webhooks from your product; Svix Ingest receivesA quick look at a payload; scripted workflows on paid plans
Free plan 3 endpoints, 3 days of history, 100 requests each 10,000 events a month, 3-day retention 50,000 messages a month, 7-day retention No account: a URL for 7 days, stops after 100 requests
Paid plans, per month (USD) $5, $9, $15 From $39 and $499, then metered From $20 and $490, then metered $9, $27, $69
How the bill moves Flat; your traffic never changes it Metered past 10,000 events, from $3.00 per 100,000 $0.0001 per message past 50,000 Flat
Longest history 365 days, on Team at $15 30 days on Growth at $499; longer on Enterprise 90 days on Professional at $490; longer on Enterprise 365 days on every paid plan
Requests kept Up to 100,000 per endpoint, across up to 200 endpointsNot stated as a count; bounded by retentionNot stated as a count; bounded by retention Up to 100,000 per URL on Enterprise at $69
Alarm when a webhook stops arriving Watchdogs, from Solo Not among its issue types Not stated on the pages read Not stated in its docs
A request whose signature fails Kept and labelled failed; re-checked when you fix the secretRejected at the source and raised as an issueIngest verifies known providers; generic sources skip it Verification not stated in its docs
Forwarding with retries Eight attempts over about an hour, then dead-letter with an alert Up to 50 automatic retries on your interval Eight attempts over just over 27 hours CLI relays to any target; retries not stated
Replay One request on any plan, in bulk from Solo One event, or in bulk by filter One message, or every failure since a date Not stated in its docs
Transform or script requests Eleven no-code rule operations, from Pro JavaScript on every plan JavaScript, listed on every plan WebhookScript Custom Actions, from Basic
Local and CI testing Self-expiring CI endpoints and a wait-for-arrival API, from Solo; no local tunnel CLI relays to localhost; Console needs no account Svix Play needs no signup; CLI relays to localhost No-account URL; CLI relays to localhost
Send webhooks to your own customers Not offered; WebhookVault is the receiving side Outpost, a separate open-source product Dispatch, its main product Not in its plans
SSO, uptime SLA, audit report None of the three SSO and SCIM, 99.999% SLA, SOC 2 Type 2 99.9% SLA from Basic; SOC 2 Type II from Professional SAML SSO on Enterprise; SLA and audit not stated
Self-hosting Managed only Event Gateway is managed only MIT-licensed server MIT-licensed version, without Custom Actions

Key: ✓ covered · ◐ covered, with limits or a different approach · ✕ not offered or not stated

WebhookVault figures are from our pricing page. Prices are in USD as each vendor publishes them, per month, before tax. Spotted something out of date? Tell us and we will correct it.

Where WebhookVault stands out

What you get here that the others do not offer, or charge far more for.

An alarm for the webhook that never arrives

A Watchdog holds the cadence you set for a sender and raises the alarm when a window passes with nothing. A provider that silently stops sending is the failure nothing else catches; none of the three lists an alarm for it.

A year of history for $15

Team keeps 365 days and up to 100,000 requests per endpoint across 200 endpoints, at a flat $15 a month. Hookdeck's published plans top out at 30 days, on its $499 plan, and Svix's at 90 days, on its $490 plan; webhook.site keeps 100,000 per URL on its $69 plan.

A bill your traffic cannot move

Every plan is a flat monthly price with every limit published. Hookdeck and Svix meter by volume past their included events, so a busy month or a retry storm at your provider shows up on the invoice.

A failed signature is kept, not dropped

A request that fails verification is stored and labelled failed, so you can see exactly what arrived. Fix the secret and the stored history is checked again. Hookdeck rejects such a request at the source.

Forwarding with a record of every attempt

Each capture goes to your app through a durable outbox. Every attempt is kept with its status and timing, a dead letter raises one alert per outage with a resolve notice, and any request can be replayed to one action or all of them.

Built for CI

Create a self-expiring endpoint, run your test, and one API call waits until the webhook lands or times out. Proof in your pipeline that the integration fires, without a tunnel or a sleep.

The full comparisons

Every row, product by product.

THE CLOSEST

WebhookVault vs Hookdeck

Both receive, verify, transform and deliver webhooks. Hookdeck is a managed event queue priced by volume. WebhookVault keeps every webhook you receive for up to a year, searchable and replayable, at a flat monthly price, and alarms when an expected one stops arriving.

A DIFFERENT JOB

WebhookVault vs Svix

Svix mainly sends webhooks on behalf of your product. WebhookVault receives the webhooks your providers send you, keeps each one and forwards it to your app. Svix Ingest, Svix's receiving product, is where the two overlap.

THE SCRATCHPAD

WebhookVault vs webhook.site

webhook.site gives you an instant, no-account URL for a quick look at a payload. WebhookVault keeps every request so you can search, replay and forward it later, and alarms when one stops arriving. Different jobs, and plenty of people use both.

Compare it with your own traffic.

Free tier, no card. Point one provider at WebhookVault and see what it keeps.