Interesting that they seem to be trying to coin a new term here.

I like it a bit more than "webhook proxy" but I'm not sure calling it a gateway is the best fit, either.

Hey!

Convoy Founder here.

The way we think about it is API Gateways are the entry point to your API. Webhook Gateways are the exit point to the API. Hence the name. :)

I think callling it a gateway might be slightly correct. For example an API gateway acts as a reverse proxy to accept all API calls whilst handling traffic authentication and authorization and even things like A/B testing capabilities. A webhooks proxy that supports both sending and receiving might be classified as a gateway.

Well the technology does more things that a conventional proxy, I'd say it's a proxy with batteries Included. I love the gateway term and the great similarity to API gateways; very relatable.

I love this but I’m looking for the other direction. What about receiving hooks?

I’ve often wondered where Hookdeck like service is that has an OSS core. This looks like a fantastic approach, bravo.

That's exactly what Convoy is. It's open source and supports both directions of webhooks. Receiving and Sending. See here [1] to get started receiving.

[1] https://getconvoy.io/docs/getting-started/receiving-webhook-...

Convoy handles both incoming and outgoing Webhooks, think of Hookdeck + the sending side but OSS

It wasn’t immediately clear, but can Convoy be used to mutate an incoming webhook before fanning it out? So that a single incoming webhook can be “translated” to formats used by disparate systems?

Not at the moment. But this is currently on our roadmap. See here [1]

[1] https://github.com/orgs/frain-dev/projects/3