Ingestlayer

Hey HN, I got tired of rewriting the same event handling code, so built a more permanent solution for myself. The idea is something happens here (a signup, a failed payment, a support ticket, an error) and three things need to happen there: a Slack message, a row in a database, an email. Every time it's a new handler in code (maybe even retries, a queue, etc.) and maybe even more work integrating with Customer.io, Zapier, and so on to "get it there".So I built my own, re-usable solution that handles the above. You build a pipeline, throw events at it (SDK or HTTP), and it runs on every event. In the middle of the pipeline you can enrich the payload with an HTTP call, branch/filter, reshape fields, or run an AI step when you need one. Then it fans out to your destinations. The whole pipeline is also representable as YAML, so it's reviewable and diffable rather than a flowchart you click together. Agents can have a token and fire data at a pipeline for further processing.The sources and destination catalogue is still small tbh. but I'm adding more as I go.It's live at ingestlayer.com. I'd appreciate any feedback, especially what would make you go "I'd use this if it also did X."