webhook.site is a quick online tool for inspecting webhook payloads. Corral is a self-hosted binary with persistent storage, replay, and forwarding. Different tools for different jobs.
| Corral | webhook.site | |
|---|---|---|
| Hosting | Self-hosted | Hosted online (their servers) |
| Setup | curl install + run | Visit website, copy URL |
| Persistent storage | Yes — SQLite, configurable retention | No (temporary, session-based) |
| Capture & inspect | Yes | Yes |
| Replay | Yes (Pro) | No |
| Auto-forwarding | Yes, with retry (Pro) | No |
| Multiple endpoints | Yes, named and persistent | One per session |
| Data on your servers | Yes | No |
| Works offline / LAN | Yes | No |
| Price | Free (3 endpoints) / $0.99/mo | Free / Pro ~$9/mo |
If you need to see what a webhook payload looks like right now — no setup, no binary, just open a URL — webhook.site is the fastest way to do that. It's genuinely useful for a quick one-off inspection.
The tradeoff: payloads are temporary, forwarding isn't built in, and you're sending potentially sensitive data through their servers. For local development or production debugging, those tradeoffs add up.
Corral is the right tool once you move past the "what does this payload look like" phase into actually building with webhooks:
Corral vs Hookdeck · How to debug webhooks locally · Corral overview
Corral runs as a single binary on your server. Webhooks arrive at your endpoint, get logged to embedded SQLite, and optionally get forwarded to your application. Webhook.site is a cloud service — webhooks route through their infrastructure before reaching yours. For payment webhooks containing transaction amounts and customer data, the distinction between self-hosted and cloud-routed is a compliance question, not just a preference.
Every webhook Corral captures is stored in a SQLite database on your server. Export captured webhooks by querying the database directly or through the API. Replay any historical webhook to test updated handler code. With Webhook.site, your captured webhooks live on their servers — if you stop paying or they change their retention policy, that history disappears.
If you are building webhook integrations and need a capture tool during development, try Corral alongside Webhook.site. Point your webhook source at both endpoints for a week. If Corral handles your workflow — capture, inspect, replay, forward — switch over fully. The migration is instant because webhook endpoints are just URLs you configure in the sending service.
Single binary. Runs on your machine or your server. Free to start.