Comparisons anchored on Matrix, the open federated messaging protocol, and Synapse, its AGPL-3.0 homeserver developed by Element, covering how Matrix deployments are built and scaled.
When a self-hosted Matrix homeserver can run Synapse as a single monolith process and when to split it into workers. Covers the Redis and PostgreSQL that workers require, the generic worker and stream writers, the reverse proxy routing that workers add, and the operating effort against the throughput gained.
Whether a self-hosted Matrix deployment can run Element's free ESS Community distribution or needs ESS Pro: the 100-user and non-commercial positioning of Community, Element's Cyber Resilience Act and production warnings, and what Pro adds with Synapse Pro, LTS releases, LDAP and SCIM, auditing, retention, high availability and air-gapped support.
Element's two homeservers today: Synapse, actively developed with workers and Redis replication, against Dendrite, now in maintenance mode without clustering or Element X support, with a clear verdict for new deployments.
The Python reference homeserver against the Rust successor to conduwuit backed by the Swiss government: resource use, database choices, licensing (AGPL against Apache-2.0), feature coverage and the missing migration path from Synapse.
Two open messaging standards: Matrix's replicated rooms over HTTP JSON APIs against XMPP's RFC 6120 message passing with extensions, compared on federation, encryption, server choices and bridges, with a verdict for an organization picking one.
Element's Helm-based Element Server Suite Community on K3s or Kubernetes against installing Synapse, MAS and Element Web yourself: what is bundled, licensing limits on non-commercial use, upgrades and when ESS Pro becomes the real choice.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.