Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A Matrix homeserver written in Rust, the official successor to conduwuit, that works with any Matrix client, bridge or bot and federates with other servers. It stores everything in an embedded RocksDB database, so there is no PostgreSQL or Redis to run alongside it, and it aims to be low-cost to run.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (31 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Tuwunel when you want a Matrix homeserver that runs as one Rust process with no database server beside it. It is Apache-2.0, the official successor to conduwuit, and positions itself as a homeserver you can use instead of Synapse with any Matrix client, bridge or bot. The snippet pins `jevolk/tuwunel:v1.9.4` from Docker Hub (the same release is on GHCR), published 2026-10-10, and adapts the project's `docs/deploying/docker-compose.yml` with a generated registration token. Data lives in an embedded RocksDB directory, so the stack is a single container, where Synapse in this catalog is Python with PostgreSQL or SQLite. Upstream publishes no RAM minimum, so our 512 MB floor is an estimate; the catalog's Synapse entry uses 1 GB. Tuwunel is a homeserver only: it has no chat web app of its own, so users bring Element or another client. Compared with Mattermost, Zulip and Rocket.Chat, which are complete team-chat products, it is the protocol-level choice, and it is the one to take if your priority is a small federated Matrix server.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Tuwunel — Matrix homeserver — adapted from the project's docs/deploying/docker-compose.yml, pinned to v1.9.4
mkdir tuwunel && cd tuwunel
echo "REGISTRATION_TOKEN=$(openssl rand -hex 16)" > .env
# server name is permanent (it becomes every user ID, @alice:matrix.example.com); set your real domain before the first start
cat > docker-compose.yml <<'EOF'
services:
homeserver:
image: jevolk/tuwunel:v1.9.4
restart: unless-stopped
stop_grace_period: 30m
ports:
- "8008:6167"
volumes:
- db:/var/lib/tuwunel
environment:
TUWUNEL_SERVER_NAME: matrix.example.com
TUWUNEL_DATABASE_PATH: /var/lib/tuwunel
TUWUNEL_PORT: 6167
TUWUNEL_ADDRESS: 0.0.0.0
TUWUNEL_ALLOW_REGISTRATION: 'true'
TUWUNEL_REGISTRATION_TOKEN: ${REGISTRATION_TOKEN}
TUWUNEL_ALLOW_FEDERATION: 'true'
TUWUNEL_TRUSTED_SERVERS: '["matrix.org"]'
volumes:
db:
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:8008/_matrix/client/versions; do sleep 3; done'
# → http://SERVER_IP:8008 (a homeserver API, not a web app: point a Matrix client such as Element at it and register with the token in .env; federation needs a real domain with TLS in front)Tuwunel's Docker documentation flags several things you should settle before users arrive:
Tuwunel used 31 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
The Tuwunel install snippet is marked verified on Ubuntu 26.04 (Nov 2026).