← Back to home
Comparison · Comms

Matrix vs Stalwart

A side-by-side editorial comparison of Matrix and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.

Matrix vs Stalwart: at a glance

FeatureMatrixStalwart
SectorCommsComms
Velocity score5.05.0
Sparks · 30d00
Top themesprotocol-spec, msc-process, community-newsletter, local-firstmail-server, jmap, imap, rfc-compliance
Last editorial update3d ago20h ago
WebsiteVisit →Visit →

What is Matrix?

Matrix ships spec, not product — the MSC queue keeps filling while nothing reaches final comment

The weekly newsletter is the whole feed, and its shape barely varies: a Matrix Live episode, community events, and a spec roundup. This week brings three new MSCs — an incompatible-server error code, state event power levels, and OAuth 2.0 refresh token error handling — with nothing in final comment period and nothing accepted. The 08-14 issue leads on local-first Matrix and FrOSCon.

Read the full Matrix trajectory →

What is Stalwart?

Stalwart is chasing mail RFCs and its own storage layer at the same time

Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.

Read the full Stalwart trajectory →

Matrix vs Stalwart: editorial side-by-side

M
Matrix
COMMS
5.0

Matrix ships spec, not product — the MSC queue keeps filling while nothing reaches final comment

◆ Current state

The weekly newsletter is the whole feed, and its shape barely varies: a Matrix Live episode, community events, and a spec roundup. This week brings three new MSCs — an incompatible-server error code, state event power levels, and OAuth 2.0 refresh token error handling — with nothing in final comment period and nothing accepted. The 08-14 issue leads on local-first Matrix and FrOSCon.

◆ Where it's heading

Proposals are accumulating faster than they are being resolved. Several consecutive issues now report new MSCs opened with an empty FCP list and no acceptances, which is what a spec process looks like when authorship outruns review capacity. The substantive engineering themes running underneath are local-first and peer-to-peer Matrix, and homeserver decentralisation — both discussed in talks rather than landed in the spec.

◆ Prediction

The next issues should keep adding MSCs at a similar rate; the thing to watch is whether any of the newer proposals reach final comment period, since none has in the recent run. Note that this feed truncates at 8000 characters, so server and client release news further down each issue may fall outside what is visible here.

S5.0

Stalwart is chasing mail RFCs and its own storage layer at the same time

◆ Current state

Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.

◆ Where it's heading

Two threads run through every release. One is RFC coverage across IMAP, JMAP, CalDAV and WebDAV, implemented close to the specification including drafts. The other is a long tail of protocol-conformance fixes, many of them cases where JMAP and IMAP disagreed about the same state. The newest release adds a third: memory and scheduling limits, which is what a server codebase starts doing when deployments get large enough for defaults to hurt.

◆ Prediction

Expect continued RFC additions across the JMAP and IMAP surfaces, with more of the storage-tuning work that v0.16.18 started as RocksDB deployments scale.

Alternatives to Matrix 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 Matrix or Stalwart.

See all Matrix alternatives → · See all Stalwart alternatives →

Recent activity from Matrix and Stalwart

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoStalwartResource limits arrive for inbound reports and RocksDB caches
  2. 4d agoMatrixWeekly spec update: three new MSCs, none accepted or in FCP
  3. 8d agoStalwartIMAP gains UIDONLY, UIDBATCHES and message-limit extensions
  4. 11d agoMatrixMatrix Live on Continuwuity; local-first Matrix talk published
  5. 16d agoStalwartJMAP delivery push arrives; strict relays stop rejecting calendar mail
  6. 18d agoMatrixCommunity workation in Krems set for 22 August to 13 September
  7. 23d agoStalwartFix-only release: JMAP semantics and a credential escalation
  8. 25d agoMatrixMatrix Live: Homeserver Decentralisation Working Group
  9. 29d agoStalwartVAPID lands for JMAP Web Push
  10. 1mo agoMatrixWeekly spec update: seven new MSCs, global spec versioning
  11. 1mo agoStalwartFreeBSD support, plus OAuth scopes for IMAP, SMTP and Sieve
  12. 1mo agoMatrixWeekly spec update: moderation policy servers, rooms as pages

Frequently asked questions

What is the difference between Matrix and Stalwart?

They serve adjacent needs but don't currently overlap on shipped themes. Matrix and Stalwart 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 Matrix better than Stalwart?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Matrix and Stalwart 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 Matrix?

Top Matrix alternatives in Comms are ranked by recent ship velocity. Browse the "Matrix alternatives" section above for the current picks, or visit /alternatives/matrix 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.