Slack
Slack raises the Marketplace bar back to ten installs while the agent platform consolidates.
Comparison · Comms
Courier vs Stalwart
A side-by-side editorial comparison of Courier and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Courier vs Stalwart: at a glance
What is Courier?
Courier is turning its notification API into a full messaging orchestration platform.
Courier has evolved from a transactional notifications API into an orchestration platform anchored by Journeys, its event-driven workflow engine. Recent releases layer optimization and enterprise controls on top — A/B testing inside journeys, isolated environments, and reusable routing strategies. Design Studio has matured into the central authoring surface across email, SMS, push, in-app, and chat.
What is Stalwart?
SCIM v2 lands in the Enterprise tier, opening a provisioning surface beside the protocol work.
Stalwart ships weekly, and 0.16.20 breaks a long run of pure spec-completeness work by adding SCIM v2 to the Enterprise tier: core schema (RFC 7643), protocol (RFC 7644), cursor-based pagination (RFC 9865), the SCIM interoperability profile and the IPSIE lifecycle profile. The rest of the release is the established mix - conference links in calendar invites and alarms, 25 interface translations, and a fix run covering DANE lookup and failure semantics, Redis Sentinel deployments where rediss:// URLs connected to the master in cleartext, and cluster node leases that left removed nodes marked stale indefinitely.
Courier vs Stalwart: editorial side-by-side
Courier
5.0COMMS
Courier is turning its notification API into a full messaging orchestration platform.
◆ Current state
Courier has evolved from a transactional notifications API into an orchestration platform anchored by Journeys, its event-driven workflow engine. Recent releases layer optimization and enterprise controls on top — A/B testing inside journeys, isolated environments, and reusable routing strategies. Design Studio has matured into the central authoring surface across email, SMS, push, in-app, and chat.
◆ Where it's heading
The build order is clear: ship the orchestration core first (Journeys, Design Studio, the MCP-aware CLI), then make it production-grade for larger teams. The last quarter is about optimization and governance — experiments, custom environments, decoupled routing — rather than net-new channels. AI is being threaded in as a feature, like localization, not a headline product.
◆ Prediction
Expect continued hardening of Journeys as the hub: more experiment types, richer per-variant analytics, and deeper AI assistance inside Design Studio.
Stalwart
6.3COMMS
SCIM v2 lands in the Enterprise tier, opening a provisioning surface beside the protocol work.
◆ Current state
Stalwart ships weekly, and 0.16.20 breaks a long run of pure spec-completeness work by adding SCIM v2 to the Enterprise tier: core schema (RFC 7643), protocol (RFC 7644), cursor-based pagination (RFC 9865), the SCIM interoperability profile and the IPSIE lifecycle profile. The rest of the release is the established mix - conference links in calendar invites and alarms, 25 interface translations, and a fix run covering DANE lookup and failure semantics, Redis Sentinel deployments where rediss:// URLs connected to the master in cleartext, and cluster node leases that left removed nodes marked stale indefinitely.
◆ Where it's heading
The protocol gap-closing continues, with DANE, iMIP, CalDAV and JMAP absorbing corrections every release, but SCIM points at a different axis: who is expected to deploy this. Provisioning, per-tenant branding, cluster lease handling and the recovery-admin impersonation fixes are operator concerns rather than mail-standard concerns, and they have been accumulating since 0.16.15. Calendar remains the least settled surface, now extending into localization rather than correctness alone.
◆ Prediction
SCIM shipped with the interoperability and IPSIE profiles attached, so the near-term work is likely the directory-side corrections that follow first contact with real identity providers - the same pattern the LDAP and SQL directory integrations have been producing. The 25 new translations open a localization surface that has not yet had to survive a release cycle.
Alternatives to Courier and Stalwart
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 Courier or Stalwart.
Synapse
Synapse publishes only a changelog link, so its feed records releases without describing them
Element X Android
Element X Android ships roughly weekly, alternating real features with fix rounds
Wire
Calling is the one surface Wire's web client touches in every documented release.
Zoho Cliq
Zoho retells Cliq 7.0 as an AI story, and lets customers pick whose model tells it.
Rocket.Chat
Rocket.Chat finishes the 8.8 calling work while the licence wall for SSO gets a date.
See all Courier alternatives → · See all Stalwart alternatives →
Recent activity from Courier and Stalwart
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoStalwartSCIM v2 provisioning lands in the Enterprise tier ⚡
- 8d agoStalwartMySQL key columns need a manual ALTER; Sieve gains spam-score vars
- 15d agoStalwartResource limits arrive for inbound reports and RocksDB caches
- 22d agoStalwartIMAP gains UIDONLY, UIDBATCHES and message-limit extensions
- 1mo agoStalwartJMAP delivery push arrives; strict relays stop rejecting calendar mail
- 1mo agoStalwartFix-only release: JMAP semantics and a credential escalation
- 1mo agoCourierExperiments: A/B Testing in Journeys
- 2mo agoCourierAI Localization
- 2mo agoCourierEmbed Notification Preferences with One Web Component
- 3mo agoCourierIntroducing Routing: Reusable Strategies for Every Template
- 4mo agoCourierEmail Fonts and Colors
- 4mo agoCourierCustom Environments for Safer Messaging Workflows
Frequently asked questions
What is the difference between Courier and Stalwart?
They serve adjacent needs but don't currently overlap on shipped themes. Stalwart is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Courier better than Stalwart?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Stalwart is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
What are the best alternatives to Courier?
Top Courier alternatives in Comms are ranked by recent ship velocity. Browse the "Courier alternatives" section above for the current picks, or visit /alternatives/courier for the full list with editorial commentary on each.
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.