| webhook.site | WebhookVault | |
|---|---|---|
| Instant no-signup URL | ✓ its superpower | signup first (free, under a minute) |
| Retention | days on paid; requests capped | 3-365 days by plan, limits published |
| Search stored requests | basic | method, state, time, text, body search on Pro |
| Forwarding | forwarding & XHR redirect | durable outbox: retries, backoff, dead-letter, per-attempt ledger |
| Replay | re-send | single + bulk through the audited pipeline |
| CI testing mode | - | ephemeral TTL endpoints + block-until-arrival await API |
| Missing-webhook alarms | - | ✓ Watchdogs: cadence alarms per sender |
| Custom scripting on requests | ✓ WebhookScript engine | transformations on Pro |
| Mandatory 2FA + passkeys | optional | 2FA required on every account |
| Price of the useful tier | from ~$9/mo | $5 Solo · $9 Pro, every limit published |
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 the vault is
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 the vault starts keeping. Your webhook.site flows keep working for scratchpad moments; plenty of our users run both.
Try the vault next to it.
Free tier, no card, point one provider at it and compare with your own traffic.