Novu
Open-source notification infrastructure — one API to send in-app, email, SMS, push, and chat messages, plus connect your agents to the channels users live on
Novu is an open-source notification infrastructure: one API and one workflow engine to send messages across an in-app inbox, email, SMS, push, and chat, with an embeddable inbox component and a newer layer that connects AI agents to channels like Slack, Teams, and Telegram. It has 39,298 GitHub stars as of July 2026 and is built in TypeScript. For a founder it removes a real, repetitive chore — wiring a separate provider and webhook for every channel — so product and lifecycle messages ship from one place. But Novu delivers the message; it does not decide what to say, who should receive it, or bring you the users worth messaging in the first place. That upstream work — activation, retention, and the audience itself — is where growth actually happens.
What Novu is
Novu (github.com/novuhq/novu) is an open-source infrastructure for sending notifications. Instead of wiring up a separate provider and webhook for every channel, you send through one API and one workflow engine, and Novu fans the message out to an in-app inbox, email, SMS, push, and chat. It ships an embeddable inbox component for the in-app feed, a workflow engine with branching and conditions, and a digest engine that batches a flurry of events into a single message. A newer layer, which the project calls Agent Communication Infrastructure, connects an AI agent you have already built to channels like Slack, Microsoft Teams, Telegram, and WhatsApp through one conversation model. It is built in TypeScript, offers a hosted plan, and can be self-hosted from the repo.
- One API for every channel — an in-app inbox, email, SMS, push, and chat, instead of a separate SDK and webhook per provider.
- A workflow engine — branching, conditions, and delays so the right people get the right message on the right channel.
- An embeddable inbox — a real-time notification feed you can drop into your product with a prebuilt component.
- A digest engine — batch many events into one message so you don't flood a user's inbox.
- Open-source and self-hostable — the notification data and logic stay in your control.
- An agent-to-channel layer — connect an existing agent to Slack, Teams, Telegram, or WhatsApp without building a handler per platform.
Where Novu fits a founder's growth stack
Notifications are a growth lever, not just plumbing. The messages that drive activation and retention — a welcome nudge, a "your report is ready" ping, a re-engagement email when someone goes quiet — are exactly the touches that decide whether a new user comes back. Novu sits at the delivery layer: it owns which channel a message goes out on and how it is batched, so those touches ship reliably from one place instead of five half-built integrations.
This is a problem we know from the inside. In building AgentCeres — the AI Growth Officer at agentceres.com — we deliver our agents' messages over Slack, Telegram, Discord, and Feishu, and we built that per-channel plumbing ourselves: inbound webhooks, message normalization, and the per-platform formatting quirks. Novu productizes precisely that layer, and its agent-communication piece targets the same job of connecting an agent to the channels people actually use. Having paid the cost of building it by hand, we can say the value here is real — it is genuinely tedious work you don't want to reinvent.
What Novu doesn't do — and what to pair it with
Novu delivers the message; it does not write it, decide the strategy behind it, or bring you the users worth messaging. Sending infrastructure is only valuable once there is an audience to notify and something worth saying — and that upstream work is a different job entirely.
- Delivers the welcome and lifecycle messages — but you still need the signups that earn a welcome, and the lifecycle strategy that decides which message to send when.
- Fans a message out across channels — but the content and launches that fill the top of the funnel still have to be created.
- Owns the notification plumbing — but keeping users around after the ping is a retention job, not a delivery one.
This is where AgentCeres — the AI Growth Officer fits alongside a tool like Novu. AgentCeres is a managed AI marketing team: specialists draft the lifecycle messages, the content that grows your audience, and the launches that fill the funnel — and you approve every outbound send before it goes out. Novu makes sure the message arrives; the team helps you decide what to say and earns the audience to say it to. For how a related tool handles building the email itself, see React Email; for how AI answer engines factor into being found, see generative engine optimization.
FAQ
- Is Novu free?
- Novu is open-source, so you can self-host it for free, and it also offers a hosted cloud plan with a free tier plus paid tiers for higher volume and team features. Check the repo and novu.co for current limits.
- How is Novu different from an email tool like Resend or Mailchimp?
- Those tools focus on one channel — email — and the sending and list behind it. Novu is multi-channel notification infrastructure: it orchestrates an in-app inbox, email, SMS, push, and chat through one API and workflow engine, and can route a single event to whichever channel fits. Many teams use a dedicated email API to send and Novu to orchestrate across channels; the two are complementary, not either-or.
- Do I need Novu as a solo founder?
- Not on day one. If you send a couple of transactional emails, a single email API is simpler. Reach for Novu once you have more than one channel to coordinate — an in-app inbox plus email plus push — or once you are building an agent that needs to talk to users on Slack or Telegram. The bigger early bottleneck is usually the audience and the message, not the delivery layer.
You built it. Now grow it.
AgentCeres is a managed AI marketing team — specialists draft the SEO, social, and outreach that fill your links, you approve what ships. 14-day free trial, from $19/month.