Twake Chat

Twake Chat is a cross-platform messaging client designed for team communication over the Matrix protocol. Maintained by Linagora and built with Flutter, it connects to standard homeservers while simplifying cryptographic verification and room discovery for staff. By anchoring discussions in a federated architecture, it keeps team conversations and attachments within organizational boundaries.

Why Twake Chat instead of Slack

Slack stores message history, uploaded files, and communication metadata on proprietary servers managed by Salesforce. For teams subject to strict confidentiality mandates, this centralized cloud model introduces compliance exposure, potential vendor lock-in, and unpredictable subscription increases. While Slack provides enterprise key management on premium tiers, encryption keys and customer data remain tied to closed infrastructure. Twake Chat shifts sovereignty back to the organization by separating the client interface from central platform control. Teams run their own Matrix homeserver on premises or in a private cloud, retaining complete custody over databases, logs, and cryptographic material.

The trade-off lies in integration maturity and operational effort. Slack offers an extensive marketplace of pre-built app integrations, workflow bots, and turnkey enterprise administration. Twake Chat delivers core team messaging—threaded conversations, direct messages, media sharing, voice clips, and structured spaces—backed by Olm and Megolm end-to-end encryption. However, transitioning from Slack requires technical staff to maintain Matrix infrastructure, handle message retention policies, and guide members through cross-signing device verification rather than relying on standard single-sign-on logins.

What it does well

• Federated cross-domain messaging: Ops leads can collaborate with external contractors or client teams across independent Matrix domains without provisioning guest seats in internal workspaces.
• End-to-end encryption: Rooms safeguard conversations, voice notes, and file exchanges with Megolm encryption, device cross-signing, and SAS emoji verification.
• Hierarchical Matrix Spaces: Teams can group channels into structured client workspaces, keeping operational discussions separated under distinct permissions.
• Containerized web deployment: Administrators can launch the web interface via a lightweight Docker container configured through a single mounted JSON file.