← Back to home
Comparison · Comms

Synapse vs Matrix

Side-by-side trajectory, velocity, and editorial themes.

S
Synapse
COMMS
5.0

Synapse holds its biweekly cadence, grinding through Matrix spec MSCs

◆ Current state

Synapse is the reference Matrix homeserver, shipping on a steady two-week release train. Recent work centers on Simplified Sliding Sync (MSC4186), sticky events, cancellable delayed events, and a preview-URL capabilities API, alongside a run of federation and to-device stability fixes. This is maintenance-heavy engineering: paired rc/stable releases, a mid-May CVE security patch in 1.152.1, and Debian 12 packaging now being retired.

◆ Where it's heading

The arc is incremental spec conformance, not new direction. Sliding Sync and appservice/ephemeral-event plumbing are maturing toward Matrix 1.15 requirements, with repeated fix-and-stabilize cycles (one Sliding Sync change was reverted for performance and re-landed). Expect continued MSC pickups and hardening rather than architectural change.

◆ Prediction

The next release likely stabilizes more Sliding Sync and sticky-event behavior and continues trimming legacy packaging, arriving as another rc-then-stable pair within roughly two weeks.

M
Matrix
COMMS
6.3

Matrix 1.19 lands encrypted room history sharing and custom emoji, clearing a multi-year MSC backlog

◆ Current state

Matrix ships a spec release roughly quarterly and reports weekly via This Week in Matrix. The ecosystem is mid-transition to Matrix 2.0, where simplified sliding sync and closing E2EE gaps are the dominant threads. Version 1.19 is the headline event of this window; the rest is community, governance, and ecosystem reporting.

◆ Where it's heading

The spec is working through a long-pending MSC backlog: image packs merged, simplified sliding sync accepted, and now encrypted history sharing standardized. Each release chips at features that clients (Element X, FluffyChat, Cinny, Nheko) already shipped ahead of the spec, pulling the ecosystem toward a common Matrix 2.0 baseline.

◆ Prediction

Expect the E2EE-related sliding-sync extension MSCs to be the next priority, since simplified sliding sync is accepted but won't land in a spec release until enough extensions (several supporting encrypted messaging) are also accepted.

See more alternatives to Synapse
See more alternatives to Matrix