Help Scout
Help Scout keeps adding channels — now a portal customers sign into
Comparison · Comms
Stalwart vs SuprSend
A side-by-side editorial comparison of Stalwart and SuprSend — release velocity, themes, recent moves, and the top alternatives to consider.
Stalwart vs SuprSend: at a glance
| Feature | Stalwart | SuprSend |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | email-standards, jmap, imap, dmarc | notification infrastructure, developer experience, templates, mcp |
| Last editorial update | 1d ago | 3mo ago |
| Website | Visit → | — |
What is Stalwart?
Stalwart is shipping email's next-generation auth stack while the specs are still in draft.
Stalwart is an all-in-one mail and collaboration server — SMTP, IMAP, JMAP, CalDAV, CardDAV and WebDAV in one binary — releasing every one to two weeks on the 0.16.x line. The last two months read as a standards campaign: DKIM2 and the full DMARCbis set in 0.16.12, VAPID push in 0.16.14, FreeBSD support in 0.16.13, and a run of IMAP extensions (UIDONLY, UIDBATCHES, MESSAGELIMIT/SAVELIMIT) in 0.16.17. Between the additions, most of each release is JMAP conformance repair driven by the jmap-test-suite.
What is SuprSend?
Notification infra platform invests in developer ergonomics — MCP, CLI, Templates 2.0, OTEL.
SuprSend has been shipping for a developer-first audience: Templates 2.0 with variants and a redesigned editor (one template per channel, with tenant/language/plan branches), a programmatic Messages API for fetching and updating delivery state, zero-install CLI and MCP server via npx, native monitoring integrations for Datadog, New Relic, and OpenTelemetry. CLI updates also added automatic SKILLS.md generation and fixed a corrupted Node SDK package-lock.
Stalwart vs SuprSend: editorial side-by-side
Stalwart
5.0COMMS
Stalwart is shipping email's next-generation auth stack while the specs are still in draft.
◆ Current state
Stalwart is an all-in-one mail and collaboration server — SMTP, IMAP, JMAP, CalDAV, CardDAV and WebDAV in one binary — releasing every one to two weeks on the 0.16.x line. The last two months read as a standards campaign: DKIM2 and the full DMARCbis set in 0.16.12, VAPID push in 0.16.14, FreeBSD support in 0.16.13, and a run of IMAP extensions (UIDONLY, UIDBATCHES, MESSAGELIMIT/SAVELIMIT) in 0.16.17. Between the additions, most of each release is JMAP conformance repair driven by the jmap-test-suite.
◆ Where it's heading
The project is building toward being the reference implementation of the modern mail stack — JMAP first, with the classic protocols held at parity rather than left behind. The fix lists have shifted in character over these eight releases: less "feature does not work", more "spec detail is wrong", which is what a codebase looks like as it converges on conformance. Security and multi-tenancy fixes keep appearing alongside the protocol work, indicating real deployments are exercising the newer subsystems.
◆ Prediction
The next releases most likely track revisions to the drafts already implemented — DKIM2, JMAP push and the calendar drafts are all still moving — rather than adding another protocol surface. Expect continued JMAP conformance fixes until the test suite stops producing them.
SuprSend
5.0COMMS
Notification infra platform invests in developer ergonomics — MCP, CLI, Templates 2.0, OTEL.
◆ Current state
SuprSend has been shipping for a developer-first audience: Templates 2.0 with variants and a redesigned editor (one template per channel, with tenant/language/plan branches), a programmatic Messages API for fetching and updating delivery state, zero-install CLI and MCP server via npx, native monitoring integrations for Datadog, New Relic, and OpenTelemetry. CLI updates also added automatic SKILLS.md generation and fixed a corrupted Node SDK package-lock.
◆ Where it's heading
SuprSend is positioning as the notification infrastructure that backend engineers — and the AI coding agents working on their behalf — actually want to use. The MCP-server and CLI-via-npx work, plus Claude Code plugin refresh, signal a deliberate AI-native posture. Templates 2.0 is the structural play: one template that resolves to the right variant per tenant/language/plan removes a real maintenance burden for multi-tenant SaaS and i18n use cases, which is where notification infra usually breaks down at scale.
◆ Prediction
Expect deeper Inbox/in-app notification primitives now that the Messages API is programmatic, more advanced Templates 2.0 variant logic (likely conditional fragments and content reuse), and broader observability surface — possibly per-workflow SLO tracking. Continued investment in MCP/agent-callable workflows is highly likely.
Alternatives to Stalwart and SuprSend
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Stalwart or SuprSend.
Synapse
Synapse alternates release candidates with security patches on a tight two-week cycle
Canary Mail
Canary Mail ships maintenance across four platform lines; features have gone quiet since April.
Bandwidth
Bandwidth is closing the gaps that used to require a support ticket
Beeper
Beeper stopped aggregating apps and started merging the people inside them.
Respond.io
respond.io is monetizing AI usage directly while putting an assistant that builds agents in every workspace.
See all Stalwart alternatives → · See all SuprSend alternatives →
Recent activity from Stalwart and SuprSend
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoStalwartIMAP gains UIDONLY, UIDBATCHES and message-limit extensions
- 9d agoStalwartJMAP delivery push arrives; strict relays stop rejecting calendar mail
- 16d agoStalwartFix-only release: JMAP semantics and a credential escalation
- 22d agoStalwartVAPID lands for JMAP Web Push
- 1mo agoStalwartFreeBSD support, plus OAuth scopes for IMAP, SMTP and Sieve
- 1mo agoStalwartDKIM2 and the full DMARCbis suite ship in one release ⚡
- 3mo agoSuprSend Messages API — query and update delivery state programmatically
- 3mo agoSuprSendMessages API (republish)
- 3mo agoSuprSend CLI & MCP Server — Zero-install via npx suprsend
- 3mo agoSuprSendCLI & MCP zero-install (republish)
- 4mo agoSuprSend Templates 2.0 - variants, redesigned editor, one template for every channel ⚡
- 4mo agoSuprSendTemplates 2.0 (republish)
Frequently asked questions
What is the difference between Stalwart and SuprSend?
They serve adjacent needs but don't currently overlap on shipped themes. Stalwart and SuprSend are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Stalwart better than SuprSend?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Stalwart and SuprSend are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
What are the best alternatives to Stalwart?
Top Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.
What are the best alternatives to SuprSend?
Top SuprSend alternatives in Comms are ranked by recent ship velocity. Browse the "SuprSend alternatives" section above for the current picks, or visit /alternatives/suprsend for the full list with editorial commentary on each.