Introduction
Trioditis (“of the three roads”) is an open-source, self-hosted universal messaging hub: one fast, cohesive app for every messaging network you use, running on infrastructure you own.
Anyone can spin up a Trioditis server and invite family, friends, or teammates. Each member has their own account, connects their own messaging networks, and holds the keys to their own stored message history.
Design principles
Section titled “Design principles”- Your server, your data. Bridges and storage run on the operator’s hardware. Nothing in the message path relies on a third-party hosted bridge cloud.
- Sealed by default. Stored message content, media, chat names, and contact profiles are encrypted to each member’s own keys before reaching the database. Operators can administer and back up the server without reading anyone’s history.
- Reliability over features. No silently lost messages, no hidden duplicates, and an honest
unknowndelivery state whenever a network outcome is ambiguous. Bridge health is always visible. - Simple to operate. One installer script sets up and upgrades the stack on any Linux box, VM, Proxmox VE host, or VPS across
x86_64andarm64, with built-in automatic updates, encrypted backups, and one-command restore. - Native-feeling everywhere. Shared logic and crypto in one monorepo; platform-appropriate UI on desktop/web and mobile rather than lowest-common-denominator wrappers.
- Instant by default. Clients are designed to open directly to your inbox from an encrypted local cache before the network responds.
- Built to expand. Every messaging network plugs into the same
bridgev2connector contract, advertises its capabilities, uses a single generic login stepper, and passes the same conformance suite. - Agents are first-class, and on a leash. External AI agents appear as conversations, authenticate via OAuth 2.1 over MCP, start with zero access, and act only within explicit per-chat grants and human approvals.
Supported networks
Section titled “Supported networks”Trioditis currently ships bridge hosts for 12 messaging networks. Admins choose which ones to offer inside Admin settings → Networks without touching server config.
| Network | ID | Current maturity | Sign-in flow | Platform ToS risk |
|---|---|---|---|---|
whatsapp |
Stable | QR code or phone pairing code | No | |
| Signal | signal |
Experimental | Link a device (QR) | No |
| Google Messages | gmessages |
Beta | Sign in with Google + phone emoji tap | No |
| Google Voice | gvoice |
Experimental | Sign in with Google | Yes |
| Telegram | telegram |
Beta | QR code or phone number (requires Telegram API ID/hash) | No |
| Messenger | meta |
Beta | Sign in on facebook.com / messenger.com | Yes |
instagram |
Beta | Sign in on instagram.com | Yes | |
| Slack | slack |
Experimental | Sign in on slack.com, email code, or bot app | Yes |
| GroupMe | groupme |
Experimental | Access token or email/phone & password | No |
linkedin |
Experimental | Sign in on linkedin.com | Yes | |
| X | twitter |
Experimental | Sign in on x.com | Yes |
| Bluesky | bluesky |
Experimental | App password (with DM access) | No |
Discord awaits upstream mautrix-discord’s migration to bridgev2. See the Networks guides for per-network implementation status, unsupported features, and setup steps.
Licensing
Section titled “Licensing”Trioditis is licensed under the AGPL-3.0.
It depends on the self-hosted Convex backend, which is source-available under FSL-1.1-Apache-2.0 (converting to Apache-2.0 after two years) and runs unmodified as a separate service in the Docker Compose bundle.