NotifKit vs SuprSend

SuprSend is a proprietary cloud notification platform with web campaign builders and usage-based tiers. NotifKit is an open-source, self-hosted notification engine that runs on PostgreSQL and Redis Streams with total queue visibility, modular TypeScript providers, and zero platform fees.

The short version

SuprSend targets product and growth teams who want a cloud platform to manage multi-channel messaging campaigns through a web UI. However, relying on a closed-source SaaS means your customer data is stored on their servers, message queues are black boxes, and volume spikes trigger expensive overage charges.

NotifKit gives developers direct control over notification pipelines. All queues, delivery logs, dead letters, and preference rules reside in your own database, with modular transports you can inspect and customize in pure TypeScript.

Feature comparison

Pricing & total cost of ownership (TCO)

SuprSend offers a free tier (10k notifications/mo), an Essentials plan at $100/month (includes 50,000 notifications/mo), and a Business plan at $250/month with volume overages ($0.002/msg on Essentials, $0.005/msg on Business). Additionally, you pay underlying transport rates directly to your providers (Twilio SMS, Resend, AWS SES, FCM Push).

Monthly TCO by notification volume

The table below models total monthly TCO across notification scales, including standard multi-channel deliverability (10% Twilio SMS @ $0.0079, 70% Resend/SES Email @ $0.0001–$0.0008, 20% FCM Push @ $0):

Key differences deep-dive

1. Transparent Redis Stream mechanics vs black-box SaaS

When an upstream delivery fails on a proprietary cloud aggregator, debugging why a message was dropped or delayed often means opening a support ticket or parsing opaque webhook errors.

NotifKit structures its delivery engine across distinct Redis Streams:

Inbound Stream → Enricher → Outbound Stream → Delivery Worker → Gateway (Resend/Twilio/FCM)
                                                    ↳ Retry / DLQ Stream

Priorities are separated into physical streams (critical, normal, low), preventing bulk email campaigns from starving urgent transactional authentication codes. If a delivery permanently fails, it lands in the Dead-Letter Queue (/v1/dlq) where it can be inspected, replayed, or debugged.

2. Extensibility with modular TypeScript packages

Adding a new transport or custom internal webhook in NotifKit requires no proprietary plugin marketplace. Every transport implements a clean TypeScript contract:

import type { Transport, NotificationDispatchedPayload, DeliveryResult } from "notifkit";

export class CustomSmsTransport implements Transport {
  readonly channel = "sms" as const;

  async send(task: NotificationDispatchedPayload): Promise {
    if (!task.destination) {
      return { success: false, error: "no destination resolved for sms" };
    }

    const content = task.renderedContent.content as Record;
    const body = (content.text ?? content.body) as string | undefined;
    if (!body) return { success: false, error: "template produced no text" };

    const response = await fetch("https://internal-sms-gateway.company.com/send", {
      method: "POST",
      headers: { "Content-Type": "application/json" },
      body: JSON.stringify({
        to: task.destination,
        message: body,
      }),
    });

    if (!response.ok) {
      return { success: false, retryable: response.status >= 500, error: await response.text() };
    }

    return { success: true, providerMessageId: (await response.json()).id };
  }
}

When to choose what