You can read more about why we built Svix in the original Show HN[0], though the gist is: our customers wanted webhooks to build integrations and workflows around our product, but we weren't willing to commit the engineering time, resources and ongoing maintenance required of a webhook delivery system.
Why open source? On a personal level, I've been an open source maintainer and contributor for many years, and I care a lot about open source. So open-sourcing the Svix dispatcher was one of the first tickets I created on our issue tracker. As for the company, webhooks are currently a mess, everyone does them differently, with differing levels of quality and features supported. This is something we really want to fix. The Svix service is already making a difference there (we're lucky enough to call some really cool companies our customers), and open-sourcing the dispatcher is the next logical step to increase our impact.
Why Rust? It's really fast, it makes writing secure and correct code easier, it's easier to deploy and distribute (one static binary), and it's a lot more fun. :)
Webhooks are really cool, and I absolutely love what they enable. They make the web compose-able, interconnected, and enable people to automate a lot of their work! Our goal is to make them easy, reliable, and consistent, so that more services offer them and they are easier to consume.
I'd love to hear your feedback! We've incorporated most of the comments we got the last time[0] (thanks again everyone!), and we would love to know how we can improve the product further. Got any suggestions?
Homepage: https://www.svix.com
Repo: https://github.com/svix/svix-webhooks/
Docs: https://docs.svix.com/
API reference: https://api.svix.com/