We are building Convoy for engineering teams that value efficiency, especially during this bear market. You might already know about API Gateways. Convoy is exactly that for webhooks. Engineering teams today use Convoy to securely send, receive and manage millions of webhooks reliably with robust support for retries, rate limiting, static IPs, circuit breaking, rolling secrets and more. We know both receiving and sending webhooks can become a lot of work to manage, we have built a product to enable engineers to build and ship highly scalable stripe-like webhooks infrastructure.
Subomi Oluwalana is the Co-founder and CEO of Convoy. Subomi is a software engineer and entrepreneur. Nothing excites him more than bringing ideas to life. Originally, He graduated from Landmark University where he received a Bachelor in Accounting & Finance.
Emmanuel Aina is the Co-Founder, Chief Operating Officer, and Software Engineer of Frain. Emmanuel ensures that business and engineering operations run with little to zero blockers along with leading Frontend Engineering efforts. Previously he lead a Frontend Engineering team at Tangerine Africa. With his background with an artist and a designer parent, he is always biased towards building user friendly and usable solutions. He earned a degree in Computer Science from South American University.
TL;DR: Convoy provides a reliable webhooks proxy that can ingest webhooks from all your providers and replay them to your backend as well as publish webhook events from your systems to your customers.
Hey YC 👋🏾
I am Subomi, and I am building Convoy alongside Emmanuel.
The Problem
Today, webhooks power critical business workflows that, if broken, will have a direct impact on customers’ experience. Usually, developers spend time building reliable webhook ingestion services and reliable webhook dispatching services for API providers. This time is wasted effort that can be spent building necessary infrastructure instead of building your product. Secondly, the tooling becomes fragmented for dispatching and receiving webhook events. We are working on Convoy to solve precisely this using a consistent toolchain to receive, publish and debug webhook events.
Our Solution
Enter Convoy, a service available as an open-source project and a cloud platform. There are two types of projects in Convoy; an incoming project and an outgoing project. In an incoming project, we provide a unique URL per provider to receive events, and in an outgoing project, we provide a REST API to receive events from your services and publish them to the outside world.
How it works?
You can see a demo here.
Asks
Thank you!