Trusted by teams at
webhook.site catches inbound HTTP for debugging. Hook0 sends webhooks out to your customers with HMAC signing, retries, delivery logs and a subscriber portal. Different job, same domain. Open-source.
100 events/day free. No credit card. Open-source.
Trusted by teams at
webhook.site receives. Hook0 sends. Picking the right one upfront saves you a refactor later.
| Need | webhook.site | Hook0 |
|---|---|---|
| Inspect incoming requests for debugging | Yes | Yes (play.hook0.com) |
| Send webhooks to your customers in production | No | Yes |
| HMAC-sign every payload | No | Yes |
| Retries and dead letter queues | No | Yes |
| Subscriber portal for your customers | No | Yes |
| Self-host on your infra | No | Free (SSPL-1.0) |
| Free tier | Yes | Yes |
Sign up, create an application. You get an auth token and an application ID on the spot. No credit card.
Replace the webhook.site URL with a Hook0 API call. Python or Node.js SDK, or plain HTTP.
Drop the subscriber portal in front of your customers. They register their own endpoints, rotate their own keys, read their own delivery logs.
// Before. webhook.site as a debug receiver:
fetch("https://webhook.site/abcd-1234", {
method: "POST",
body: JSON.stringify(payload)
});
// After. Hook0 as a production webhook platform:
await hook0.message.create("<application_id>", {
event_type: "invoice.paid",
event_id: "evt_Wqb1k73rXprtTm7Qdlr38G",
payload
});
// What changes for your subscribers: signed payloads,
// automatic retries, delivery logs they can replay themselves.
Yes — Hook0 is the production-grade alternative when you outgrow webhook.site. Where webhook.site is a request inspector ("what payload did I receive?"), Hook0 is a webhook platform: it sends events to your subscribers, signs them with HMAC, retries on failure, and stores delivery logs. Use webhook.site to debug; use Hook0 in production.
Sign up for Hook0 (free, no credit card), create an application, and replace the webhook.site URL in your code with one Hook0 REST API call. You get HMAC-signed delivery, retries, dead letter queues and a subscriber portal — no code change beyond the API endpoint.
Yes. Every event sent through Hook0 is logged with the full request, response, status code and latency. You can replay any event from the dashboard. For ad-hoc testing without an account, play.hook0.com lets you generate disposable webhook URLs the same way webhook.site does.
Yes. Hook0 is fully open-source under SSPL-1.0 and self-hostable on Docker Compose or Kubernetes. webhook.site is a closed-source SaaS. If you need to keep traffic on your own infrastructure, Hook0 is the answer.
Stop building webhook infrastructure. Start shipping features. Get started in minutes.