Courier vs Novu: 2026 notification platform comparison

Last updated: September 2026

Short answer

Courier vs Novu comes down to hosting: Courier is the better managed platform, and only Novu can run inside your own network. Courier is fully managed and covers an enterprise SLA, EU data residency, failover across 50+ delivery providers, and one platform for engineers and marketers. Novu ships a self-hostable core, MIT at the core with a commercially licensed enterprise folder, and Courier is managed only.

• Pricing units differ, and it matters. Courier bills $0.005 per send on any channel (courier.com/pricing). Novu bills per workflow run, where one run covers every channel step for one subscriber (novu.co/pricing). On the meter alone, Novu Cloud is usually cheaper.
• Novu is Open Core, not plain MIT. The core is MIT; the enterprise folder is commercially licensed (github.com/novuhq/novu).
• Failover is a real gap. Novu's docs state it "does not automatically fall back to another provider if that send fails" (docs.novu.co). Courier fails over across providers without a code change.

How we compared

We read each vendor's own pricing page, docs, and public repository in September 2026. We scored four things: delivery and architecture, 35; pricing at high volume, 25; orchestration and testing, 20; in-app and preferences, 20. Every Novu number below links to Novu's own page so you can check it. Where Novu's docs did not confirm something, we left it out rather than mark it as missing. The previous version of this page carried cross marks for event throttling and scheduling. Novu documents a Throttle step and a Digest step, so those were wrong and are gone.

Courier vs Novu at a glance

Where Novu wins

You can host it yourself. This is the honest reason to choose Novu, and no amount of feature comparison changes it. Your compliance team may require that customer data never leaves your VPC. Your procurement process may require an escrow copy of the source. Courier cannot meet either requirement. Novu can, and the deployment guide is public.

The core is genuinely open. The MIT core has 39.7k stars on GitHub. You can read the queue logic, patch a provider adapter, and run a fork. If you have been burned by a vendor changing terms, that optionality has value that does not show up on a pricing page.

Novu Cloud's meter is usually cheaper. One workflow run covers every channel step for a single subscriber. Send an email, an SMS, and an in-app message off one event and Novu counts one run. Courier counts three sends. If your notifications fan out across three or four channels per event, Novu's model costs a fraction of Courier's.

It is a real product, not a side project. SOC 2 Type II, ISO 27001, GDPR, and HIPAA are all listed on novu.co. The same page names MongoDB, Check Point, Deriv, and Ebury as customers. Digest, Throttle, Delay, and HTTP action steps are documented, so the orchestration primitives you need are there.

Where Courier wins

Nobody has to pick between a developer platform and a marketer platform. Courier is one platform for both. Your engineers trigger sends from code. Your growth or success team builds onboarding, upgrade, and renewal flows in Journeys and edits content in Design Studio without filing a ticket. You are not buying developer infrastructure and then buying a second tool for the people who write the copy.

Everything in the UI is on the API. Journeys, templates, brands, routing, preferences, audiences, tenants, users, and translations are first-class API objects. The dashboard is a client of the same public API you get. A marketer clicks. An engineer manages the same object as code. An agent works through the MCP server. All three touch one source of truth. An agent can call an API. It cannot operate a canvas.

One send does not stop because one provider is down. Courier sits on top of 50+ providers, including Twilio, SendGrid, SES, FCM, and APNs, and fails over automatically. Novu's integration docs are explicit that it sends through one integration per channel step and will not fall back on failure. That responsibility stays with you.

You get the pieces you would otherwise build twice. Experiments run A/B tests with 2 to 10 variants at a send point inside a journey, with per-variant metrics. AI Translations translate a whole template and pick the right language for each recipient at send time. Courier Create is the embeddable designer you white-label into your own product, so your customers design their own messages. Preferences come as a hosted page, an embeddable component, or headless APIs, and Courier enforces them on every send.

Managed means managed. Enterprise adds an SLA, EU data residency, RBAC, a dedicated Slack channel, and observability integrations. The pricing page lists SOC 2 compliance and HIPAA certification. Nobody on your team carries a pager for the notification queue. Twilio, LaunchDarkly, CircleCI, and Nav run on it today.

Pricing

Courier (courier.com/pricing, September 2, 2026): Developer is free and covers 10,000 sends a month, with Journeys, Broadcasts, the MCP server, the CLI, and the SDKs included. On Business, every send costs $0.005, and the rate is identical on every channel. There is no volume cap and nothing to commit to up front. Business also adds AI Translations, the AI Agent node, and cross-device email testing. Enterprise is custom volume pricing.

Novu (novu.co/pricing, September 2026): Free is $0 with 10,000 workflow runs a month, 20 workflows, 2 environments, and up to 3 team members. Pro starts at $30/mo with 30,000+ runs and $1.20 per 1K in overage. Team starts at $250/mo with 250,000+ runs, 100 workflows, and up to 10 environments. Enterprise is custom, including on-prem or VPC deployment.

The unit is the whole story. Novu defines a workflow run as "one execution of a workflow." Novu also states that "triggering a workflow to a single subscriber counts as 1 run; triggering to a topic with 100 subscribers counts as 100 runs after fan-out." So channels are free inside a run, and subscribers are not.

How much does 150,000 events a month cost?

Say you send 150,000 events a month, each one going out as an email and an in-app message to a single subscriber. We assume Pro's $30 covers the first 30,000 runs and everything above that bills at $1.20 per 1K. Pro also caps you at 20 workflows and 2 environments, so more than that moves you to Team at $250.

• Novu Pro: 150,000 runs. 30,000 are included at $30, and the remaining 120,000 bill at $1.20 per 1K, so about $174 a month.
• Courier Business: 300,000 sends at $0.005, so $1,500 a month.

Novu Cloud is roughly nine times cheaper on that meter, and we are not going to pretend otherwise. What sits inside the Courier price changes the comparison: the SLA, EU residency, failover across 50+ providers, Design Studio, Experiments, AI Translations, and Courier Create. It also changes shape at the top end, where Courier moves to custom volume pricing. Where the run meter bites back is broadcast. A weekly digest to 200,000 subscribers is 200,000 runs every time you send it. The plan tiers also cap workflows and environments in ways a per-send price does not.

What does Novu's Open Core license actually cover?

Novu is Open Core, not plainly MIT, and the distinction shows up in procurement. The repository states that "the following modules and folders are licensed under the enterprise license: enterprise folder at the root of the project and all of its subfolders and modules" (github.com/novuhq/novu). Everything outside that folder is MIT. So you can self-host the core for free, and the enterprise code needs a commercial license from Novu.

What does self-hosting Novu actually take?

Free to license is not free to run. Novu's own self-hosting guide is direct about the shape of the deployment. You run an API server, a worker, a WebSocket server, and the dashboard. Behind them you need MongoDB, where an M20 or higher cluster tier is the recommendation on Atlas. You also need two separate Redis clusters, one dedicated to queues with Append Only File enabled so jobs survive an outage. Add at least 10 GB of object storage. The recommended layout is three VMs per service at 2 vCPUs and 4 GB each. Consolidating instead takes a single VM at 4 vCPUs and 8 GB.

Then add the parts you cannot buy with a credit card. Someone owns the upgrade path. Someone gets paged when the queue backs up at 2am and a password reset does not arrive. Someone tunes Redis when digest windows pile up.

The feature gap is the part most build-versus-buy spreadsheets miss. Novu documents that the self-hosted community edition does not include several things Novu Cloud has, specifically "Inbox features, email activity tracking, SSO, RBAC, and compliance certifications." Novu also documents that self-hosting "does not support social login." If you self-host to satisfy a compliance requirement, read that list twice. The compliance certifications live with the hosted product.

When to choose Novu

• Your data cannot leave your own network, and a managed vendor is not an option no matter how good the SLA is.
• You want the source code, either to fork it or to satisfy an escrow or audit requirement.
• Your notifications fan out across three or more channels per event, and the per-run meter saves you real money.

When to choose Courier

• You want engineers and marketers on one platform, with journeys and templates the marketing team owns and the API still controls.
• You need failover across providers, an enterprise SLA, and EU data residency without running MongoDB, Redis, and a queue yourself.
• You want an agent to build and edit journeys, templates, and preferences through an MCP server, not only trigger a send.

Related comparisons

• Courier vs Knock, the closest comparison to this one
• Courier vs Twilio, if you are also weighing Twilio
• Courier vs SendGrid, if email is where you are starting
• Courier vs OneSignal, if push is your main channel
• Courier vs Customer.io, if marketing sends are in scope too
• Best notification infrastructure software, the full ranked list

Start free with 10,000 sends a month at courier.com, or book a demo if you want to walk through journeys, failover, and EU data residency with us.