Hookflo tern - Webhook verification, without the boilerplate.

Zero-dependency webhook signature verification and reliability SDK - Hookflo/tern

Add a comment

Replies

Best
Hey Product Hunt 👋 Maintainer of Tern here, With Tern here to solve a very specific problem with webhooks: the verification layer shouldn’t need to be reinvented for every provider. Stripe, GitHub, Clerk, Shopify, Linear, Sentry and others all have slightly different signing schemes, headers, timestamps and edge cases. Tern gives you one verification layer for all of them. You get: 15+ providers · multiple signing algorithms · automatic provider detection · Next.js/Express/Hono/Cloudflare adapters · custom provider configs · stable verification errors · zero dependencies And it goes beyond signatures. Tern can optionally handle retries, deduplication, dead-letter queues, replay controls and Slack/Discord alerts through QStash, so the same layer can take you from "is this webhook authentic?” to “what happens when delivery fails?” It’s open source, TypeScript-first, and designed to stay out of your way. I built this because webhook infrastructure felt unnecessarily fragmented Tern is my attempt to make it feel like one coherent primitive. if your app consumes webhooks, this is worth trying.🚀 If you have any questions, run into an issue, or want to see a specific platform supported, drop a comment I’d love to hear from you. And if Tern looks useful, a ⭐ on the repo would mean a lot and help more developers discover it
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
Vercel v0, Vercel for Deployment, Next.js