Why catchbin exists

You're integrating Stripe. You configure a webhook.site URL, debug for a few days, come back the next week — and the URL is gone. Stripe is logging failed deliveries, your captured history is wiped, and you're reconfiguring the endpoint from scratch. ngrok has the opposite problem: the tunnel only exists while your laptop is open, so anything that arrives while it's closed is simply lost.

catchbin exists because that dance got old.

It's a webhook inspector built around URLs that don't expire. Point a provider at a catchbin URL once. Every event that arrives is captured and held, whether or not your local server is up. Inspect the raw request, replay any event with one click, forward traffic to localhost through a small CLI — and when signature verification fails, see why. Nine times out of ten it's a middleware layer mutating the raw body before your handler sees it; catchbin shows you the byte mismatch instead of a bare "invalid signature".

How it's built

A tool that asks you to send it your webhook traffic should be able to say how it treats that traffic:

• Webhook payloads are encrypted at rest.
• Payloads, secrets, and full headers never appear in our logs — the build fails if a code change tries.
• The forwarding CLI is open source:github.com/catchbin/cli.

Who builds it

catchbin is built and run by one developer — Aubrey Kilian. That means no sales team and no support tiers, but it also means the person reading support@catchbin.io is the person who wrote the code.

Every webhook, caught.