Self-Hosted / Projects / Synapse
Synapse
StableSpecs verified October 3, 2026 · against v1.162.0
Overview
Self-hosted Matrix homeserver for federated chat and real-time communication.
Synapse is an open-source Matrix homeserver for people and organizations that want to run their own federated chat server, control user accounts and data, and communicate with other Matrix servers.
Why people choose Synapse
The practical search intent is a self-hosted alternative to centralized chat and community platforms. Synapse provides the server-side implementation for Matrix, so users can join rooms and communicate across the federation while the operator controls a distinct server name, local policy, authentication, and retention decisions.
What is included
Official documentation covers Matrix rooms, federation, user registration and authentication, media handling, the Client-Server and Federation APIs, an Admin API, modules, monitoring, structured logging, and worker processes for scaling. Clients such as Element connect to Synapse but are separate from the homeserver itself.
What to know before deployment
The server name is a foundational decision: the official installation guide says it determines the domain part of Matrix user IDs and how other servers reach yours. Production deployments also need PostgreSQL planning, reverse-proxy and federation configuration, media storage, backups, abuse controls, and upgrade discipline.
Best fit
Choose Synapse when you need a full-featured Matrix homeserver and federated communication. A smaller Matrix homeserver or hosted provider may be easier for a personal account, while Synapse is the established choice when administration, compatibility, and scaling options matter.
Interface previews
Screenshots of the Synapse interface.
Feature support
| Feature | Support |
|---|---|
| Matrix rooms and real-time messagingSynapse implements the Matrix homeserver side of rooms and real-time communication. | Supported |
| Federation with other Matrix serversFederation is a core Matrix capability, with configuration and reachability requirements. | Supported |
| User registration and authenticationOfficial docs cover registration, authentication configuration, and optional single sign-on. | Supported |
| Media uploads and storageHomeserver deployments handle media, with storage and retention choices owned by the operator. | Supported |
| Client-Server and Federation APIsSynapse exposes the Matrix APIs required by compatible clients and federated servers. | Supported |
| Admin API and pluggable modulesOfficial administration documentation covers the Admin API and modules. | Supported |
| PostgreSQL production databaseThe official docs provide PostgreSQL setup guidance for production-style deployments. | Supported |
| Docker deploymentSynapse publishes container deployment material, while native installation paths are also documented. | Supported |
| Worker-process scalingWorkers can scale Synapse, but require additional architecture and operational tuning. | Partial support |
Community signals
- Stars
- 4.7k
- Forks
- 636
- Open issues
- 2.1k
- Last commit
- 2d ago
- Latest release
- v1.162.0
- Repo created
- Dec 2023
Includes open pull requests
2w ago
Refreshed nightly from the GitHub API.
Questions
What is Synapse used for?
Synapse is used to run a Matrix homeserver for accounts, rooms, real-time chat, media, federation, authentication, and server administration.
Is Synapse a self-hosted alternative to Slack or Discord?
It can serve as a self-hosted and federated chat alternative, but Matrix is a protocol ecosystem rather than one centralized service. Synapse is the homeserver, and clients such as Element are separate.
What is the Matrix server name and why does it matter?
The server name determines the domain portion of Matrix user IDs and affects how other Matrix servers reach your homeserver, so the official installation guide recommends choosing it carefully before installation.
Does Synapse need PostgreSQL?
The official documentation provides PostgreSQL guidance and recommends it for production deployments; small test setups may use SQLite with limitations.
Can Synapse run in Docker?
Yes. Synapse provides container deployment options, but production operators still need persistent media, database, reverse proxy, federation, backups, and upgrade planning.
Does Synapse support federation?
Yes. Federation is a core Matrix feature, but it requires correct server naming, DNS, TLS, and network reachability.
What is the main tradeoff with self-hosting Synapse?
You gain control and interoperability across Matrix, but you take responsibility for a real homeserver: databases, media, abuse handling, federation, monitoring, backups, and upgrades.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.