Launching today

Posthawk
The email layer that ships with your deploy
7 followers
The email layer that ships with your deploy
7 followers
The email layer that ships with your deploy. Edge-native transactional email for Next.js, Vercel, and Cloudflare Workers — with an open-source self-host option.








love that this plugs straight into the deploy pipeline without a third party. one thing that would push me to switch from resend is built in bounce and complaint webhooks with retry logic, so failed sends dont just disappear into the void. would save me from wiring up another service just to keep my list clean.
@gcekirdek75377 Appreciate that, and you are describing pretty much why I built it this way.
Bounce and complaint handling is built in, not a bolt-on. Posthawk ingests the SES bounce and complaint events and auto-suppresses for you: hard bounces and spam complaints get added to your suppression list immediately, and it also catches soft-bounce patterns (three consecutive soft bounces from an address and it gets suppressed too, with the counter resetting on a successful delivery). So your list stays clean on its own, without you standing up a separate service just to prune it.
On top of that there are signed outbound webhooks so you can pipe those same events into your own stack, and everything lands in the metrics dashboard, so a failed send never just disappears into the void.
Curious what your ideal setup looks like here. Do you want the events pushed to you to act on, or are you happy letting the platform handle suppression and just reading the dashboard? Genuinely shaping this surface right now, so feedback like this is gold.
Really cool to see an email layer that lives at the edge. One thing that would make my life easier is built-in bounce and complaint webhook handling with automatic suppression list sync, so I don't have to wire up SES or Resend webhooks manually just to keep my sender reputation safe.
The setup felt almost too easy, just dropped it into my Next.js project and it was sending before I even refreshed. Loving that it runs at the edge instead of another round trip to a third-party API.