Novu

Move notification delivery behind one API and workflow layer

For product notifications, Novu exposes Inbox/In-App, Email, SMS, Push, and Chat through a common API and lets workflows define per-channel conditions and delivery paths. It also provides a digest engine, a no-code email editor, embeddable notification preferences, and a real-time React <Inbox /> component. Providers such as SendGrid, Resend, Amazon SES, and Twilio can sit behind Novu, reducing the amount of provider-specific logic that application code needs to own.

Sources: [1]

Normalize inbound messages and replies through one conversation model

Agent Communication Infrastructure receives messages from channels such as Slack, Microsoft Teams, Telegram, WhatsApp, and email, normalizes their platform-specific formats, and routes them to an existing agent. Agent responses can travel back through the same layer to the originating channel. This allows teams using AI SDK, LangGraph, Claude-based agents, or custom stacks to keep their agent logic while centralizing webhook handling, threading, reactions, formatting, and outbound delivery. Novu is the communication layer around the agent rather than the agent itself.

Sources: [1]

For teams expanding beyond email notifications

Novu fits SaaS and application teams adding in-app notifications, SMS, Push, and Chat alongside email, especially when provider switching, routing rules, digests, per-user preferences, and an Inbox UI would otherwise become separate projects. It is also relevant when an AI agent needs to reach users through several communication channels and the team wants to avoid maintaining a different inbound webhook and reply implementation for every platform.

Sources: [1]

Self-hosting means operating a multi-service communication platform

A self-hosted deployment includes application services such as the API, Worker, WebSocket service, and Dashboard as well as dependencies such as MongoDB and Redis. The repository's local Docker Compose setup starts development dependencies only and is not a production deployment by itself. Production use also requires secure secrets, persistence, appropriate database architecture, and credentials for whichever email, SMS, Push, or Chat providers are selected; those providers retain their own pricing and delivery limits.

Novu uses an open-core licensing model. The core is available under the MIT license, while code under areas such as enterprise/packages is covered by Novu's proprietary enterprise license. Self-hostability therefore should not be interpreted as meaning that every feature in the repository is MIT-licensed; teams should verify which licensing boundary applies to the features they plan to deploy.

Sources: [2][3][4]