open source · end-to-end encrypted · yours
Messaging you can own, down to the name on the icon.
Xoyo is a self-hosted messaging platform built on the Matrix protocol. Run it on your own server, keep conversations end-to-end encrypted, and ship the apps under your own brand — this very site is wearing the same brand-config layer the apps use. Try the dots in the header.
- So what actually makes this different?
- It runs on our server. Nobody in the middle.
- And every message looks like this to anyone else:
- AwgAEnBv9k2xLqm4TZ08c/Vf1uHqJ7Rye3PdN5sYAoQiWlkgB6mtC0z8XrD4h1UwKfEjSGa2
- Exactly. That’s the whole point.
Three promises, enforced by architecture
Encrypted by default
Every direct conversation uses Matrix’s Olm/Megolm end-to-end encryption, with multi-device key sync. When a room is ever bridged to an external service, the UI says so plainly — we don’t imply privacy we can’t deliver.
Self-hosted, not rented
The homeserver, the database, the media store — all on infrastructure you control. Our entire dev environment is reproducible from scripts in the repo; yours can be too.
White-label from day one
App name, icon, splash, colors, and bundle IDs live in a typed brand config, not in the code. One codebase, any number of branded apps. Xoyo itself is just the reference brand.
Real, and honestly early
The backend core — accounts, 1:1 messaging, encryption, media, push fan-out — is built and tested. The web client is taking shape; mobile is next. The roadmap shows exactly where every piece stands, by task, with nothing rounded up.