I built NotifyKit after running into the friction of working with multiple email providers across different projects. Each provider had its own API, logging system, retry behavior, and quirks, which made switching providers or combining them unnecessarily complex. I wanted a way to abstract that complexity into a single, consistent interface. Something that would let developers plug in multiple providers, choose the best one for each use case, and still have unified visibility into delivery, logs, and failures. While building it, the focus evolved from just “sending emails” to designing a reliable delivery system. That led to adding queue-based processing, retries with backoff, rate limiting, and automatic failover—where failed requests are retried using the next available provider or API key. Over time, it became less of a wrapper and more of a notification infrastructure layer with observability and control built in.

NotifyKit

The notification infrastructure for modern products.

The notification infrastructure for modern products.