Skip to content

Networks Overview

Each messaging network runs as its own isolated Go bridge-host process implementing mautrix bridgev2’s NetworkConnector. By default, a self-hosted server builds and starts all 12 bridge hosts, and admins enable or disable networks for members inside Admin settings → Networks without restarting the server.

Every network carries a visible maturity label (stable, beta, or experimental) in the app and is tested against Trioditis’s bridge host checks.

Network ID Maturity Implementation status Login flows ToS risk
WhatsApp whatsapp Stable Primary network; full bridge + live pairing/messaging QR code, phone pairing code No
Signal signal Experimental Patched mautrix-signal + Rust libsignal; automated no-retry tests passing; awaiting live account soak Link a device (QR) No
Google Messages gmessages Beta Built with no-retry transport guard & aggressive reconnect; awaiting live Android phone verification Sign in with Google + phone emoji tap No
Google Voice gvoice Experimental Built with no-retry transport guard; unsigned sends (no Electron helper); awaiting live verification Sign in with Google Yes
Telegram telegram Beta MTProto Go connector wired with file-cache sweep; requires operator API ID/hash; awaiting live verification QR code, phone number No
Messenger meta Beta Unencrypted + encrypted (whatsmeow) chats wired with global log filter & buffer sweep; awaiting live verification Sign in on facebook.com / messenger.com Yes
Instagram instagram Beta Direct messages wired with global log filter; E2EE chats unsupported; awaiting live verification Sign in on instagram.com Yes
Slack slack Experimental Workspaces, channels, DMs, threads wired; channels map as group; awaiting live verification Sign in on slack.com, email code, Slack app Yes
GroupMe groupme Experimental Connector wired with 30-min native_content sweep; awaiting live verification Access token, email/phone & password No
LinkedIn linkedin Experimental Wired with single-send HTTP transport guard; awaiting live verification Sign in on linkedin.com Yes
X twitter Experimental Legacy DMs + encrypted X Chat wired with HTTP/2 transport test; awaiting live verification Sign in on x.com + X Chat PIN Yes
Bluesky bluesky Experimental Text-only DMs wired with no-retry transport guard; 5s polling; awaiting live verification App password No
  • Discord: mautrix-discord still uses the legacy bridge framework rather than bridgev2. Discord will join once its bridgev2 migration lands.
  • Future candidates: iMessage (via an optional macOS companion).

Running all 12 bridge hosts uses extra memory, and Signal compiles libsignal from Rust source on the first build. Use --networks to restrict which bridge hosts run:

Terminal window
deploy/install/install.sh # All supported networks (default)
deploy/install/install.sh --networks whatsapp,signal # Only WhatsApp and Signal
deploy/install/install.sh --networks all # Re-enable every network

Your choice is saved in deploy/.env (INSTALL_NETWORKS). Dropping a network removes its container while keeping its volume and database intact.

Seven networks authenticate through their own websites: Google Messages, Google Voice, Messenger, Instagram, Slack, LinkedIn, and X.

Trioditis runs an isolated login-browser container (Debian Chromium + launcher on an internal signin network with per-browser egress proxies) so members sign in interactively inside the app’s login stepper—no copying cookies out of DevTools. Every login gets its own ephemeral Chromium process and never-reused UID (~0.5 GiB while open, 0 when idle; max LOGIN_BROWSER_MAX=4).

Manual Paste cookies instead always remains available as a fallback. See Sign-in Browser Architecture for full security details.