[ This is a mirror, official repo: https://github.com/matrix-org/dendrite ] Dendrite is a second-generation Matrix homeserver written in Go! https://matrix-org.github.io/dendrite/
You cannot 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
Till 234ed603e6
Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026)
Doesn't buy us much, but makes everything a bit more consistent.

Also removes the SQL trace driver, as it is unused and the output is
hard to read anyway.
1 day ago
.github Upload covdatafiles for each server 2 days ago
appservice Remove `BaseDendrite` (#3023) 3 days ago
build Update Go, use go tool covdata for coverage files? 2 days ago
clientapi Remove `BaseDendrite` (#3023) 3 days ago
cmd Remove `BaseDendrite` (#3023) 3 days ago
docs Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
federationapi Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
helm Version 0.12.0 (#3009) 2 weeks ago
internal Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
mediaapi Remove `BaseDendrite` (#3023) 3 days ago
relayapi Remove `BaseDendrite` (#3023) 3 days ago
roomserver Remove `BaseDendrite` (#3023) 3 days ago
setup Remove `BaseDendrite` (#3023) 3 days ago
syncapi Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
test Update Go, use go tool covdata for coverage files? 2 days ago
userapi Remove `BaseDendrite` (#3023) 3 days ago
.dockerignore Docker Hub (#1053) 3 years ago
.gitignore Initial Store & Forward Implementation (#2917) 2 months ago
.golangci.yml Increase gocyclo complexity to 25 (and remove all but 2 golint directives related to it) (#1783) 2 years ago
CHANGES.md Version 0.12.0 (#3009) 2 weeks ago
Dockerfile Remove polylith/API mode (#2967) 1 month ago
LICENSE Add Apache Version 2.0 license and headers to all golang files 6 years ago
README.md Updated instructions and references to monolith to their new names (#2994) 3 weeks ago
are-we-synapse-yet.list AWSY missing federation tests (#2943) 2 months ago
are-we-synapse-yet.py Add Are We Synapse Yet to GHA (#2321) 12 months ago
build-dendritejs.sh Add startup testing for Wasm Pinecone build (#1910) 2 years ago
build.cmd build.sh to build.cmd (#2319) 12 months ago
build.sh Disable WebAssembly builds for now 9 months ago
dendrite-sample.yaml Change default stats reporting endpoint (#3007) 2 weeks ago
go.mod Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
go.sum Move every `db.Prepare` to `sqlutil.Statementlist`, remove trace driver (#3026) 1 day ago
run-sytest.sh Use /usr/bin/env bash in shebangs to make them universal (#2735) 6 months ago
show-expected-fail-tests.sh Use /usr/bin/env bash in shebangs to make them universal (#2735) 6 months ago
sytest-blacklist Use `t.TempDir` for SQLite databases, so tests don't rip out each others databases (#2950) 2 months ago
sytest-whitelist Use `t.TempDir` for SQLite databases, so tests don't rip out each others databases (#2950) 2 months ago
test-dendritejs.sh Add startup testing for Wasm Pinecone build (#1910) 2 years ago



Build status Dendrite Dendrite Dev

Dendrite is a second-generation Matrix homeserver written in Go. It intends to provide an efficient, reliable and scalable alternative to Synapse:

  • Efficient: A small memory footprint with better baseline performance than an out-of-the-box Synapse.
  • Reliable: Implements the Matrix specification as written, using the same test suite as Synapse as well as a brand new Go test suite.
  • Scalable: can run on multiple machines and eventually scale to massive homeserver deployments.

Dendrite is beta software, which means:

  • Dendrite is ready for early adopters. We recommend running in Monolith mode with a PostgreSQL database.
  • Dendrite has periodic releases. We intend to release new versions as we fix bugs and land significant features.
  • Dendrite supports database schema upgrades between releases. This means you should never lose your messages when upgrading Dendrite.

This does not mean:

  • Dendrite is bug-free. It has not yet been battle-tested in the real world and so will be error prone initially.
  • Dendrite is feature-complete. There may be client or federation APIs that are not implemented.
  • Dendrite is ready for massive homeserver deployments. There is no sharding of microservices (although it is possible to run them on separate machines) and there is no high-availability/clustering support.

Currently, we expect Dendrite to function well for small (10s/100s of users) homeserver deployments as well as P2P Matrix nodes in-browser or on mobile devices.

If you have further questions, please take a look at our FAQ or join us in:


See the Planning your Installation page for more information on requirements.

To build Dendrite, you will need Go 1.18 or later.

For a usable federating Dendrite deployment, you will also need:

  • A domain name (or subdomain)
  • A valid TLS certificate issued by a trusted authority for that domain
  • SRV records or a well-known file pointing to your deployment

Also recommended are:

  • A PostgreSQL database engine, which will perform better than SQLite with many users and/or larger rooms
  • A reverse proxy server, such as nginx, configured like this sample

The Federation Tester can be used to verify your deployment.

Get started

If you wish to build a fully-federating Dendrite instance, see the Installation documentation. For running in Docker, see build/docker.

The following instructions are enough to get Dendrite started as a non-federating test deployment using self-signed certificates and SQLite databases:

$ git clone https://github.com/matrix-org/dendrite
$ cd dendrite
$ ./build.sh

# Generate a Matrix signing key for federation (required)
$ ./bin/generate-keys --private-key matrix_key.pem

# Generate a self-signed certificate (optional, but a valid TLS certificate is normally
# needed for Matrix federation/clients to work properly!)
$ ./bin/generate-keys --tls-cert server.crt --tls-key server.key

# Copy and modify the config file - you'll need to set a server name and paths to the keys
# at the very least, along with setting up the database connection strings.
$ cp dendrite-sample.yaml dendrite.yaml

# Build and run the server:
$ ./bin/dendrite --tls-cert server.crt --tls-key server.key --config dendrite.yaml

# Create an user account (add -admin for an admin user).
# Specify the localpart only, e.g. 'alice' for '@alice:domain.com'
$ ./bin/create-account --config dendrite.yaml --username alice

Then point your favourite Matrix client at http://localhost:8008 or https://localhost:8448.


We use a script called Are We Synapse Yet which checks Sytest compliance rates. Sytest is a black-box homeserver test rig with around 900 tests. The script works out how many of these tests are passing on Dendrite and it updates with CI. As of January 2023, we have 100% server-server parity with Synapse, and the client-server parity is at 93% , though check CI for the latest numbers. In practice, this means you can communicate locally and via federation with Synapse servers such as matrix.org reasonably well, although there are still some missing features (like SSO and Third-party ID APIs).

We are prioritising features that will benefit single-user homeservers first (e.g Receipts, E2E) rather than features that massive deployments may be interested in (OpenID, Guests, Admin APIs, AS API). This means Dendrite supports amongst others:

  • Core room functionality (creating rooms, invites, auth rules)
  • Room versions 1 to 10 supported
  • Backfilling locally and via federation
  • Accounts, profiles and devices
  • Published room lists
  • Typing
  • Media APIs
  • Redaction
  • Tagging
  • Context
  • E2E keys and device lists
  • Receipts
  • Push
  • Guests
  • User Directory
  • Presence
  • Fulltext search


We would be grateful for any help on issues marked as Are We Synapse Yet. These issues all have related Sytests which need to pass in order for the issue to be closed. Once you've written your code, you can quickly run Sytest to ensure that the test names are now passing.

If you're new to the project, see our Contributing page to get up to speed, then look for Good First Issues. If you're familiar with the project, look for Help Wanted issues.