You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Patrick Cloke 2a234b788e
Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15350)
21 hours ago
.ci Add developer documentation for the Federation Sender and add a documentation mechanism using Sphinx. (#15265) 7 days ago
.github Speed up generate sample config CI lint (#15340) 3 days ago
changelog.d Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15350) 21 hours ago
contrib Make it easier to use DataGrip w/ Synapse's schema (#14982) 1 month ago
debian 1.80.0 3 days ago
demo demo: check if we are in a virtualenv before overriding PYTHONPATH (#12916) 10 months ago
dev-docs Add developer documentation for the Federation Sender and add a documentation mechanism using Sphinx. (#15265) 7 days ago
docker Load `/password_policy` endpoint on workers. (#15331) 4 days ago
docs Add the ability to enable/disable registrations when in the OIDC flow (#14978) 1 day ago
rust Stabilize support for MSC3873: disambuguated event push keys. (#15190) 3 weeks ago
scripts-dev Add developer documentation for the Federation Sender and add a documentation mechanism using Sphinx. (#15265) 7 days ago
stubs Use immutabledict instead of frozendict (#15113) 1 week ago
synapse Set thread_id column to non-null for event_push_{actions,actions_staging,summary} (#15350) 21 hours ago
synmark Bump black from 22.12.0 to 23.1.0 (#15103) 1 month ago
tests to_device updates could be dropped when consuming the replication stream (#15349) 22 hours ago
.codecov.yml Disable codecov reports to GH comments. 4 years ago
.coveragerc Fix coverage in sytest and use plugins for buildkite (#5922) 4 years ago
.dockerignore Fix pinning Rust deps in docker images (#14129) 6 months ago
.editorconfig Apply correct editorconfig to .pyi files (#14526) 4 months ago
.git-blame-ignore-revs Update .git-blame-ignore-revs for #15103. 1 month ago
.gitignore Fix `.gitignore` rule for the Complement source tarball downloaded automatically by ``. (#15319) 7 days ago
.rustfmt.toml Port the push rule classes to Rust. (#13768) 6 months ago
AUTHORS.rst Automatically delete empty groups/communities (#6453) 3 years ago 1.80.0 3 days ago Advertise docs (#10595) 2 years ago
Cargo.lock Bump regex from 1.7.1 to 1.7.3 (#15325) 4 days ago
Cargo.toml Add a stub Rust crate (#12595) 7 months ago Fix broken links in (#10331) 2 years ago
LICENSE Reference Matrix Home Server 9 years ago
README.rst fix grammar 7 months ago
UPGRADE.rst fix broken link to upgrade notes (#10631) 2 years ago
book.toml Compile and render Synapse's docs into a browsable, mobile-friendly and searchable website (#10086) 2 years ago Always build Rust extension in release mode (#14009) 6 months ago
mypy.ini Add missing type hints to ``. (#15230) 3 weeks ago
poetry.lock Bump ruff from 0.0.252 to 0.0.259 (#15328) 3 days ago
pylint.cfg Added pylint config file: ignore missing-docstring messages. 9 years ago
pyproject.toml Merge branch 'master' into develop 3 days ago
sytest-blacklist Back out implementation of MSC2314 (#12474) 12 months ago
tox.ini Run lints under poetry in CI; remove lint tox jobs (#12434) 12 months ago


Synapse |support| |development| |documentation| |license| |pypi| |python|

Synapse is an open-source `Matrix <>`_ homeserver written and
maintained by the Foundation. We began rapid development in 2014,
reaching v1.0.0 in 2019. Development on Synapse and the Matrix protocol itself continues
in earnest today.

Briefly, Matrix is an open standard for communications on the internet, supporting
federation, encryption and VoIP. has more to say about the `goals of the
Matrix project <>`_, and the `formal specification
<>`_ describes the technical details.

.. contents::

Installing and configuration

The Synapse documentation describes `how to install Synapse <>`_. We recommend using
`Docker images <>`_ or `Debian packages from

.. _federation:

Synapse has a variety of `config options
which can be used to customise its behaviour after installation.
There are additional details on how to `configure Synapse for federation here

.. _reverse-proxy:

Using a reverse proxy with Synapse

It is recommended to put a reverse proxy such as
`nginx <>`_,
`Apache <>`_,
`Caddy <>`_,
`HAProxy <>`_ or
`relayd <>`_ in front of Synapse. One advantage of
doing so is that it means that you can expose the default https port (443) to
Matrix clients without needing to run Synapse with root privileges.
For information on configuring one, see `the reverse proxy docs

Upgrading an existing Synapse

The instructions for upgrading Synapse are in `the upgrade notes`_.
Please check these instructions as upgrading may require extra steps for some
versions of Synapse.

.. _the upgrade notes:

Platform dependencies

Synapse uses a number of platform dependencies such as Python and PostgreSQL,
and aims to follow supported upstream versions. See the
`deprecation policy <>`_
for more details.

Security note

Matrix serves raw, user-supplied data in some APIs -- specifically the `content
repository endpoints`_.

.. _content repository endpoints:

Whilst we make a reasonable effort to mitigate against XSS attacks (for
instance, by using `CSP`_), a Matrix homeserver should not be hosted on a
domain hosting other web applications. This especially applies to sharing
the domain with Matrix web clients and other sensitive applications like
webmail. See for more

.. _CSP:

Ideally, the homeserver should not simply be on a different subdomain, but on
a completely different `registered domain`_ (also known as top-level site or
eTLD+1). This is because `some attacks`_ are still possible as long as the two
applications share the same registered domain.

.. _registered domain:

.. _some attacks:

To illustrate this with an example, if your Element Web or other sensitive web
application is hosted on ````, you should ideally host Synapse on
````. Some amount of protection is offered by hosting on
```` instead, so this is also acceptable in some scenarios.
However, you should *not* host your Synapse on ````.

Note that all of the above refers exclusively to the domain used in Synapse's
``public_baseurl`` setting. In particular, it has no bearing on the domain
mentioned in MXIDs hosted on that server.

Following this advice ensures that even if an XSS is found in Synapse, the
impact to other applications will be minimal.

Testing a new installation

The easiest way to try out your new Synapse installation is by connecting to it
from a web client.

Unless you are running a test instance of Synapse on your local machine, in
general, you will need to enable TLS support before you can successfully
connect from a client: see
`TLS certificates <>`_.

An easy way to get started is to login or register via Element at or respectively.
You will need to change the server you are logging into from ````
and instead specify a Homeserver URL of ``https://<server_name>:8448``
(or just ``https://<server_name>`` if you are using a reverse proxy).
If you prefer to use another client, refer to our
`client breakdown <>`_.

If all goes well you should at least be able to log in, create a room, and
start sending messages.

.. _`client-user-reg`:

Registering a new user from a client

By default, registration of new users via Matrix clients is disabled. To enable

1. In the
   `registration config section <>`_
   set ``enable_registration: true`` in ``homeserver.yaml``.
2. Then **either**:

   a. set up a `CAPTCHA <>`_, or
   b. set ``enable_registration_without_verification: true`` in ``homeserver.yaml``.

We **strongly** recommend using a CAPTCHA, particularly if your homeserver is exposed to
the public internet. Without it, anyone can freely register accounts on your homeserver.
This can be exploited by attackers to create spambots targetting the rest of the Matrix

Your new user name will be formed partly from the ``server_name``, and partly
from a localpart you specify when you create the account. Your name will take
the form of::

(pronounced "at localpart on my dot domain dot name").

As when logging in, you will need to specify a "Custom server".  Specify your
desired ``localpart`` in the 'User name' box.

Troubleshooting and support

The `Admin FAQ <>`_
includes tips on dealing with some common problems. For more details, see
`Synapse's wider documentation <>`_.

For additional support installing or managing Synapse, please ask in the community
support room |room|_ (from a account if necessary). We do not use GitHub
issues for support requests, only for bug reports and feature requests.

.. |room| replace:: ````
.. _room:

.. |docs| replace:: ``docs``
.. _docs: docs

Identity Servers

Identity servers have the job of mapping email addresses and other 3rd Party
IDs (3PIDs) to Matrix user IDs, as well as verifying the ownership of 3PIDs
before creating that mapping.

**They are not where accounts or credentials are stored - these live on home
servers. Identity Servers are just for mapping 3rd party IDs to matrix IDs.**

This process is very security-sensitive, as there is obvious risk of spam if it
is too easy to sign up for Matrix accounts or harvest 3PID data. In the longer
term, we hope to create a decentralised system to manage it (`matrix-doc #712
<>`_), but in the meantime,
the role of managing trusted identity in the Matrix ecosystem is farmed out to
a cluster of known trusted ecosystem partners, who run 'Matrix Identity
Servers' such as `Sydent <>`_, whose role
is purely to authenticate and track 3PID logins and publish end-user public

You can host your own copy of Sydent, but this will prevent you reaching other
users in the Matrix ecosystem via their email address, and prevent them finding
you. We therefore recommend that you use one of the centralised identity servers
at ```` or ```` for now.

To reiterate: the Identity server will only be used if you choose to associate
an email address with your account, or send an invite to another user via their
email address.


We welcome contributions to Synapse from the community!
The best place to get started is our
`guide for contributors <>`_.
This is part of our larger `documentation <>`_, which includes

information for Synapse developers as well as Synapse administrators.
Developers might be particularly interested in:

* `Synapse's database schema <>`_,
* `notes on Synapse's implementation details <>`_, and
* `how we use git <>`_.

Alongside all that, join our developer community on Matrix:
` <>`_, featuring real humans!

.. |support| image::
  :alt: (get support on

.. |development| image::
  :alt: (discuss development on

.. |documentation| image::
  :alt: (Rendered documentation on GitHub Pages)

.. |license| image::
  :alt: (check license in LICENSE file)
  :target: LICENSE

.. |pypi| image::
  :alt: (latest version released on PyPi)

.. |python| image::
  :alt: (supported python versions)