Matrix clients you can't recommend
The protocol is solid; the clients are clunky. You won't put Element in front of a non-technical friend.
Open source · Matrix-native
No black box. Federated on Matrix, AGPLv3, keyboard-first — bring your own server or build on ours.
You know the problem isn't the protocol.
The protocol is solid; the clients are clunky. You won't put Element in front of a non-technical friend.
The pretty ones aren't federated, aren't E2EE, can't be self-hosted — pick your compromise.
You've been burned before: promising projects abandoned, and your migration wasted.
The short version, for people who read the docs first.
# Self-host CORAX on your own Matrix homeserver
docker run -d --name corax \
-e HOMESERVER=https://matrix.example.org \
-p 8008:8008 ghcr.io/corax/server:latest
# …or bring your own client — it's just Matrix
curl https://matrix.example.org/_matrix/client/versionsOpen code, documented process. No black box.
AGPLv3-licensed code, public roadmap, transparent governance backed by a French non-profit. Anyone can audit, fork or contribute.
Built on Matrix. Federated, no single point of failure, self-hostable.
Hundreds of independent servers already federate over Matrix. If one goes down, the network keeps running — and you can self-host yours.
Encryption by default. Nobody can read your messages.
Olm and Megolm protocols — the same battle-tested cryptography behind Element. Keys never leave your device.
Switch clients without losing a thing. Your identity stays yours.
Export your full history with one click and import it into another Matrix client. Your contacts, rooms and identity follow you.
Join the waitlist, or follow the roadmap and open issues as we build in the open.