# Novu vs BuildBase, and the workflow run that means two things

> Novu bills workflow runs at $1.20 per 1,000. So do we, at $0.10 to $0.25. The gap looks decisive, but the two products do not mean the same thing by a run, and that is the comparison.

- Source: https://www.buildbase.app/compare/novu-vs-buildbase
- Section: Comparisons
- Author: Dharmendra Jagodana
- Published: 2026-11-13

## In short

Novu is open-source notification infrastructure: Inbox, email, SMS, push and chat behind one workflow, billed per workflow run. BuildBase bills workflow runs too, at a fifth of the rate, but ours execute automations while theirs sit on the notification path. Novu reaches more channels. Our meter counts less.

Both products print the same words on the invoice. Novu bills a workflow run.
So do we. Theirs costs $1.20 per 1,000 past the allowance and ours costs
between $0.10 and $0.25, which looks like the sort of gap that ends a
comparison in the first paragraph.

It does not, and the reason is worth more than the number. A run is not the
same amount of work on the two platforms, so the rates are not actually
comparable. What is comparable is what each meter is attached to, and that is
a real difference you can decide on.

## The one-paragraph answer

Pick Novu if notifications are a surface your users judge you on and you need
to reach them across channels: an in-app Inbox you drop into React, mobile
push, text messages, WhatsApp, Slack, Teams and Discord. That is
their entire product and they are good at it, and it is open source if you
would rather run it yourself. Pick BuildBase if your notifications are email,
web push and Slack alerts, and they are one piece of a backend you still have
to build anyway. Novu reaches further. Our meter counts less.

## What each one actually is

Novu is open-source communication infrastructure. You write one workflow and
it handles routing, conditions, delays, digests and fallbacks across every
channel you have configured, with a per-user preference set covering quiet
hours and snoozing. Its best-known piece is the Inbox: a prebuilt React
component you add with `` from `@novu/react`, with unread counts,
tabs, filters and preferences already built. The project is open core and
self-hostable alongside the managed cloud.

BuildBase is a backend sold as an SDK, and notifications are a few of its 20
modules rather than the product. Email runs through Mailgun, Google, Amazon
SES or your own SMTP, with templates, tracking, unsubscribe groups and
preference centers. Web push generates VAPID keys per organization on the
first subscribe, so there is no push service for you to set up. Slack alerts
are real-time Block Kit messages that link back to the console record. The
workflow builder wires all of it together with more than 100 triggers and 19
actions.

So Novu is a layer you add to a product. BuildBase is the thing underneath
that had to solve auth, billing and workspaces before notifications were worth
having.

## What each one costs

Novu's figures below were read from novu.co/pricing on 13 November 2026. Ours
are the published plans, last verified against the production API on 31
October 2026, so check the live pricing page before you lean on them.

Workflow runs are the only line on Novu's price list. Free is $0 with 10,000 runs a
month, 5 workflows, 2 environments, up to 3 team members and a 24-hour
activity feed. Pro starts at $30 a month for 30,000 runs or more, with 20
workflows and 7-day retention. Team starts at $250 a month for 250,000 runs or
more, with 100 workflows, up to 10 environments and 90-day retention. Both
paid tiers charge $1.20 per 1,000 runs past the allowance. Enterprise is
negotiated, starts at 10 million runs, and is where SAML, SCIM, a HIPAA BAA
and self-hosted deployment live.

Those tiers say "starting from" for a reason: the price scales with the volume
you commit to. Divide either entry point and you get the same figure, about
$1.00 per 1,000 runs, with marginal runs at $1.20. Novu is a one-dial product
and the dial is honest.

BuildBase plans are Free at $0, Launch at $19, Grow at $49 and Scale at $99 a
month, with yearly billed as ten months for twelve. Workflow runs included:
1,000 on Free, then 100,000, 500,000 and 2,000,000. Past those it is $0.25,
$0.15 and $0.10 per 1,000 on Launch, Grow and Scale. Effectively that is $0.05
to $0.19 per 1,000 included.

> **Key takeaway:** Only three things bill over their allowance on BuildBase: workflow runs, web
> analytics events and storage. Email and web push are hard allowances that stop
> rather than charge, so a notification cannot produce a surprise invoice here.
> It can produce a ceiling.

## What a run actually buys

Here is the part that decides it, and it is not the rate.

A Novu workflow run is one execution of a notification workflow. Their pricing
page never actually defines the term, which is worth knowing before you model
a bill on it: the FAQ asks "What is a workflow run?" and the answer is not
there. What is clear is where the meter sits. You trigger a workflow, and it
fans that one event out across its channel steps, to the Inbox, an email, a
push, a text message, a Slack post. Everything their product does runs through
a workflow, which is why one dial prices the whole thing.

A BuildBase workflow run is an automation. It executes a chain of steps from
the builder - tag a user, grant credits, call a webhook, wait two days, then
send something. Sending is one action among 19, and the mail and push it sends
are counted against their own allowances rather than against the run. Our
meter is attached to the automation engine, not to the outbound pipe.

So hold the count still. At 250,000 runs a month, Novu Team is $250, because
that is where the tier starts. The same
250,000 sits inside the 500,000 included with BuildBase Grow, which is $49.
Five times the bill, on paper.

But ask what each $250 and $49 bought. Novu's 250,000 runs put 250,000 events
through their notification workflows, each one fanning out across its channel
steps to every surface their platform reaches. Our 250,000 ran
250,000 automations, and whether any of them reached a phone depends entirely
on whether your users are reachable by email, a browser and Slack. The cheaper
meter buys a narrower product. That is not a gotcha, it is the trade.

| Feature | BuildBase | Novu |
| --- | --- | --- |
| What the bill tracks | Workflow runs, plus analytics events and storage | Workflow runs, the only line on their price list |
| What one run does | Runs an automation; sends are separate allowances | Runs a notification workflow across its channels |
| Free tier | Free: $0, 1,000 runs, 10,000 MAU | Free: $0, 10,000 runs, 5 workflows |
| Entry paid plan | $19/mo (Launch), 100,000 runs | From $30/mo (Pro), 30,000+ runs |
| Overage per 1,000 runs | $0.25, $0.15 or $0.10 by plan | $1.20 on both paid tiers |
| Channels | Email, web push, Slack | Inbox, email, SMS, push, chat, WhatsApp |
| Hosting | Managed; self-host arranged with us | Cloud, open source, or Enterprise self-hosted |
| Scope | Notifications inside 20 modules | Notification infrastructure only |

The channels row settles more evaluations than the overage row, and it should.

## Where Novu wins

> **Where Novu wins:**   **The Inbox component.** Novu ships a prebuilt, composable in-app Inbox for
>   React, Next.js and Remix, with unread counts, tabs, filters, per-user
>   preferences, localization and snoozing already handled. Teams reach for Novu
>   for this alone, and building the equivalent yourself is weeks of work that
>   nobody enjoys.
>
> **Mobile and text.** They deliver to iOS and Android through APNS and Firebase
> Cloud Messaging, with Expo and OneSignal also on the list, and to text messages
> through providers you connect yourself, from a list of 38: Twilio, Telnyx, AWS
> SNS and Plivo among them. We do web push. That reaches a browser and an
> installed web app, nothing more. If your product has a native app, this
> comparison ends on this line and the pricing never comes into it.
>
> **Chat beyond Slack.** Microsoft Teams, Discord, WhatsApp Business, Mattermost,
> Zulip and Webex are first-class chat channels for them. Ours is Slack alone, configured once per
> organization with an incoming webhook URL and a list of event categories you
> tick. If your customers live in Teams or WhatsApp, that gap is the answer.
>
> **Open source, and you can run it.** Novu is open core: the repository is MIT
> licensed, with an `enterprise` directory held back under a commercial licence,
> and it carries 40.3k GitHub stars. You can read the delivery code and run it
> yourself, with the managed cloud and an Enterprise self-hosted tier as the paid
> routes. Our self-host is priced per installation and arranged by talking to us.
> For a team with a hard data-residency rule and a preference for owning the
> stack, that is a genuine advantage and no discount of ours answers it.
>
> **Digests, quiet hours and the preference model.** Novu lets users control what
> they receive, when and where, with digests that bundle a noisy stretch into one
> message, plus quiet hours and snoozing. We have unsubscribe groups
> and preference centers on the email side, and
> [an opinion about which notifications a user gets to turn off](/guides/which-notifications-users-can-turn-off).
> Theirs is the harder version of the problem, solved across more surfaces.

## When each one is the wrong call

Novu is the wrong call if your notifications are a few emails and a Slack
alert, and the rest of your backend does not exist yet. You would be paying
for orchestration across channels you never configure, while still needing
auth, billing, workspaces and the rest from somewhere else. The free tier is
generous enough to hide this for a while, which is its own kind of trap.

BuildBase is the wrong call if notifications are the product. A support tool
that has to reach a technician on their phone, or anything where an in-app
Inbox is the feature users would name if you asked them, is not a web-push
product. Our workflow runs being cheaper per thousand does not help, because
the thing you need is not on the list.

And the two are not exclusive. We emit 239 subscribable webhook events signed
with HMAC-SHA256, so Novu can take them as triggers and own delivery on the
channels we do not reach, the same way it would sit on top of
[any other backend](/blog/what-are-webhooks). You pay both bills. For a product
where the Inbox is the point and the backend is not, that is often the right
shape.

## The honest summary

If you are comparing the two on price per 1,000 workflow runs, stop. The
number favours us by five to twelve times and it is close to meaningless,
because our run executes an automation and theirs runs a notification workflow. Two
meters with the same name counting different work is exactly the kind of
comparison that reads well and decides nothing.

Compare the channels instead. If email, web push and Slack reach your users,
BuildBase bundles notifications into a backend you were going to pay for
anyway, and the meter stays cheap because it is pointed at automations. If
they do not reach your users, Novu is the better product and the bill is the
smaller question. We would rather you worked that out here than three months
into an integration.

Novu's figures here were read from their own pricing page on 13 November 2026,
and ours were last checked against the production API on 31 October 2026.
Both move. Check the date on this page before you lean on a figure. The nearest
neighbour to this comparison is
[Knock](/compare/knock-vs-buildbase), which meters messages sent rather than
runs, and splits differently as a result.
