ToolScore

Matrix (Synapse)

Matrix.org · messaging · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-13

The structural exit: unlimited history you own, federation and E2EE on your own server — the backup trap dies when there is no third-party cloud, and the bill becomes a VPS plus your upkeep.

#2 of 7 in Messaging

Try Matrix (Synapse) for $0
Real price
$0 · OSS
open-source
Free tier
Yes
The software is $0; the bill is a VPS plus upkeep. No official sizing exists — the only official hardware guid
Limits
6.0/10
$0 software · VPS + upkeep · sizing “—” (community $25–60/mo)
Verdict
OWN THE SERVER
Unlimited history you own. No official sizing: “at least 1GB of free RAM” to join large public rooms is the on

ToolScore breakdown — why 66/100

Price / Value
6.5
Token & Rate Limits
6.0
Speed / Latency
5.0
Privacy & Retention
9.5
BYOK (Own API Key)
10.0
Output Quality
7.5
Stability
6.0
Ease of Setup
4.5
Billing Transparency
4.5
Support & Community
6.5

10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →

What it does well

  • ▸Unlimited history you own — no deletion clock, no retention page, no per-seat bill
  • ▸Federation with other servers + E2EE, with retention policy set by you
  • ▸The backup trap dies when there is no third-party cloud — you are the server
  • ▸Official install docs and admin tooling exist (installation guide, purge_media_cache admin API)

Where it costs you

  • ▸No official sizing exists — the only official guidance is “at least 1GB of free RAM” for large public rooms
  • ▸PostgreSQL strongly recommended (SQLite is “only acceptable for testing purposes”) — there is a right way and it is not the default
  • ▸Media cache needs pruning (purge_media_cache admin API) — maintenance is part of the price
  • ▸Federation is a moving target: expect maintenance

Hidden traps — the stuff the pricing page doesn't say

medium riskNo official sizing — budget “—”

Community estimates land near $25–60/mo for a federated community server, but that is unofficial, so the sizing cell stays “—”. The only official hardware guidance is “at least 1GB of free RAM” to join large public rooms — a floor, not a community-server spec.

medium riskSQLite is a testing-only shortcut

PostgreSQL is strongly recommended; SQLite is “only acceptable for testing purposes” per the official install docs. A small server started on SQLite carries a migration in its future.

low riskThe media cache grows until you prune it

Federated media accumulates and needs pruning via the purge_media_cache admin API. Unattended, disk usage is the limit that arrives first.

low riskConduit's “~512MB” is community folklore

Conduit/Continuwuity are lighter Rust homeservers for small single-community servers, but “lightweight” is community-repeated and the ~512MB memory figure isn't on an accessible official page — we don't publish it as a number.

Try Matrix (Synapse)

Know the limits before you pay: read the traps above, then decide with eyes open.

Visit official site

Affiliate link where available — never affects the score.

What the advertised price hides
The software is $0; the bill is a VPS plus upkeep. No official sizing exists — the only official hardware guidance is “at least 1GB of free RAM” to join large public rooms. Community estimates land near $25–60/mo for a federated community server (unofficial, so the cell stays “—”).

Closest alternatives

Matrix (Synapse) review

In-depth analysis · last updated 2026-11-13

The structural exit

Both traps in this hub — backup escrow and metadata retention — share one root: someone else's server. Matrix is the only path in the comparison that removes the root. Unlimited history you own, federation with other servers, E2EE, and a retention policy set by you instead of by a policy page. The price stops being per-seat and becomes a VPS plus upkeep; the backup trap dies when there is no third-party cloud.

The honest cost is “—”

The software is $0 and the sizing cell is empty — honestly. No official sizing exists; the only official hardware guidance is “at least 1GB of free RAM” to join large public rooms, which is a floor for joining, not a spec for hosting a community. Community estimates land near $25–60/mo for a federated community server; unofficial numbers stay “—” in this hub, so budget exploration, not a quote.

The ops reality behind the score

The official install docs are explicit about the right way: PostgreSQL is strongly recommended, and SQLite is “only acceptable for testing purposes”. Federated media accumulates and needs pruning via the purge_media_cache admin API. And federation itself is a moving target — expect maintenance. For smaller single-community servers, the Rust homeservers Conduit/Continuwuity are the lighter alternative, but “lightweight” is community-repeated and the ~512MB memory figure isn't on an accessible official page, so it stays out of our numbers.

How the pillars land

Federation/self-host 10: the ceiling of the pillar — you are the server. E2EE & metadata 9.5: E2EE plus retention you set yourself; the ledger lives on hardware you control. Feature set 7.5: federation, E2EE, unlimited history. Real limits 6: unlimited in principle, gated by your hardware and unwritten sizing. Price/Value 6.5: $0 software against real VPS + upkeep. Track record 6 and Ease of use 4.5: a moving-target federation and a PostgreSQL-and-pruning ops burden. Pricing transparency 4.5: no official sizing exists. Support & docs 6.5: official installation docs and documented admin APIs. Platforms & sync sits at the neutral 5 — not covered by this snapshot.

Verdict — 66/100, OWN THE SERVER

The only answer in this comparison for “who holds the archive and the ledger?” that ends with “you do”. Take it when the limits and the retention — not the price — are the problem, and go in expecting to be the operations team.

From the insights