# Novu

> Novu is an open-source notification infrastructure platform that orchestrates product messages across an in-app inbox, email, SMS, push, WhatsApp, Slack, Microsoft Teams, and Telegram through a single API and workflow engine, with a drop-in React Inbox component, digest and delay steps, user preference controls, bring-your-own delivery providers, and the option to self-host the entire stack or run it on Novu Cloud from $30 a month.

- Category: Marketing Automation (https://saastracker.org/categories/marketing-automation)
- Website: https://novu.co
- Starting price: $0 (Free or self-hosted), then $30 per month (Pro)
- Free plan: 10,000 workflow runs per month, up to 20 workflows, two environments, three team members, and 24 hours of activity feed retention, across every channel.
- Free trial: No time-limited trial; the free cloud plan and the open-source distribution both serve as evaluation paths
- Founded: 2021, HQ: Tel Aviv, Israel, Ownership: Venture-backed, open-source core
- Profile last reviewed: 2026-08-22
- Canonical profile: https://saastracker.org/products/novu

## Overview

Novu started as a genuinely popular open-source project before it was a company. The repository accumulated tens of thousands of GitHub stars on the strength of a simple proposition: every product needs notifications, every team builds the same digest, preference, and multi-channel routing logic, and none of that should be proprietary. The company raised a $6.6M seed in May 2022 led by Crane Venture Partners with Eniac, MXV Capital, and Entree Capital participating, and operates from Tel Aviv with a small team.

The product is now two things. Novu Notify is the notification infrastructure: workflows that route across channels with conditions, delays, fallbacks, and digests, plus the Inbox component that drops a real-time notification centre into a React app in a few lines. Novu Connect is newer and more speculative, a two-way channel for AI agents to hold conversations with customers over WhatsApp and Slack, which reflects where the company thinks product communication is going.

What makes Novu structurally different from Knock and Courier is the licence. The core is open source and can be self-hosted, which changes the calculus for three kinds of buyer: companies with data residency or sovereignty requirements that a US-hosted SaaS cannot meet, companies embedding notifications into their own product where per-message vendor pricing would be a margin problem, and companies that simply refuse to put a critical path dependency on a startup they cannot fork. The trade is that self-hosting a notification service means running MongoDB, Redis, and several services yourself, forever.

The commercial pricing is metered by workflow runs, not messages, which is a meaningfully different unit. A workflow run that fans out to three channels is one run. Free covers 10,000 runs a month with up to 20 workflows, two environments, three team members, and 24 hours of activity feed retention. Pro starts at $30 for 30,000 runs, Team at $250 for 250,000, both with $1.20 per additional thousand runs. That $30 entry point is the cheapest paid step in the developer notification tools by a wide margin.

## How it works

1. You define a workflow, either in the Novu dashboard or as code in your own repository. A workflow describes what happens when a named event occurs: which channel steps run, in what order, with which delays, digested over what window, and gated by which conditions. Defining workflows in code means they live in version control alongside the application that triggers them.

2. You connect delivery providers with your own credentials. Novu integrates with the usual set for email, SMS, push, and chat, so messages go out through your SendGrid, Postmark, Twilio, Firebase, or Slack account and you keep whatever rates and reputation you already have. The in-app channel is the exception: Novu provides that itself.

3. Your application triggers a workflow through the API or an SDK, passing a subscriber and a payload. Novu resolves the subscriber's preferences, applies quiet hours and snooze state, digests where configured, and delivers across the resolved channels with fallbacks when a channel fails.

4. For the in-app surface you drop the React Inbox component into your application. It renders a real-time notification centre with read state, preference controls, snooze, and quiet hours, all backed by the same workflow engine. If you would rather run everything yourself, the same stack deploys to your own infrastructure from the open-source repository, or to a private cloud on an enterprise arrangement.

## Best for

Engineering teams who want notification infrastructure they can read, fork, and self-host if they need to, and small companies who want a real paid plan at $30 a month rather than a $250 floor.

## Not the right fit for

- Marketing teams; there is no campaign calendar, no contact upload, no broadcast list management, and nothing sends until an application calls the API.
- Teams without engineering capacity to run infrastructure, if self-hosting is the reason you chose Novu; the open-source deployment involves MongoDB, Redis, and multiple services, and the operational cost is real and permanent.
- Ecommerce brands; no catalog, no cart recovery, no revenue attribution, and none of the promotional tooling that category requires.
- Buyers who want a large vendor behind a critical path system; Novu has raised $7M and has a small team, which is exactly why the open-source escape hatch matters.
- Anyone expecting delivery to be included; you bring and pay for your own email, SMS, and push providers on top of the Novu bill.

## Features

### Workflow engine

The orchestration core, available in the open-source distribution as well as the cloud.

- **Multi-channel workflows**: One workflow routes across in-app, email, SMS, push, WhatsApp, Slack, Microsoft Teams, and Telegram, handling conditions, delays, and fallbacks from a single definition.
- **Digest steps**: Bundle multiple notifications into one instead of five, over a window you define. This is the feature teams most consistently build badly themselves and a primary reason people adopt Novu.
- **Delay and wait steps**: Time-based pauses so a reminder can wait and then check whether the user already acted before firing.
- **Conditional routing and fallbacks**: Branch on subscriber attributes or payload data, and fall through from one channel to the next when delivery fails or the user has opted out.
- **Workflows as code**: Define workflows in your own repository so notification logic is reviewed, versioned, and deployed like the rest of your application.
- **Environments**: Separate development and production environments, with two included on the free plan so you can test without sending to real users.

### In-app Inbox

The drop-in notification centre that most teams arrive for.

- **React Inbox component**: An `<Inbox />` component that renders a full real-time notification centre in a few lines, with read and seen state, archiving, and styling hooks.
- **Built-in preference controls**: Users manage channel and category preferences directly from the inbox, backed by the same preference model the workflow engine respects.
- **Snooze and quiet hours**: Per-user controls on when notifications may arrive, which is unusually thoughtful for an open-source project and closes a common support complaint.
- **Headless mode**: For teams who want their own UI entirely, the inbox data is available headlessly so the component's design opinions are optional.

### Providers and channels

Bring your own delivery, keep your own reputation.

- **Bring-your-own email and SMS providers**: Connect SendGrid, Postmark, Twilio, and the rest with your own credentials so you keep existing contracts, rates, and sending reputation.
- **Chat channels**: Slack, Microsoft Teams, and Telegram are first-class delivery channels rather than webhook workarounds.
- **WhatsApp**: Supported as a channel, which is unusual among the developer notification tools and matters for consumer products outside North America.
- **Push notifications**: Mobile push through APNs and Firebase, configured with your own credentials.

### Deployment and control

The reason to choose Novu over its closed competitors.

- **Open-source core**: The notification infrastructure is open source and readable, so you can audit it, extend it, or fork it if the company disappears.
- **Self-hosting**: Deploy the full stack on your own infrastructure with Docker or Kubernetes. There is no per-message vendor fee, but you own MongoDB, Redis, and the services around them permanently.
- **Private cloud deployment**: A managed but isolated deployment option for enterprises who want vendor operations without shared infrastructure.
- **Compliance certifications**: SOC 2 Type II, ISO 27001, GDPR, and HIPAA support on the cloud offering, which is a stronger posture than most open-source-first projects reach.

### Developer experience and AI

How the integration lands and where the product is heading.

- **CLI quickstart**: `npx novu connect` scaffolds an integration in minutes, which is why the project spreads through developer communities rather than through sales.
- **Server and client SDKs**: SDKs across common backend languages plus front-end packages for the Inbox, with framework support including the Vercel AI SDK.
- **Novu Connect**: Two-way AI agent conversations over WhatsApp, Slack, and other platforms, so an agent can initiate a conversation with a customer and receive replies rather than only pushing messages out.
- **Activity feed and debugging**: Per-notification execution history showing which steps ran and why, retained for 24 hours on the free plan and longer on paid tiers.

## Use cases

- **Startup that needs an in-app notification centre this week**: The roadmap has a notification feed on it, the estimate is three weeks, and nobody wants to spend three weeks on it. Outcome: The React Inbox component ships a real-time feed with read state and preference controls in an afternoon, and the free plan's 10,000 workflow runs covers early usage at no cost.
- **European company with data residency requirements**: Legal will not approve a US-hosted notification vendor holding customer contact data and message content. Outcome: Novu self-hosts on infrastructure the company already controls in the region it needs, with no per-message vendor fee and full auditability of the code handling the data.
- **SaaS product embedding notifications for its own customers**: Notifications are part of the product being sold, so a per-message vendor fee is a direct hit to gross margin at scale. Outcome: The open-source deployment removes the marginal vendor cost entirely, leaving only infrastructure, which for an embedded use case is usually the difference between viable and not.
- **Team priced out of a $250 floor**: Volume is above the free tier but the budget will not carry a quarter-thousand-dollar monthly platform fee for notification routing. Outcome: Pro at $30 a month for 30,000 workflow runs fills the gap that Knock's plan structure leaves open, with $1.20 per additional thousand runs after.

## Pricing

Usage-based on workflow runs (one run per triggered workflow regardless of how many channels it fans out to), with a free tier, two published paid tiers, quoted enterprise pricing, and a free open-source self-hosted option.

- **Free**: $0 per month. 10,000 workflow runs per month; Up to 20 workflows and 2 environments; Up to 3 team members; All channels including in-app, email, SMS, push, and chat; 24-hour activity feed retention. The workflow and team-member caps bite before the run count does for most teams.
- **Pro**: From $30 per month. 30,000 workflow runs included; $1.20 per additional 1,000 runs; More workflows, environments, and team members; Longer activity feed retention; All channels included. The cheapest real paid plan among the developer notification tools, and the reason Novu wins small-team evaluations against Knock.
- **Team**: From $250 per month. 250,000 workflow runs included; $1.20 per additional 1,000 runs; Higher limits across workflows, environments, and seats; Extended retention and support.
- **Enterprise**: Custom annual contract. 10M+ workflow runs with custom volume tiers; Self-hosted deployment with dedicated support; Private cloud deployment; SOC 2 Type II, ISO 27001, GDPR, and HIPAA support; Enterprise SLAs.

Add-ons:

- Additional workflow runs ($1.20 per 1,000): Applies on Pro and Team after the included allowance.
- Self-hosted deployment support (Quoted): The open-source distribution is free; paid support for self-hosted deployments is an enterprise arrangement.

Billing notes:

- The meter is workflow runs, not messages. A single run fanning out to in-app, email, and SMS counts once, which makes Novu materially cheaper than per-message competitors for multi-channel notifications.
- You pay your own delivery providers separately, so the Novu bill is orchestration only.
- Self-hosting removes the vendor fee entirely and replaces it with infrastructure and operations cost: MongoDB, Redis, and several services, plus somebody's time to keep them running.
- Modelled at 5,000 users receiving two notifications a month, that is 10,000 workflow runs, which the free plan covers outright. The likelier constraint at that size is the 20-workflow or 3-seat cap.
- Modelled at 50,000 users receiving two notifications a month, that is 100,000 workflow runs: Pro's 30,000 plus 70,000 overage at $1.20 per thousand, roughly $114 a month, or Team at $250 with headroom.
- The step from Pro to Team is a genuine ramp rather than a cliff, because overage pricing is identical on both, so you can stay on Pro and overrun rather than being forced up a tier.

Value assessment: Novu is the best-value paid plan in the developer notification category and the only one with a self-hosting escape hatch. Pro at $30 for 30,000 workflow runs is an order of magnitude cheaper than Knock's $250 floor, and the workflow-run meter is more forgiving than a per-message meter the moment you send to more than one channel. At 100,000 runs a month you are paying around $114 against Courier's $500 for a comparable message count. What you give up is maturity: the enterprise controls, multi-tenancy depth, and operational polish of Knock are ahead, the company is small, and self-hosting is only free if your engineers' time is worthless. For teams weighing cost against maturity, Novu is the value pick and Knock is the safe pick.

## Strengths

- Genuinely open source with a self-hostable core, which is the only real answer in this batch to data sovereignty, embedding, and vendor risk concerns.
- Pro at $30 a month is the cheapest meaningful paid tier among developer notification tools and fills the gap Knock's plan structure leaves wide open.
- The workflow-run meter is cheaper than per-message billing for any notification that fans out to more than one channel.
- The React Inbox component ships a real-time notification centre with preferences, snooze, and quiet hours in an afternoon, with a headless option for teams that want their own UI.
- Broad channel coverage including WhatsApp, Slack, Microsoft Teams, and Telegram, which is wider than most competitors at any price.
- Stronger compliance posture than most open-source-first projects: SOC 2 Type II, ISO 27001, GDPR, and HIPAA support on the cloud offering.
- Community-driven development with a public repository, so bugs, roadmap, and quality are inspectable before you commit.

## Limitations

- Self-hosting is free in licence terms only; running MongoDB, Redis, and the surrounding services is a permanent operational cost that small teams routinely underestimate.
- The free plan's 20-workflow, 2-environment, and 3-seat caps constrain growing teams before the run count does.
- Multi-tenancy, per-customer branding, and enterprise access controls are less developed than Knock's, which matters for B2B products with tenant-specific configuration.
- Small company on $7M raised holding a critical path position, mitigated but not eliminated by the open-source licence.
- No marketing capability whatsoever: no campaigns, no contact lists, no attribution, no A/B testing of the kind a growth team expects.
- Delivery and deliverability are entirely yours, including domain authentication, bounce handling, and reputation management.

## Comparisons

- **Novu vs Knock**: The same category, opposite trade-offs. Knock is closed, more mature, deeper on multi-tenancy and environments, and starts at $250 a month above its free tier. Novu is open source, self-hostable, and starts at $30. A funded B2B SaaS company putting notifications on the critical path should probably pay for Knock; a cost-sensitive team, a company with data residency requirements, or anyone embedding notifications into their own product should take Novu.
- **Novu vs Courier**: Courier bills per send at $0.005 with 10,000 free, has a stronger visual template designer for non-developers, and integrates with more than fifty providers. Novu bills per workflow run, which is cheaper for multi-channel notifications, and can be self-hosted. Choose Courier for the design surface and provider breadth; choose Novu for the licence, the WhatsApp and Telegram channels, and a lower bill at comparable volume.
- **Novu vs Dittofeed**: Both are open source with self-hosting and bring-your-own-ESP, but they solve different halves of the problem. Dittofeed is marketing automation: journeys, segments, and lifecycle campaigns, cloud from $75 a month. Novu is product notification infrastructure: inbox, digests, preferences, and routing. A team wanting onboarding email sequences takes Dittofeed; a team wanting an in-app feed and digest logic takes Novu. Companies that need both often run both, since neither pretends to cover the other.
- **Novu vs OneSignal**: OneSignal includes delivery, gives away unlimited mobile push, and is operable by a growth team once the SDK is installed. Novu delivers nothing itself and is unusable without engineering. If the goal is reaching consumers with push campaigns, OneSignal is cheaper and better shaped. If the goal is orchestrating product notifications with digests and preferences on infrastructure you can self-host, Novu is the only one of the two that qualifies.
- **Novu vs Customer.io**: Customer.io is a complete marketing automation platform with its own delivery, a CDP, real-time behavioral segmentation, and campaign tooling, from a $100 monthly floor billed on profile count. Novu is infrastructure with no campaigns and no sending. Marketing-led companies should buy Customer.io. Product-led companies whose notification problem is routing, fatigue, and an in-app feed should buy Novu and spend the difference on the delivery providers underneath.

## Implementation

- Setup time: An afternoon for a cloud integration with the Inbox component. Self-hosting is a different project: a day or two to a working Docker deployment and considerably longer to something a team would trust in production, with MongoDB and Redis to operate afterwards.
- Learning curve: Low for engineers. Subscribers, workflows, steps, and providers are clean concepts and the CLI quickstart gets a first notification flowing in minutes. Workflows as code is the part teams take longest to adopt, because it changes who owns a message change.
- Onboarding: Self-serve on Free, Pro, and Team, backed by documentation and a public community. Enterprise adds dedicated support, including for self-hosted deployments. Community help through the repository and Discord is fast and genuine.
- Migration: Because you keep your existing delivery providers, migration touches routing and templates only and carries no deliverability risk. Existing user preference and opt-out state must be loaded into Novu's subscriber preferences before cutover. The open-source licence also makes the reverse migration honest: if you leave Novu Cloud, you can self-host the same stack rather than being locked out.

## Platform, API & security

- Platforms: Web dashboard, REST API, CLI, React Inbox component, Self-hosted via Docker or Kubernetes, Private cloud deployment
- API: REST API with server SDKs across common backend languages, front-end packages for the Inbox, a CLI for workflows as code, and framework support including the Vercel AI SDK.
- Compliance: SOC 2 Type II, ISO 27001, GDPR, HIPAA support
- Data residency: Cloud is US-hosted by default; self-hosting or private cloud deployment is the answer for specific regional requirements.
- SSO: Available on higher tiers and enterprise arrangements; the free plan is limited to three team members regardless.
- Security notes: The open-source core means the code handling your customer contact data is auditable, which is a meaningful security property rather than a marketing line. Cloud carries SOC 2 Type II and ISO 27001. Self-hosted deployments inherit whatever security posture your own infrastructure has, for better or worse.

## Support

- Channels: Community Discord, GitHub issues, Email support on paid plans, Dedicated support on Enterprise, including for self-hosted deployments
- Documentation: Documentation at docs.novu.co covering workflows, channels, the Inbox component, providers, self-hosting, and the CLI.
- Community: Large and active open-source community around the GitHub repository and Discord, which is genuinely the fastest support channel for most questions.

## Company

- Founded: 2021
- Headquarters: Tel Aviv, Israel
- Ownership: Venture-backed, open-source core
- Employees: Small team; not formally disclosed
- Funding: $6.6M seed raised in May 2022 led by Crane Venture Partners.

Funding history:

- Seed (2022): $6.6M. Led by Crane Venture Partners with Eniac Ventures, MXV Capital, Entree Capital, Ariel Maislos, and a number of angel investors participating.

Timeline:

- 2021: Started as an open-source notification infrastructure project, accumulating a large GitHub following before any commercial offering existed.
- 2022: Raises a $6.6M seed round led by Crane Venture Partners to build open-source notification infrastructure for developers.
- 2023: Launches Novu Cloud as the managed offering alongside the self-hostable open-source distribution.
- 2024: Ships the React Inbox component with built-in preference controls, snooze, and quiet hours, which becomes the most common entry point for new users.
- 2025: Adds SOC 2 Type II and ISO 27001 certification to the cloud offering, alongside private cloud deployment for enterprises.
- 2026: Introduces Novu Connect for two-way AI agent conversations over WhatsApp and Slack, extending the platform from outbound notification to bidirectional messaging.

## Integrations

SendGrid, Postmark, Mailgun, Amazon SES, Resend, and other email providers, Twilio and other SMS providers, Apple Push Notification service and Firebase Cloud Messaging, Slack, Microsoft Teams, Telegram, WhatsApp, Vercel AI SDK, Webhooks and custom provider integrations, Docker and Kubernetes for self-hosted deployment

## FAQ

### What is Novu?

Novu is open-source notification infrastructure. It orchestrates product notifications across an in-app inbox, email, SMS, push, WhatsApp, Slack, Microsoft Teams, and Telegram through one API and workflow engine, with digest and delay steps, user preferences, and a drop-in React Inbox component. You can run it on Novu Cloud from $30 a month or self-host the whole stack yourself.

### How much does Novu cost?

The free cloud plan covers 10,000 workflow runs a month with up to 20 workflows, two environments, and three team members. Pro starts at $30 a month for 30,000 runs, Team at $250 for 250,000, both charging $1.20 per additional thousand runs. Enterprise is quoted. Self-hosting the open-source distribution has no licence fee at all, only infrastructure cost.

### What is a workflow run and why does the meter matter?

A workflow run is one triggered workflow, regardless of how many channels it fans out to. If a single trigger sends an in-app notification, an email, and an SMS, that is one run rather than three messages. That makes Novu meaningfully cheaper than per-message competitors like Courier for any multi-channel notification, which is most of them.

### What does self-hosting Novu actually cost?

Nothing in licence fees and a fair amount in operations. The stack involves MongoDB, Redis, and several services, deployed through Docker or Kubernetes, and somebody has to own upgrades, backups, monitoring, and scaling permanently. For a team already running that class of infrastructure the marginal cost is modest; for a five-person startup without a platform engineer, paying $30 a month for the cloud is almost always the cheaper decision once you price the time honestly.

### Do I bring my own email and SMS provider?

Yes, for every channel except the in-app inbox, which Novu provides itself. You connect SendGrid, Postmark, Twilio, Firebase, Slack, or others with your own credentials, keeping your existing rates and sending reputation, and you pay those providers separately from the Novu bill.

### Who is responsible for deliverability with Novu?

You are. Domain authentication, SPF and DKIM records, bounce handling, list hygiene, and inbox reputation belong to you and your email provider. Novu composes and routes; it does not send. This is the standard arrangement for bring-your-own-provider infrastructure and the opposite of platforms like Ortto or Drip that run the sending themselves and share the problem.

### Is Novu event-driven or list-driven?

Entirely event-driven. There is no contact list to upload and no campaign scheduled against a static audience. Workflows fire when your application triggers them with a subscriber and a payload. This makes Novu unusable by a marketer working alone and very capable at things list tools cannot do, such as digesting a burst of activity into one message.

### Can a non-developer edit Novu notifications?

Partly. Templates, workflow steps, and timing can be edited in the dashboard once an engineer has wired the triggers, so a product manager can change copy and digest windows without a deploy. But Novu's design surface is less developed than Courier's visual template designer, and teams that define workflows as code deliberately move that editing back into the repository.

### Is Novu safe to depend on given the company's size?

This is exactly what the open-source licence is for. Novu has raised $6.6M and runs a small team from Tel Aviv, which is a real concentration risk for anything on your critical path. Because the core is open source and self-hostable, the worst case is that you take over running the software you were already using rather than rewriting your notification layer under time pressure. That escape hatch is a legitimate part of the buying case.

### How does Novu compare to Knock?

They target the same problem with opposite priorities. Knock is closed source, more mature on multi-tenancy, environments, and enterprise controls, and costs $250 a month above its free tier. Novu is open source, self-hostable, cheaper at $30, and broader on channels including WhatsApp and Telegram. Funded B2B SaaS companies with tenant complexity usually land on Knock; cost-sensitive teams, sovereignty-constrained buyers, and companies embedding notifications in their own product usually land on Novu.

## Editorial verdict

Novu is the value and control pick in developer notification infrastructure. Pro at $30 a month for 30,000 workflow runs undercuts every closed competitor by an order of magnitude, the workflow-run meter is more forgiving than per-message billing the moment a notification touches two channels, and the React Inbox component delivers the thing most teams actually came for in an afternoon. The open-source licence is not decoration: it is the only credible answer in this batch to data sovereignty requirements, to embedding notifications into a product you sell, and to the reasonable worry about putting critical path infrastructure on a company that has raised $7M. The costs are honest ones. Self-hosting is free only if your engineers' time is, multi-tenancy and enterprise controls trail Knock, and there is no marketing surface at all. For a five-person startup that needs an in-app notification feed and digests without a $250 monthly floor, Novu Cloud is the sensible first purchase in this batch, and the ability to self-host later is worth having even if you never use it.

---

Source: SaaSTracker (https://saastracker.org), an independent editorial project. This profile is compiled from public information, carries no peer reviews or paid placement, and was last reviewed 2026-08-22. Awards are judged on published criteria: https://saastracker.org/methodology