Is Novu Open-Source and What Are Its Pricing Options?

Updated

Novu is an open-source notification and agent communication infrastructure, and it publishes a pricing page at novu.co/pricing for its paid plans. That combination means you can evaluate the open-source project and a commercial offering side by side before adopting. The right choice depends on whether you need to self-manage the infrastructure or want a hosted service, and on which channels and features your product requires.

What Novu actually is

Novu describes itself as "the open-source notification and agent communication infrastructure." Its stated purpose is to connect AI agents and products to customers across many channels through one API. The site reports 1.5 billion messages sent in the last month, which is a scale signal rather than a guarantee for your workload.

The platform splits into two communication modes:

  • Novu Notify — one-way notifications to users through in-app, email, and push.
  • Novu Connect — two-way AI communication across WhatsApp, Slack, and other channels.

The channels named on the site include Inbox, Slack, Microsoft Teams, WhatsApp Business, Telegram, Email, iMessage, Push, Chat, SMS, Discord, Linear, Zoom, and Google Chat.

Open-source: what that means in practice

"Open-source" here refers to the notification and agent communication infrastructure itself. The practical implication is that you can inspect and run the project rather than being locked into a closed hosted product. The site's own framing — "Opinionated about communication. Unopinionated about intelligence" — signals that Novu handles the delivery and conversation layer while leaving your AI or logic choices to you.

What the available material does not specify: the exact license, which features are gated behind paid plans, and whether self-hosting is fully supported for every channel. Those are the details to confirm on the pricing page and in the docs before committing.

Pricing: what is confirmed and what is not

The site links to a pricing page, which confirms that paid plans exist. It does not publish prices, tiers, or a free-forever plan in the material available here. Do not assume the open-source project is free to operate at scale, and do not assume a free tier exists — check novu.co/pricing directly.

Question What the site confirms What to verify yourself
Is there a paid plan? Yes, a pricing page exists Actual price, tiers, and limits
Is it open-source? Yes, described as open-source infrastructure License terms and self-host scope
Is there a free tier? Not stated Check pricing page
Which channels cost extra? Not stated Check pricing page and docs

Getting started

The site gives a concrete entry point: npx novu connect. That command is the starting action for connecting your agents and products. From there, the documented flow is:

  1. Run the connect command to initialize.
  2. Add the Inbox component to your product — the site shows a React example using @novu/react with an <Inbox /> component, and names Next.js, Remix, and React as supported frameworks.
  3. Configure the channels you need (in-app, email, SMS, push, WhatsApp, Slack, Microsoft Teams, Telegram, and others).
  4. Send a notification and verify it arrives in the target channel.

The expected result after step 2 is a working in-app inbox with real-time notifications, unread counts, built-in preferences, tabs, filters, custom styling, localization, and snoozing — all features the site lists for the Inbox.

Choosing between open-source and paid

Use this as a decision frame rather than a recommendation:

  • Lean open-source if you want to control the infrastructure, have engineering capacity to run and maintain it, and your channel needs match what the project supports.
  • Lean paid if you want a hosted service, need channels or features that are gated, or want to avoid operating the delivery layer yourself.
  • Start with the connect command either way — it is the documented first step and lets you test the integration before deciding on a plan.

The site's own positioning — "Add an [inbox] to your product by end of day" — suggests the integration is meant to be fast, which makes a trial run low-risk regardless of which path you eventually pick.

Common sticking points

  • Assuming open-source means free at scale. The pricing page exists for a reason; confirm what triggers paid usage.
  • Skipping the channel audit. Novu lists many channels, but your product may only need two or three. Match channels to actual user behavior before configuring everything.
  • Treating Notify and Connect as the same thing. Notify is one-way; Connect is two-way. If you need agents to hold conversations, you need Connect.
  • Not checking framework support. The site names Next.js, Remix, and React for the Inbox component. Verify your stack before starting.

The fastest way to resolve the open-source-versus-paid question is to run npx novu connect, test the channels you care about, and then read novu.co/pricing with your actual usage in mind.