Slack
Slack raises the Marketplace bar back to ten installs while the agent platform consolidates.
Comparison · Comms
Misskey vs Stalwart
A side-by-side editorial comparison of Misskey and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:self-hosting
Misskey vs Stalwart: at a glance
What is Misskey?
Misskey deleted its bundled machine-learning stack and made moderation someone else's service to run.
The visible history is essentially one release train, nine tags from 2026.7.0-beta.0 through the 2026.7.0 release, plus the first alpha of 2026.8.0. The defining change is that sensitive-media detection no longer runs inside Misskey: nsfwjs, TensorFlow.js, and the bundled NSFW model are gone from the codebase, replaced by HTTP calls to a separate sensitive-detector service. Operators who rely on the feature must stand that service up and point the control panel at it; if they do not, detection stops and all media is treated as non-sensitive.
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.
Misskey vs Stalwart: editorial side-by-side
Misskey
6.3COMMS
Misskey deleted its bundled machine-learning stack and made moderation someone else's service to run.
◆ Current state
The visible history is essentially one release train, nine tags from 2026.7.0-beta.0 through the 2026.7.0 release, plus the first alpha of 2026.8.0. The defining change is that sensitive-media detection no longer runs inside Misskey: nsfwjs, TensorFlow.js, and the bundled NSFW model are gone from the codebase, replaced by HTTP calls to a separate sensitive-detector service. Operators who rely on the feature must stand that service up and point the control panel at it; if they do not, detection stops and all media is treated as non-sensitive.
◆ Where it's heading
The direction is a smaller, more conventional Node application with its heavy and specialized dependencies pushed outside the process. The same release raises the Node floor to 22.22.2, 24.17.0 and 26.4.0, moves the Docker image to Node 26 on Debian trixie, and inherits a sharp requirement that breaks x86_64 CPUs without SSE4.2. The rebuilt logging layer points the same way, with one-line JSON output, per-domain levels, automatic credential redaction, and Sentry trace correlation, which is what an operator using standard tooling wants rather than what a self-contained appliance would ship.
◆ Prediction
Node 22 support is already flagged for removal, so the next train should drop it. Whether OpenTelemetry returns after being pulled between beta.6 and the release candidate is not something these entries settle.
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 Misskey 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 Misskey 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 Misskey alternatives → · See all Stalwart alternatives →
Recent activity from Misskey 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
- 18d agoMisskeyImage viewer gains a pixel-art zoom mode
- 22d agoStalwartIMAP gains UIDONLY, UIDBATCHES and message-limit extensions
- 1mo agoStalwartJMAP delivery push arrives; strict relays stop rejecting calendar mail
- 1mo agoMisskeyNSFW detection moves out of core to an external service ⚡
- 1mo agoMisskeyRelease candidate drops OpenTelemetry from 2026.7.0
- 1mo agoStalwartFix-only release: JMAP semantics and a credential escalation
- 1mo agoMisskeyImage viewer rebuilt and upload preview added
- 1mo agoMisskeyFixes account creation API for non-initial accounts
- 1mo agoMisskey2026.7.0-beta.4
Frequently asked questions
What is the difference between Misskey and Stalwart?
Both compete on the same themes — self-hosting — within Comms. Misskey and Stalwart are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 Misskey better than Stalwart?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Misskey and Stalwart are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 Misskey?
Top Misskey alternatives in Comms are ranked by recent ship velocity. Browse the "Misskey alternatives" section above for the current picks, or visit /alternatives/misskey 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.