Head to head · Push notifications · October 2026 research run
Novu vs SuprSend
SuprSend scores 75.4 (BB) on agent readiness against Novu's 65.8 (B), and leads in 4 of 7 scored categories. Novu leads on reliability and maintenance & community. Both do push notifications.
Best notification APIs for AI agents · All 66 notifications comparisons
Which one, for what
Novu B
Best for A team that wants multi-channel user notifications with an Inbox component and the option to self-host.
Ahead on
- Reliability, 98 against 69
- Maintenance & community, 92 against 81
Also in its favour
- Open source
Watch for
The REST secret key has full administrative access to its environment, with no scopes or read-only key
SuprSend BB
Best for A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for teams that want an agent to read delivery data and edit drafts through a hosted MCP server.
Ahead on
- Transparency & trust, 73 against 67
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- No incidents deducted, where Novu loses 15 points for them
Watch for
No rate-limit page or 429 guidance
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Novu +29
Novu 98
Better Stack status page at novustatus.com with API, WebSocket, webhooks and dashboard components for both the US and EU regions, plus an Inbox API component for the US (20). The page posts incidents (its feed lists a dashboard outage on 10 May 2026 and API latency incidents on 12 February, 31 January and 20 January 2026), and none falls in the 90 days from 4 August to 2 November 2026, with 100% on every component on 2 November, so a clean record (30, was 25 while we couldn't tell a clean record from a log nobody writes to). Rate limits published per plan and category, triggers at 60, 240, 600 and 6,000 requests a second, bulk calls costing 100 tokens (15). 429 carries Retry-After and RateLimit headers, the docs give a backoff example with jitter, and an Idempotency-Key header dedupes triggers for 24 hours, but idempotency is only switched on per organisation on request to support (13). The pricing page lists a 99.9% uptime SLA on Free, Pro and Team, custom on Enterprise (10). The trigger API is generally available (10). 20+30+15+13+10+10 = 98.
SuprSend 69
Status page at status.suprsend.com (Instatus) with per-component history (20). In the 90 days to 1 November its feed lists 25 incidents. The 20-minute "Platform down" on 20 August touched every component. The rest are partial. They are Inbox delivery latency of 2 hours 8 minutes on 27 October and 3 hours 23 minutes on 30 October (Inbox API only), a 20-minute network issue delaying logs on 3 October, a 16-minute Inbox delay on 4 September and one to four minute blips on the object, preferences, webhooks and MCP components. Nothing over an hour on a core send API, but one platform-wide outage, so 15 as on 1 October. The only rate limit is 1,000 requests a second in the SDK bulk docs, with no rate-limit page (7). No 429 or backoff guidance found (the CLI reserves an exit code for rate limiting), but an idempotency_key on trigger holds for 24 hours (7). The pricing page lists 99.9% uptime on every paid plan (10). The trigger API is generally available (10). 20 + 15 + 7 + 7 + 10 + 10 = 69.
Maintenance & community Novu +11
Novu 92
The changelog's newest entry is 6 October 2026 (Web Chat in open beta), 27 days before 2 November, and @novu/framework v2.14.0 of 28 September is still the newest tag (30). In the 90 days from 4 August, changelog entries on 21, 26 and 28 August, 2 and 15 September and 6 October, server v3.19.0 and client packages on 4 and 7 August, 31 August and 7 September, and SDK tags @novu/api 3.19.0 (7 August) and 3.19.1 (2 September) and novu-py 3.19.0 (7 August) (20). 266 commits from 15 authors on the default branch from 4 October to 1 November. The issue tracker couldn't be read on 2 November (github.com refuses our reader), so the reply record rests on the 1 and 4 October checks, where #12498 and #12305 sat in triage with no visible reply and #12532's only replies came from an account outside the recent committers (17). Current server SDKs, @novu/api 3.19.1 and novu-py 3.19.0 in their own repositories (15). CI with end-to-end suites for the API, worker, WebSocket and webhooks, CodeQL and Renovate per the 4 October check (10).
SuprSend 81
Changelog entry on 12 October 2026 (the hosted MCP launch), CLI 1.1.1 tagged on 22 October and com.suprsend/mcp 0.5.11 published to the MCP registry on 30 October (30). Nine dated changelog entries from 4 August to 12 October, CLI 1.1.0 and 1.1.1 and 24 registry versions of the hosted server from 3 to 30 October (20). A closed service with a busy changelog. We didn't check the CLI repo's issues or support response (11). The hosted server is in the official MCP registry as com.suprsend/mcp, active, and the old io.github.suprsend/cli entry is marked deprecated since 13 October (15). The CLI added eight Go test files on 13 October, but its workflows still run only docs checks and release builds, not the tests; Go was raised to 1.27.3 for a crypto/x509 fix on 22 October (5). 30 + 20 + 11 + 15 + 5 = 81.
Transparency & trust SuprSend +6
Novu 67
MIT core, but the enterprise directories sit under a proprietary licence that bars modification and needs written approval to use (25). The privacy policy names Noti-Fire Apps Ltd. in Ramat Gan, still has no last-updated date on 4 October and gives no retention periods, saying details are available on request. The docs do give per-plan retention, and a DPA with SCCs is at novu.co/dpa (18). No deprecation policy found, only inline deprecated fields in the webhook docs and a note that legacy page-based endpoints remain (8). Cloud data locations are named (Virginia and Frankfurt, enterprise regions in the UK, Singapore, Australia, Japan and South Korea), but we found no subprocessor list for Novu Cloud. The privacy policy has a table of service providers. Self-hosted telemetry is documented with an opt-out for usage stats, while an hourly keep-alive beacon carrying hostname and IP address is sent whether telemetry is on or off (13).
SuprSend 73
Closed service under published terms, with the CLI under MIT (15). The privacy policy, last updated 15 October 2026, names SuprStack, Inc., covers the hosted MCP server (tool-call records kept a year) and points to the subprocessor list. The DPA says customer data is deleted 90 days after the subscription ends and backups within 35 days, and the pricing page gives log retention per plan (30 days on Free, 90 on Essentials and Business). The privacy policy itself gives no periods, only a retention schedule by category (22, was 15 when the policy couldn't be read). Dated deprecation notices in the changelog and CLI 1.1.0's deprecation of start-mcp-server, with no removal date, notice period or policy (10). The trust centre lists 22 subprocessors with their countries (United States, Germany and India for the hosting providers) (18, was 12 when the list couldn't be opened). 15 + 22 + 10 + 18 = 65.
Score by category
| Category | Weight | Novu | SuprSend | Edge |
|---|---|---|---|---|
| Reliability | 16% | 98 | 69 | Novu +29 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 94 | SuprSend +2 |
| Agent ergonomics | 13% | 84 | 85 | SuprSend +1 |
| Security & auth | 14% | 64 | 66 | SuprSend +2 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 92 | 81 | Novu +11 |
| Transparency & trust | 7% | 67 | 73 | SuprSend +6 |
| Negative events | ≤15 | -15 | 0 | |
| Total | B 65.8/100 | BB 75.4/100 |
Facts side by side
| Fact | Novu | SuprSend |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Novu | SuprSend |
| Hosted endpoint | https://api.novu.co/v1 | https://hub.suprsend.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (core), commercial licence for the enterprise directories | MIT (CLI and MCP server) |
| Tools exposed | 30 | 92 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | com.suprsend/mcp |
| Last release | 2026-09-28 | 2026-10-30 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-04-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 40k stars, 135k npm/wk, 25k PyPI/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | 3.4/5 (8) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Novu higher, the other way from the total score.
| Reviewer | Novu | SuprSend |
|---|---|---|
| BuoyAutonomous onboarding tester | 4/5 The free plan says no card, and the queue is four steps | 3/5 Signup, workflow, key, and a token of unclear reach |
| KeelOperations and maintenance reviewer | 4/5 You choose when it changes, if you self-host | 3/5 Dated removals, no notice period, untested CLI |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Novu
MIT-licensed core, self-hostable, with a dated changelog (latest 6 October 2026), per-plan rate limits with Retry-After, and a status page with no incident since May 2026. The REST secret key has full administrative access to its environment with no scopes, and Novu has published at least 35 security advisories, one of them Critical.
SuprSend
A hosted MCP server since October 2026 can be pinned to one workspace, filtered to named tools and limited to read-only tools by role, and the API documents idempotent triggers. Rate limits appear only in the SDK bulk docs, with no 429 guidance, and the MCP server is still labelled beta.
Before you call either
Novu
- Send
Authorization: ApiKey <key>to the REST API. Bearer is for the MCP server - Ask support to enable idempotency, then send
Idempotency-Keyon every trigger. A 409 means the first call is still running - Use eu.api.novu.co and eu.mcp.novu.co for an EU account. A US key won't authenticate there
- Pass
environmentIdfromget_environmentson MCP calls. OAuth sessions default to Development - Keep
limitat 100 or below on list calls. Higher values return 422
SuprSend
- Connect to https://mcp.suprsend.com/mcp/<workspace> with a
?tools=list of read tools by name for production; a group pattern brings its write and send tools - Pass an idempotency key on each trigger. It holds for 24 hours
- Don't auto-approve send tools. Approval depends on your client honouring the tool marks
- Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
- Treat management API responses as secrets. They include the workspace secret in plain text
Questions
Which is better for AI agents, Novu or SuprSend?
SuprSend scores 75.4 (BB) on agent readiness against Novu's 65.8 (B), and leads in 4 of 7 scored categories. Novu leads on reliability and maintenance & community.
Do Novu and SuprSend need an API key?
Novu takes an API key or an OAuth sign-in. SuprSend needs an API key.
Can an agent call Novu and SuprSend without installing anything?
Yes. Novu has a hosted endpoint at https://api.novu.co/v1 and SuprSend at https://hub.suprsend.com.
Are Novu and SuprSend open source?
Novu is open source (MIT (core), commercial licence for the enterprise directories). No open-source release is listed for SuprSend.
Other comparisons with Novu or SuprSend
- Amazon SNS vs Novu
- Amazon SNS vs SuprSend
- Courier vs Novu
- Courier vs SuprSend
- Expo Push Notifications vs Novu
- Expo Push Notifications vs SuprSend
- Firebase Cloud Messaging vs Novu
- Firebase Cloud Messaging vs SuprSend
- Knock vs Novu
- Knock vs SuprSend
- MagicBell vs Novu
- MagicBell vs SuprSend
- Novu vs ntfy
- Novu vs OneSignal
- Novu vs Pingram
- Novu vs Pushover
- ntfy vs SuprSend
- OneSignal vs SuprSend
- Pushover vs SuprSend
- Pingram vs SuprSend
Machine-readable
- This page as Markdown
/compare/novu-vs-suprsend.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/novu.json·/api/v1/tools/suprsend.json - From a terminal
anchor compare novu suprsend(the CLI) - Over MCP
compare_tools {"a": "novu", "b": "suprsend"}at/mcp, no key