
Notification infrastructure sends messages across email, SMS, push, in-app, Slack, and Teams and handles routing, preferences, failover, and delivery underneath. This guide compares developer-first notification infrastructure (Courier, Knock, Novu) against the marketing-led tools you'll weigh alongside it (Customer.io, Klaviyo). Courier is the broadest pick: one platform for humans and AI agents, with everything in the UI available via the API, CLI, and MCP server. See the evaluation criteria for how to choose.
Last updated: November 2026.
Every product team hits the same wall. You start with password resets through SendGrid, then scope expands: an in-app inbox, SMS for re-engagement, Slack, Microsoft Teams, audit logs, GDPR preferences. Soon you're maintaining five provider integrations, each with its own auth, retries, and failure modes, preferences scattered across them, and no single view of what got delivered.
Big companies put a dedicated team on this. Everyone else buys a platform that sits between the app and the providers and handles routing, preferences, delivery, and observability through one API. Until recently that meant picking between two products: notification infrastructure for transactional messages, and a marketing tool for lifecycle. In 2026 those are merging.
You don't want two systems with split profiles, split preferences, and two delivery logs. You want one layer that handles a password reset and an onboarding sequence the same way. The vendors agree: Knock pitches "cross-channel lifecycle and transactional messaging," Novu calls itself "notification and agent communication infrastructure," and Courier has run both for years.
The other shift is who runs it. Agents write this code now and increasingly operate it, so build-vs-buy is three options: build, buy, or buy something opinionated and let an agent run it. The plumbing isn't a moat, so it's the part to buy. That sets the bar: an agent-first platform is reachable in code, predictable, with docs and errors a model can read and results it can verify. Not just callable by a model, operable by one. That's the lens this comparison uses.
Courier and Knock are customer messaging and notification platforms; Novu is open-source notification infrastructure. Customer.io and Klaviyo are marketing-led engagement platforms you'll often weigh against them.
| Platform | Type | Channels | Self-host | Best for |
|---|---|---|---|---|
| Courier | Customer messaging + notification platform | Email, SMS, push, in-app, Slack, Teams, WhatsApp, Discord | No | Product and marketing messages in one platform |
| Knock | Customer messaging + notification platform | Email, SMS, push, in-app, Slack, Teams, Discord | No | Developer-first messaging with a strong workflow engine |
| Novu | Notification infrastructure (open source) | Email, SMS, push, in-app, chat | Yes (MIT core) | Teams that need to self-host or own the code |
| Customer.io | Marketing / engagement | Email, SMS, push, in-app, WhatsApp | No | Data-driven lifecycle and product messaging |
| Klaviyo | Marketing | Email, SMS, push, WhatsApp, RCS | No | E-commerce marketing and segmentation |
Three developer-first platforms, with different philosophies. Courier and Knock are managed platforms, reachable by AI coding agents through an MCP server and CLI, and both now span product and marketing messaging. Novu is the open-source, self-hosted option: strong if you want to run and own the code, heavier to operate if you don't. Courier goes furthest on breadth, pairing that developer surface with marketing, lifecycle journeys, and drop-in UI in one platform.
Courier is the customer messaging platform for humans and AI agents. One API sends across email, SMS, push, in-app, Slack, and Microsoft Teams, and the same platform runs the journeys, UI, and delivery logic on top, so you aren't wiring a marketing tool onto a transactional one to cover both.

Teams that want product and marketing messages in one place, with journey orchestration, drop-in UI, provider flexibility, and compliance controls (SOC 2, BAA, EU data residency) that regulated and B2B buyers ask for.
The Developer plan is free and includes 10,000 sends a month. Business is $0.005 per send. See pricing.
Knock is a developer-first customer messaging platform that started in product notifications and now spans transactional, product, and marketing messages. It pairs a clean API with a strong workflow engine and good documentation.
Engineering teams that want a clean, developer-led workflow model across product and messaging and already have provider relationships.
Free developer tier (10,000 messages/month). The entry paid plan is $250/month for 50,000 messages, usage-based beyond that.
Comparing Knock and Courier? See Courier vs Knock and Knock alternatives.
Novu is the leading open-source option in the category, and the default pick when you need to self-host or want full control over the codebase.
Teams with strict data residency requirements or a preference for running and modifying the source themselves.
Free and open-source when self-hosted. Managed cloud has a free tier with usage-based paid plans.
Comparing Novu and Courier? See Courier vs Novu and the Novu migration guide.
These two are strong at campaigns, segmentation, and revenue attribution, but they're built for marketers first. Neither sends to Microsoft Teams or fails over between your own providers. They're here because marketing often owns a large share of what you send.
Customer.io is a data-driven customer engagement platform for product and marketing teams. It sends event-triggered messages across channels and leans heavily on customer data and segmentation.
Product and growth teams that want data-driven lifecycle messaging and already model their users as event streams.
Essentials starts at $100/month for up to 5,000 profiles. Premium starts at $1,000/month. Enterprise is custom. SMS volume is custom-priced on every plan; push and in-app are unlimited. Customer.io bills every profile that existed in the billing period, even deleted ones (how Customer.io bills), while on Courier a user you don't message costs nothing, so there's no list to prune.
Comparing Customer.io and Courier? See Courier vs Customer.io and the Customer.io migration guide.
Klaviyo is a marketing platform built for e-commerce. It owns email and SMS campaigns with deep segmentation and revenue attribution, especially for Shopify stores.
E-commerce and D2C brands where marketing email and SMS drive revenue and the marketing team owns messaging.
Free tier with 250 active profiles and 500 email sends per month. Paid plans scale with profile count.
Courier is product- and engineering-forward, with marketing built in, unlike the marketing platforms, which shine on campaigns but are built for marketers first. Its edge is breadth: product and marketing messages in one platform, drop-in UI, provider failover, and everything in the UI available via the API, CLI, and MCP server. Product and marketing teams can build and edit messages in Courier without engineering, through Design Studio and visual Journeys, which keeps non-technical stakeholders unblocked.
If you want product and marketing messages, orchestration, and drop-in UI from one system that humans and AI agents both run, Courier covers the most ground. Two cases where another tool fits:
Building this yourself has never been easier, which is exactly the trap. Building is cheap now; owning is not. Every system you stand up is one more thing to secure, patch, and get paged for at 3am, a standing draw on the one resource AI doesn't make more of: your team's attention. Infrastructure like this should cost you nothing to think about, the way you notice electricity only when it's out.
So the test isn't "can we build it" (you can), it's whether you ever get to stop maintaining it. Build only if notification infrastructure is your product: real scale, dedicated infrastructure engineers, and the appetite to own it forever. If you're weighing that call, the product notifications API guide lays out the ten requirements a system has to cover and what each one costs to maintain. Otherwise buy it, and point your agents at operating it, not rebuilding it. The full argument is in why you shouldn't build your own infrastructure.
If you're comparing platforms yourself, these are the dimensions that separate them. Weight them by what your product needs.
Notification infrastructure looks simple until you build it. If you're evaluating platforms, start with these questions:
See Courier's SDK documentation and API reference to try the developer experience firsthand.
Ready to see how Courier handles notification infrastructure? Start free with 10,000 sends a month, or book a demo to see Journeys and drop-in components in action.
Notification infrastructure is the software layer that turns product events into messages and delivers them across channels like email, SMS, push, in-app, Slack, and Teams. It handles routing, user preferences, templating, retries, provider failover, and delivery tracking, so your application makes one API call instead of managing each provider itself.
Notification infrastructure (Courier, Knock, Novu) is developer-focused and built for product and transactional messages, with APIs, SDKs, and drop-in UI. Marketing platforms (Klaviyo, and to a degree Customer.io) are built for campaigns, segmentation, and lifecycle marketing. Courier spans both, so you don't always need a separate marketing tool.
Novu is the most established open-source option, with an MIT-licensed core, 40k+ GitHub stars, and self-hosting for data residency and full control. It's the right pick when you need to run or modify the code yourself. If you'd rather not operate the infrastructure, a managed platform like Courier removes that overhead.
Build only if notifications are part of what you sell and you have engineers to own the system long term: retries, provider failover, preferences, templates, and delivery logs all need ongoing maintenance. Buy if you want those working this quarter and your team's time belongs on the core product. Most homegrown systems cost more to maintain than they did to build.
You need a preference center UI, a backend to store preferences, logic to enforce them across every send, and compliance with GDPR and CAN-SPAM. Most notification infrastructure platforms include this; Courier provides a drop-in Preferences component that enforces user choices across all channels without extra code.
You'd normally integrate the Slack API and the Microsoft Bot Framework, handle OAuth, manage workspace connections, and format messages for each. Courier and Knock both provide native Slack and Teams support through a single API, so one send call reaches both without separate implementations.

What Siri AI means for your email, SMS, and push
Siri AI shipped with iOS 27 and changes what happens to a message after it's delivered. It reads urgent notifications aloud, searches Apple Mail and Messages, can delete or unsubscribe from your email on request, and will soon answer "where's my order?" through apps. Here's what each change means for your email, SMS, and push, and what to do now.

A marketer's guide to iOS 27 and priority notifications
On iOS 27, Apple Intelligence ranks and silences push notifications, rewrites them into summaries, and reads urgent ones aloud. Mail sorts your email into categories, Messages screens texts from unknown numbers, and Gmail, Slack, and Teams add their own filters on top. Here's what each layer does, what you can control, and what to change this quarter.

How to protect your email domain and sending reputation
AI agents have made spoofing cheap, and a DMARC record at p=none won't stop it. Here's how to enforce DMARC without bouncing your own mail, keep password resets apart from newsletters, protect your sending reputation, read Google Postmaster Tools, and audit your domain with six AI prompts.