| Area | webhook.site | WebhookVault |
|---|---|---|
| Built for | A quick look at a payload: a URL with no account, and scripted workflows on paid plans | Receiving webhooks and keeping every one: verify, forward, replay, watch |
| A URL with no account | Instant; the URL and its data are removed after 7 days, and it stops accepting after 100 requests | Sign up first: free, a few minutes, with two-factor authentication required |
| Paid plans | Basic $9, Pro $27, Enterprise $69 a month; flat | Solo $5, Pro $9, Team $15 a month; flat |
| History kept | 365 days on every paid plan | 30, 90 or 365 days on Solo, Pro and Team; 3 days on Free |
| Requests kept | 1,000, 10,000 or 100,000 per URL, with 1, 50 or unlimited URLs | 5,000, 25,000 or 100,000 per endpoint, with 15, 50 or 200 endpoints |
| Signature verification | Not stated in its docs | A verdict on every request; presets for 56 providers plus manual schemes; from Solo |
| Forwarding to your app | The CLI relays a URL's traffic to any target, localhost included; retries not stated | Durable outbox: eight attempts over about an hour, dead-letter alerts, a record of every attempt |
| Replay | Not stated in its docs | One request on any plan, in bulk from Solo |
| Alarm when webhooks stop arriving | Not stated in its docs | Watchdogs alarm when a webhook misses the interval you set; from Solo |
| Scripting on requests | WebhookScript Custom Actions and schedules, from Basic | Eleven no-code rule operations per action, from Pro |
| Inbound email | Custom email addresses, from Basic | Not offered |
| CI testing | No dedicated mode stated | Self-expiring endpoints and a wait-for-arrival API, from Solo |
| Teams and sign-in | Multi-user and SAML SSO on Enterprise | 1, 1, 3 or 10 seats by plan; no SAML; two-factor required on every account |
| Custom domain | On Enterprise | Not offered |
| Self-hosting | An MIT-licensed open-source version, without Custom Actions | Managed only |
WebhookVault figures are from our pricing page. Prices are in USD as published. Spotted something out of date? Tell us and we will correct it.
When webhook.site is the right choice
You want a URL right now, no account, to eyeball a payload once, or you want its custom scripting engine to transform requests inline. It's excellent at both. We're not going to pretend otherwise.
When WebhookVault is the right choice
The moment webhooks become infrastructure rather than a curiosity: you need last month's deliveries, not last hour's; "did it arrive?" answerable in CI; forwarding that survives a crash and shows its receipts; the payload findable by the order ID inside it.
Migrating is nothing
There's nothing to migrate: create an endpoint, swap the URL at your provider, and WebhookVault starts keeping every request. Your webhook.site flows keep working for scratchpad moments, so nothing stops you using both.
More comparisons: vs Hookdeck · vs Svix · all comparisons
Try WebhookVault next to it.
Free tier, no card, point one provider at it and compare with your own traffic.
Sign up with GitHub, Google or email. Two-factor authentication is required on every account, Free included, for account security.