Relaybench is a test bench for the endpoints that receive webhooks. Point a payment provider, a shipping carrier or your own service at a Relaybench address, then replay the same event twice, deliver it out of order, hold it for six minutes or send it with a signature that is one character wrong. You find out which of your handlers fall over while the fix is still cheap.
Free during the beta. Wave two onboards 150 engineering teams.
Each one comes from a real incident report that a beta team shared with us.
Pick a delivery from your history and fire it again. Relaybench shows what your handler did the second, fifth and fiftieth time it saw the same event identifier.
Slide a control to hold events back or swap their order, the way a real provider does during an outage. Your idempotency logic gets its first honest workout.
Send payloads with an expired timestamp, a rotated secret or a single flipped byte, and watch whether your verification code rejects them for the right reason.
Start from a library of realistic payloads for payments, shipping, identity and chat, written from each provider's own documentation and refreshed monthly.
Run the same chaos suite on every pull request. A failing handler blocks the merge with a readable diff of expected and actual behaviour.
Give support a link to a failed delivery and a button that says send again. Nobody needs a database login to help a customer.
Tell us where to send your invitation. We approve seats in the order teams sign up, with a head start for those who bring a colleague.
“Relaybench showed us in twenty minutes that our refund handler would charge twice if the provider retried. We shipped the fix before the next release.”
“Our support team now replays a failed delivery without opening a ticket with us. That alone saves a few hours every week.”
“I added the CLI to our pipeline on a Friday afternoon. By Monday it had blocked a merge that would have broken order sync for a whole region.”
No. The bench works on payloads you choose to import or fixtures we provide, and it never needs credentials to your live systems.
The CLI is a single binary for macOS, Linux and Windows and tests any endpoint over HTTP, so your handler can be written in whatever you like.
We expect to stay in closed beta until the end of the year, then open to everyone with a free plan for small projects.
Yes. Teams in the beta keep a generous free tier permanently and receive a discount on paid plans when they arrive.
Yes. A small tunnel agent opens an outbound connection only, so no inbound ports are required.
Join wave two, bring a colleague and run your first chaos suite in under half an hour.
Every request for a new failure mode is read by an engineer. Describe the outage and we will tell you if the bench can reproduce it.