NotifKit vs Courier

Courier is a hosted multi-tenant notification platform built around visual designers and SaaS tiers. NotifKit is a self-hosted, code-first notification engine that runs inside your own infrastructure (PostgreSQL + Redis) with zero per-message markup, complete data privacy, and native AI integration.

The short version

If your company requires non-technical marketing staff to visually design transactional email templates inside a hosted web app and you are comfortable routing customer PII through a third-party cloud, Courier is built for that workflow.

If you are an engineering team that treats notifications as critical product infrastructure, wants workflows versioned in Git, refuses to pay a SaaS tax on every message, and must keep user data inside your private VPC, NotifKit gives you a battle-tested engine you own completely.

Feature comparison

Pricing & total cost of ownership (TCO)

Courier charges a per-message platform toll on top of your notification volume once you exceed their free tier. Courier's standard self-serve pricing charges $0.005 per notification after the initial 10,000 free sends, or requires negotiation for enterprise contracts. You also pay underlying provider fees (Twilio, Resend, AWS SES, APNs/FCM) directly on top of Courier's SaaS platform fee.

Monthly TCO by notification volume

Here is the complete Total Cost of Ownership across volumes, incorporating standard delivery mix (10% Twilio SMS @ $0.0079, 70% Resend/SES Email @ $0.0001–$0.0008, 20% FCM Push @ $0):

Key architectural differences

1. Data privacy and compliance

Courier is a multi-tenant cloud service. To send a notification, your application must transmit the recipient's email address, phone number, device push tokens, and the interpolated message payload (which often contains billing amounts, reset tokens, or personal health/financial data) to Courier's servers.

NotifKit runs in your private network. Customer profiles, contact endpoints, and notification logs remain inside your PostgreSQL database. When a delivery occurs, NotifKit speaks directly to the upstream gateway (e.g. Resend, Twilio, FCM) over TLS. No third-party data processor agreement (DPA) or external data retention audit is required.

2. Code-defined workflows vs cloud automation graphs

Courier coordinates multi-channel sequences using Courier Automations (a node-based DAG builder and JSON schema API). While visual automation builders appeal to marketing and non-technical stakeholders, they create synchronization drift between application state and notification logic.

In NotifKit, workflows are defined directly in TypeScript code and executed by durable Redis Stream state machines. Workflows can sleep for days, wait for external domain events (like setup.completed), and resume cleanly across worker restarts:

import { workflow } from "notifkit";

workflow("user-onboarding", async ({ step, event }) => {
  // Step 1: Send welcome email immediately
  await step.notify({
    template: "welcome-email",
    channels: ["email"],
    data: { name: event.name },
  });

  // Step 2: Wait for 3 days (survives restarts and deploys)
  await step.wait("3d");

  // Step 3: Check if user completed setup; if not, send reminder
  const completed = await step.waitForEvent("setup.completed", {
    timeout: "2d",
    match: { userId: event.user.id },
  });

  if (!completed) {
    await step.notify({
      template: "setup-reminder",
      channels: ["push", "sms"],
      fallback: true,
    });
  }
});

3. Local-first AI agent integration via Model Context Protocol (MCP)

Both platforms support the Model Context Protocol (MCP) for AI coding assistants like Claude Code and Cursor. However, Courier's MCP server interacts with its remote multi-tenant cloud API, while NotifKit's built-in MCP server runs locally inside your private network, allowing coding assistants to inspect PostgreSQL recipient records, preview Handlebars rendering, and query Redis Stream queues directly without transmitting operational data to a third party.

When to choose what