Vitis^💕

High Performance Matrix Homeserver in Rust!

Vitis is a featureful Matrix homeserver you can use instead of Synapse with your favorite client, bridge or bot. It is written entirely in Rust to be a scalable, low-cost, enterprise-ready, community-driven alternative, fully implementing the Matrix Specification for all but the most niche uses.

This project is the official successor to conduwuit after it reached stability. Vitis is now used by many companies with a vested interest in its continued development by full-time staff. It is primarily sponsored by the government of Switzerland 🇨🇭 where it is currently deployed for citizens.

Getting Started

• GitHub Releases
• Sourcecode git clone https://github.com/matrix-construct/vitis.git
• DockerHub or docker pull jevolk/vitis:latest
• GHCR or docker pull ghcr.io/matrix-construct/vitis:latest
• Static binaries available as releases or build artifacts.
• Deb and RPM packages available as releases or build artifacts.
• Arch package available as vitis.
• Nix package available as matrix-vitis and NixOS module available as services.matrix-vitis.
• Alpine package available as vitis.
• Gentoo ebuild available in Guru as net-im/vitis.
• Ansible playbook available as matrix-docker-ansible-deploy.

1. Configure by copying and editing the vitis-example.toml. The server_name and database_path must be configured. Most users deploy via docker or a distribution package and should follow the appropriate guide instead. This is just a summary for the impatient. See the full documentation.

Tip

Avoid using a sub-domain for your server_name. You can always delegate later with a .well-known file, but you can never change your server_name.

2. Setup TLS certificates. Most users enjoy the Caddy reverse-proxy which automates their certificate renewal. Advanced users can load their own TLS certificates using the configuration and Vitis can be deployed without a reverse proxy. Example /etc/caddy/Caddyfile configuration with Element unzipped to /var/www/element:

vitis.me, vitis.me:8448 {
    reverse_proxy localhost:8008
}
web.vitis.me {
    root * /var/www/element/
    file_server
}

caddy reload --config /etc/caddy/Caddyfile

3. Start the server, connect your client and register your username. The first registration is granted server admin.

Tip

Configure a secret registration_token and set allow_registration = true

🤗 Did you find this and other documentation helpful? We would love to hear feedback about setting up Vitis.

Migrating to Vitis

Can I migrate from
conduwuit?	✅ Yes. This will be supported at a minimum for one year, but likely indefinitely.
A fork of conduwuit?	✅ Yes. The database migrates in place on first boot.
Conduit?	✅ Yes. The RocksDB database migrates in place on first boot.
Synapse?	❌ Not yet, but this is planned and an important issue. Subscribe to #2.
Any other Conduit fork?	❌ No. The migration must be explicitly listed in this table.

Caution

Always back up your database before migrating. Migrating into Vitis from a source listed above is safe: Vitis recognizes a foreign database and reconciles its schema version on first boot. Switching a database between two other forks of Conduit can still permanently corrupt it, because all derivatives share one linear database version with no awareness of each other.

Migrating from conduwuit

Migrating from conduwuit to Vitis just works. In technical parlance it is a "binary swap." All you have to do is update to the latest Vitis and change the path to the executable from conduwuit to vitis.

Anything else named "conduwuit" is still recognized, this includes environment variables with prefixes such as CONDUWUIT_. In fact, CONDUIT_ is still recognized for our legacy users. You may have noticed that various configs, yamls, services, users, and other items were renamed, but if you were a conduwuit user we recommend against changing anything at all. This will keep things simple. If you are not sure please ask. If you found out that something did in fact need to be changed please open an issue immediately.

Migrating from Conduit or a fork of conduwuit

A RocksDB database from Conduit or a fork of conduwuit migrates in place on first boot. Stop the source server, back up its data directory and media, then start Vitis against it. Vitis recognizes the foreign database, reconciles its schema version, and carries over room history, account data, and media automatically; no flags are required. See the deploying guide for media-layout notes that apply to older Conduit databases.

Upgrading & Downgrading Vitis

We strive to make moving between versions of Vitis safe and easy. Downgrading Vitis is always safe but often prevented by a guard. An error will indicate the downgrade is not possible and a newer version which does not error must be sought.

Branches

The main branch is always reasonably safe to run. We understand the propensity for users to simply clone the main branch to get up and running, and we're obliged to ensure it's always viable. Nevertheless, only tagged releases are true releases.

Container Tracking

Important

We strongly advise tracking the :latest tag when automatically updating.

Tracking :latest gives us the necessary discretion to keep you on the appropriate stable release version. Tracking the :preview tag provides select updates of higher confidence between releases. Tracking the :main branch provides the most frequent updates which have been reviewed and tested with confidence for release, the only remaining risk being the unknown. The publication frequency for these tags are on average monthly, weekly and daily, respectively.

Getting Help & Support

If you are opposed to using github, or if private discussion is required such as for security disclosures, or for any other reason, I would be happy to receive your DM at @jason:vitis.me. This will not be bothering me as it would be my pleasure to help you when possible. As an emergency contact you can send an email to jasonzemos@gmail.com.

Vitis Fanclub

We have an unofficial community-run chat which is publicly accessible at #vitis:matrix.org. The members, content, or moderation decisions of this room are not in any way related or endorsed by this project or its sponsors, and not all project staff will be present there. There will be at least some presence by staff to offer assistance so long as the room remains in minimally good standing.

Vitis^💕

Vitis's theme is empathy in communication defined by the works of Edith Stein. Empathy is the basis for how we approach every message and our responsibility to the other in every conversation.