惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
C
Check Point Blog
B
Blog RSS Feed
G
Google Developers Blog
H
Help Net Security
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
H
Hackread – Cybersecurity News, Data Breaches, AI and More
量子位
Recent Announcements
Recent Announcements
B
Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
D
DataBreaches.Net
小众软件
小众软件
T
The Blog of Author Tim Ferriss
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
MongoDB | Blog
MongoDB | Blog
Y
Y Combinator Blog
T
Tailwind CSS Blog
J
Java Code Geeks
MyScale Blog
MyScale Blog
雷峰网
雷峰网
有赞技术团队
有赞技术团队
博客园 - 聂微东

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Novu Pricing Teardown 2026
Vlad Nadymov · 2026-05-27 · via DEV Community

TL;DR

Novu is open-source notification infrastructure — ~36k GitHub stars, MIT-licensed, unifying email, SMS, push, in-app, and chat behind a single API. Free covers 10k workflow runs/month but only 24-hour activity retention, which makes it a dev environment, not a production one.

  • Billing unit is "workflow runs," not messages — captures orchestration usage, not just delivery
  • Free at $0 covers 10k runs/month, 2 environments, 3 team members, 24-hour retention
  • Pro at $30/month is mostly a retention unlock (7 days), not a volume unlock
  • Team at $250/month adds RBAC, 10 environments, 90-day retention, unlimited members — a steep jump from Pro
  • MIT license means full self-hosting is on the table for teams that want to own the infra

This post is a part of series on commercial open source software pricing. See full list of articles here.

Novu is open-source notification infrastructure — a unified API for sending email, SMS, push notifications, in-app notifications, and chat messages from a single platform. ~36k GitHub stars. The problem it solves: every growing product eventually builds a notification system, then rebuilds it, then rebuilds it again. Novu is the "just use this" answer instead of duct-taping together SendGrid, Twilio, and a custom in-app notification table.

Plans

  • Free — $0: 10,000 workflow runs/month, all channels, 2 environments, 3 team members, 24-hour activity retention.
  • Pro — from $30/month: 30,000+ runs, 7-day retention, Novu branding removed.
  • Team — from $250/month: 250,000+ runs, 10 environments, unlimited team members, RBAC, 90-day retention.
  • Enterprise: Custom, 10M+ runs, unlimited environments.

"Workflow runs" as the billing unit

Most notification platforms bill per message sent. Novu bills per workflow run — a single trigger event that passes through your workflow logic (filter → decide channel → deliver → track delivery → handle failures).

This is actually a smarter billing metric. One "send a password reset email" notification might be a single workflow run. One "send a weekly digest" notification that evaluates 10,000 user preferences and sends 7,000 emails triggers 10,000 workflow runs.

The billing unit captures your usage of the orchestration layer, not just the delivery. If your workflows are simple (trigger → send), workflow runs ≈ messages sent. If your workflows are complex (trigger → evaluate → branch → retry → track), the multiplier grows.

For most use cases, this is more predictable than per-message billing because you control the complexity of your workflows. But it means you need to actually think about how Novu counts runs before you estimate costs.

24-hour retention on free is essentially non-functional for production

The free tier's 24-hour activity log retention is the single biggest friction point. If something breaks in production on a Friday night, you have until Saturday night to debug it. Your notification that failed on Thursday? Gone.

This isn't accidental. It's the conversion mechanic. Retention is cheap to provide (it's disk space), but it's psychologically painful to lose. The moment you're shipping notifications to real users, 24-hour logs feel dangerously short. Pro's 7-day retention is the minimum viable retention for production ops.

The move from free to Pro ($30/month) is primarily a retention unlock, not a volume unlock. 10k vs 30k runs is fine for most small apps; losing your logs after 24 hours is not.

The 3-member cap on free

Free tier caps at 3 team members. If you have a 4-person team, you're at Pro. It's a soft lock — the retention issue would probably push you there anyway, but the member cap ensures you can't linger on free as you grow.

Team at $250/month is a big jump from Pro ($30/month). The delta buys you RBAC, 10 environments (instead of 2), 90-day retention, and unlimited members. For a SaaS company where engineering + growth + ops all touch notification workflows, RBAC and multiple environments are legitimate needs. But the pricing cliff is steep.

The multi-channel value proposition

Novu's real pitch isn't any single channel — it's the unified API across all channels. If you're already using SendGrid for email and Twilio for SMS, you have two billing relationships, two integration points, two places for things to break. Novu wraps all of that in one abstraction layer.

The catch: Novu doesn't provide the actual sending infrastructure. You still need SendGrid or Postmark for email delivery, Twilio for SMS. Novu is the orchestration layer, not the delivery layer. For teams that don't realize this upfront, the architecture can feel like more complexity, not less.

License

MIT. Full self-hosting capability, no license restrictions for commercial use. For teams that want full ownership of their notification infrastructure (common in fintech, healthcare), self-hosted Novu is a real option.

Worth paying for?

Pro at $30/month is worth it the moment you're in production — purely for the retention upgrade. Free tier's 24-hour logs make it a development environment, not a production one. The unified multi-channel orchestration is genuine value if you're managing more than one notification channel. Team tier at $250 is a significant step; justify it when you actually hit the team size or environment limits.


How Novu pricing scales

Novu's Free tier covers 10k runs; Pro ($30) is mostly a retention unlock, and Team ($250) is a steep jump for RBAC and longer retention.

Novu pricing by tier. The Pro→Team jump is steep for what's mostly RBAC + retention.
Novu pricing by tier. The Pro→Team jump is steep for what's mostly RBAC + retention.

This post is a part of series on commercial open source software pricing. See full list of articles here.

I build Beton — open source revenue intelligence for B2B SaaS.

FAQ

Is Novu open source?

Yes, MIT-licensed. The full product is on GitHub at github.com/novuhq/novu with no license restrictions for commercial use, so self-hosting is a real option for teams in fintech or healthcare that need full ownership.

What does Novu charge for and how is usage measured?

Novu bills per workflow run, not per message sent. A single trigger event passing through your workflow logic counts as one run, regardless of how many channels it fans out to.

What's the cheapest paid Novu plan?

Pro starts at $30/month. It bumps you to 30,000+ workflow runs, extends retention to 7 days, and removes Novu branding.

Why is the free tier not usable in production?

Activity log retention is capped at 24 hours. If a notification fails on Thursday, the logs are gone by Friday — there's no way to debug production incidents past a one-day window.

Does Novu replace SendGrid and Twilio?

No. Novu is the orchestration layer, not the delivery layer. You still need SendGrid or Postmark for email and Twilio for SMS; Novu sits on top and gives you a unified API across them.