January 6, 2026
4 min read
Loading...
Bi-weekly engineering deep dives on auth, notifications, and developer infrastructure. No spam.
Sign Up for UpdatesPublished by Zyphr
Today we're opening Zyphr to public beta. Before we talk about features, we want to talk about why this thing exists.
We've spent years building SaaS products. Every single one needed the same two things on day one: user authentication and transactional messaging. Sign up? Send a verification email. Forgot password? Send a reset link. Enable MFA? Deliver an OTP. Suspicious login? Fire a security alert.
Auth and notifications are inseparable. But the tooling treats them as completely different concerns.
So you pick an auth provider. You pick an email provider. Then you spend the next two weeks writing glue code — webhook handlers, queue consumers, template syncing, error handling, retry logic — just to connect the two. You end up maintaining a fragile integration layer that touches every critical user interaction in your app.
We did this enough times to get tired of it.
Here's what a "standard" SaaS notification stack looks like in 2026:
Five vendors. Five dashboards. Five billing relationships. Five sets of API keys. Five SDKs. And a pile of custom code that nobody wants to maintain but everybody depends on.
We watched this pattern repeat across every project we touched. Not just our own — teams we advised, companies we consulted for, open-source projects we contributed to. Everyone was solving the same problem with the same duct tape.
The idea behind Zyphr is simple: auth events and their corresponding messages should be part of the same system.
When a user registers, the verification email should just happen. When they reset their password, the reset link should just go out. When they enable MFA, the OTP should just arrive. No webhooks. No glue code. No second API call.
But we didn't want to stop at auth-triggered emails. If you're already sending transactional messages, you need the full channel set: email, SMS, push notifications, and in-app inbox. You need templates. You need subscriber preferences. You need delivery tracking. You need webhooks for your own downstream systems.
So that's what we built.
Zyphr is a developer platform that combines user authentication and multi-channel transactional messaging into a single API:
One SDK. One dashboard. One bill.
We're calling this a beta because we're honest about where we are:
Over the coming weeks, we'll publish deep dives on the architecture decisions behind Zyphr — why we chose to build auth and messaging as a unified system, how we designed the webhook infrastructure, and how our multi-channel delivery pipeline works.
If you've ever been frustrated by the duct tape stack, we built this for you. Sign up, break things, and tell us what's missing.
