Open-source secure messaging, honestly reviewed. No marketing fluff — just what you get when you put a French open-source company’s Matrix client on your server.

TL;DR

What it is: Open-source (AGPL-3.0) Matrix protocol messaging client developed by Linagora, a French software company. Think Element — but with a more polished consumer UI and an enterprise-behind-it backstory [4][5].
Who it’s for: Privacy-conscious teams who want end-to-end encrypted messaging on their own infrastructure, with decent mobile apps and the interoperability of the Matrix network [README][1].
Cost savings: Slack’s paid plans start at $7.25/user/month; at 10 users that’s $870/year. Twake Chat self-hosted runs on any Matrix homeserver — a $6–10/mo VPS — with no per-user pricing [5].
Key strength: Built on Matrix, which means full federation and bridges to Telegram, Discord, Signal, and 30+ other networks out of the box [website]. The Flutter-based mobile apps are cross-platform and actually maintained [README].
Key weakness: Only 147 GitHub stars — a red flag for enterprise adoption. The product has pivoted identity at least once (from a full Nextcloud-like suite to a chat-focused app). Several features on the website are still listed “COMING SOON” [website][README].

What is Twake Chat

Twake Chat is a Matrix-protocol messaging client built by Linagora, a French open-source company that also produces Twake Workplace, Twake Drive, and Twake Mail under a unified account system [website]. The client itself — what’s reviewed here — is the twake-on-matrix Flutter app on GitHub. It connects to any Matrix homeserver, which means you’re not locked into Linagora’s infrastructure.

The history matters for context. The original “Twake” that reviewers wrote about in 2020–2021 was a completely different product: a full collaboration suite with Kanban boards, shared calendars, OnlyOffice document editing, and task management [1][4]. That was essentially a Nextcloud competitor. The current Twake Chat is a narrower pivot — a messaging-first client built on Matrix, with the broader workplace suite sold separately. If you’re reading old Twake reviews, they’re describing a product that has since been rebranded and restructured.

What makes Twake Chat distinct from a bare-bones Matrix client:

Linagora backing. This isn’t a hobbyist project — Linagora is a 23-year-old French open-source company, GDPR-compliant, EU-hosted, and actively maintaining the codebase [website][4].
Flutter client. The app is cross-platform by design (Android, iOS, Linux, macOS, web), not a different codebase per platform [README].
Matrix federation. Because it’s Matrix-based, messages from your Twake Chat instance are interoperable with Element, Nheko, NeoChat, and any other Matrix client [README][website].
AGPL-3.0 license. More restrictive than MIT — if you embed it in a commercial product, you have to publish your modifications [merged profile].

As of this review, the GitHub repository at linagora/twake-on-matrix sits at 147 stars. That’s low — for reference, Element (the flagship Matrix client) has 10,000+ stars. Rocket.Chat is at 40,000+. Mattermost exceeds 30,000. The number alone doesn’t determine quality, but it’s a signal about community breadth and third-party troubleshooting resources.

Why people choose it

The third-party coverage is thin and dated, which itself says something. The three most relevant reviews were written in 2020–2021 and reviewed the original full-suite Twake — not the current Matrix-focused client. The core reasons people choose it are inherited from the broader Matrix ecosystem rather than being specific to Twake Chat.

The Matrix interoperability argument is the strongest case. Instead of juggling separate apps for Telegram, Discord, and Slack, a Matrix client with bridges consolidates everything into one interface [website][5]. Twake Chat inherits this directly. The nixFAQ reviewer [1] described the original Twake as covering “all major tools needed in one place” — that value still holds for the chat layer, but it’s now delivered via Matrix protocol rather than a bespoke backend.

The privacy and data ownership argument mirrors what drives every self-hosted chat adoption. The Chanty roundup [5] frames it clearly: “In self-hosting, your data stays on your servers. You do not have to be afraid that it might leak into the public or become available for unauthorized access.” For teams handling anything sensitive — legal, finance, healthcare — the calculus of passing messages through Slack’s servers versus your own is real.

The EU/GDPR angle is meaningful for European teams. Linagora is French, EU-hosted, and explicitly GDPR-compliant [4]. For companies subject to GDPR that want the compliance story to be simple, “we self-host and the vendor is EU-based” is cleaner than explaining Slack’s data processing agreement.

The anti-Slack pricing argument is the emotional driver. Slack’s pricing, vendor lock-in, and history of changing terms push teams toward alternatives. Twake Chat — and Matrix generally — is the cleanest answer for teams that want something Slack-shaped without per-user SaaS pricing [5].

Where the reviews are honest about limits: the itsFOSS review from 2021 [4] noted the login page was slow and that the original Twake “works pretty well in limited testing” — not exactly a ringing endorsement. No post-2022 in-depth review of Twake Chat specifically exists in the sources, which points to limited external validation of the current product.

Features

Based on the GitHub README and website:

Core messaging:

Text, image, file, and voice messages [README]
End-to-end encryption (E2EE) with emoji verification and cross-signing [README]
Private and public group chats, public channels [README]
Direct messages [README]
Push notifications [README]
Feature-rich group moderation including all Matrix features [README]

Matrix-specific:

Federation — your instance talks to any other Matrix homeserver [README]
Bridges to Telegram, Discord, Signal, and 30+ other networks via Matrix bridge protocol [website]
Compatible with Element, Nheko, NeoChat, and all standard Matrix clients [README]
Matrix ID management simplified with QR codes [README]
Spaces (Matrix Spaces, similar to Slack workspaces) [README]

UI/UX:

Dark mode and custom themes [README]
Custom emotes and stickers [README]
Multi-account support — personal and work accounts in one interface [website]
Cross-device sync [website]

Enterprise/deployment:

SSO via corporate directory integration [website]
Docker deployment [merged profile]
APT package for Linux [merged profile]
Identity server for email/phone searchability [website]

Listed as “COMING SOON” on the official website:

Matrix bridges beyond current integrations [website]
Jitsi video conferencing integration [website]
Corporate domain connection [website]

The “COMING SOON” count is worth flagging. Bridges are one of the main selling points of the Matrix ecosystem — listing them as upcoming undermines the pitch.

Pricing: SaaS vs self-hosted math

Twake Chat Cloud: The website offers a “Sign Up” cloud option but does not publish pricing on the public pages. For on-premise or managed deployment, the call-to-action is “Contact Us.” No specific pricing tiers, per-user costs, or feature gates are listed on the public website [website]. This makes direct SaaS pricing comparison impossible without contacting sales.

Self-hosted:

Software license: $0 (AGPL-3.0) [README]
Matrix homeserver (Synapse or Dendrite): $0 additional license, runs on same VPS
VPS: $6–15/mo on Hetzner, Contabo, or DigitalOcean
Storage costs scale with file attachments and media uploads

Slack for comparison:

Free: 90-day message history, limited integrations
Pro: $7.25/user/month billed annually
Business+: $12.50/user/month
Enterprise Grid: custom pricing

Concrete math: A 15-person team on Slack Pro pays approximately $1,305/year. Self-hosted Twake Chat on a $10/mo Hetzner VPS (which comfortably handles 50+ active users) costs $120/year — a saving of roughly $1,185/year. The math holds regardless of team size because self-hosted is flat-rate infrastructure, not per-seat [5].

The AGPL-3.0 license has one cost implication worth noting: if you’re building a commercial product on top of Twake Chat and distributing it, you must open-source your modifications. For internal team use, this doesn’t matter. For ISVs or agencies building client products, it may [merged profile].

Deployment reality check

Twake Chat is a client — a Flutter application that connects to a Matrix homeserver. This means deployment is actually two problems: setting up the homeserver, and distributing the client.

What you’re actually deploying:

A Matrix homeserver (Synapse is the most common — maintained by Element). Twake Chat doesn’t ship its own homeserver — you bring your own [README].
The Twake Chat web client, OR you point users to the iOS/Android apps from the App Store/Play Store [README].
Optional: an identity server for email/phone lookup [website].

Homeserver requirements (Synapse):

Linux VPS, minimum 2GB RAM (4GB+ recommended for production)
PostgreSQL
Docker or native install
A domain with valid TLS certificate

What can go sideways:

Matrix homeserver administration is non-trivial. Synapse in particular has a reputation for memory usage that grows with room history. If you’ve never run a Matrix homeserver, budget more than a weekend.
The development setup in the README [README] is notably complex — requires Flutter 3.38.9, Android SDK with specific build tools (34.0.0), NDK (26.1.10909125), JDK 17, Rust, and a docker-based libolm build for web. This is the developer setup, not the end-user experience, but it signals a complex build chain.
The itsFOSS review [4] noted that in their limited testing the product was a bit slow at login — and that was the managed cloud version.
147 GitHub stars means if you hit a novel problem, you may not find a Stack Overflow answer. You’re relying on the Linagora team’s responsiveness.
The AlternativeTo listing shows Twake with 29 likes [3] — a small but real user base that adds Twake to comparison lists.

Realistic time estimate: For a technical user familiar with Docker and Matrix: 3–6 hours for a working Synapse + Twake Chat deployment. For a non-technical founder: this is firmly in “hire someone” territory. Unlike Activepieces or Mattermost, Matrix homeserver administration has enough sharp edges that a one-off setup service is genuinely worth paying for.

Pros and Cons

Pros

Matrix protocol. Federation, bridges, and interoperability are the strongest argument. Connect to Telegram, Discord, Signal from one interface [website]. Your messages aren’t siloed.
Linagora is a real company. 23 years old, EU-based, GDPR-compliant, active development [website][4]. Not an abandoned side project.
Genuine E2EE. End-to-end encryption with cross-signing and emoji verification — not a marketing claim but a cryptographic reality inherited from Matrix [README].
Flutter means real mobile apps. iOS and Android apps are in the App Store and Play Store, not a mobile-responsive webapp [README].
SSO integration. Corporate directory integration via SSO is supported (notable because many open-source chat tools gate this behind enterprise licensing) [website].
AGPL-3.0 open source. Full source available, no vendor backdoors, auditable security [README].

Cons

147 GitHub stars. This is a meaningful signal. It means a small community, fewer third-party integrations, fewer tutorials, and less certainty about long-term sustainability [merged profile].
AGPL-3.0 is restrictive. Unlike MIT, modifications to AGPL code that you distribute must be open-sourced. Fine for internal use; potentially a blocker for building commercial products on top [merged profile].
Website has significant “COMING SOON” sections. Bridges and Jitsi integration are core selling points that aren’t shipped yet [website].
No public pricing. “Contact Us” for on-premise is a sales friction that most teams won’t bother with [website].
Sparse recent reviews. Meaningful third-party coverage of Twake Chat specifically — as opposed to the original full-suite Twake — is nearly absent. The product has pivoted once and may do so again.
Matrix homeserver complexity. You’re not just deploying one Docker container. Synapse + Twake Chat + identity server is a real ops project [README].
The 2020–2021 reviews are outdated. They describe a different product. Positive coverage of “Twake” doesn’t necessarily transfer to “Twake Chat” [1][4].
No REST API documentation surfaced in public materials — limited external integration options for teams that want to build on top of it [merged profile].

Who should use this / who shouldn’t

Use Twake Chat if:

You’re a European team that needs GDPR-compliant messaging with data on your own servers.
You already have Matrix infrastructure (or a sysadmin comfortable with Synapse) and want a polished Flutter client as an alternative to Element.
You want to consolidate Telegram, Discord, and Slack contacts into one Matrix-bridged interface.
You work at a company that already uses Linagora products (Twake Workplace ecosystem) and wants unified accounts.

Skip it (pick Mattermost instead) if:

You want a Slack replacement with documented REST APIs, plugin marketplace, and 30,000+ GitHub stars proving community stability.
Your team has non-technical members who need a no-setup experience — Mattermost’s Docker install is more battle-tested and has far more community resources.

Skip it (pick Element instead) if:

You want the flagship Matrix client with maximum compatibility, the largest community, and the most complete feature set.
You need video calling now rather than when Jitsi integration ships.

Skip it (pick Rocket.Chat instead) if:

You need an out-of-the-box Slack replacement with livechat, bots, and hundreds of integrations that don’t require Matrix bridge setup.
Your team values ecosystem depth over protocol purity.

Skip it (stay on Slack) if:

Your team has no technical staff to manage a Matrix homeserver.
You’re on Slack’s free tier and the 90-day history limit isn’t bothering you.
Your compliance or legal team requires a vendor-backed SLA.

Alternatives worth considering

Element — the reference Matrix client, 10,000+ stars, most complete Matrix feature set, backed by Element (formerly New Vector). If you want Matrix, this is the safer default [3].
Mattermost — the serious Slack replacement for engineering teams. 30,000+ stars, MIT-licensed Team Edition, mature REST API, plugin marketplace, documented ops playbook [5].
Rocket.Chat — the broadest open-source chat platform, 40,000+ stars, includes livechat and omnichannel. AGPL-3.0 like Twake Chat but vastly larger community [5].
Zulip — the outlier: threaded conversation model instead of channel/DM model. Apache 2.0 license, genuinely different UX that some teams love for async work [5].
Nextcloud Talk — if you’re already self-hosting Nextcloud for files/docs, Talk integrates cleanly and avoids running a second server [3][5].
Wire — end-to-end encrypted, EU-based, used by governments for secure comms. Closed-source at the server layer but client is open [5].

For a non-technical founder escaping Slack’s per-user pricing, the realistic shortlist is Mattermost or Rocket.Chat — not Twake Chat. Both have dramatically larger communities, more tutorials, and more predictable ops. Twake Chat makes more sense for teams already in the Matrix ecosystem or those with a strong preference for the Linagora stack.

Bottom line

Twake Chat is a technically credible Matrix client from a legitimate European open-source company, but it’s not the product you should reach for first when escaping Slack bills. The 147 GitHub stars tell a story: this is a niche client for teams already committed to Matrix or already inside the Linagora product ecosystem. The Matrix protocol underneath is solid — federation, E2EE, and bridges are genuinely valuable. But the “COMING SOON” features on the website, the absence of public pricing, the pivot from a full suite to a chat-focused client, and the near-total lack of recent third-party reviews all suggest a product in transition rather than a stable foundation to bet your team’s communications on. If you’re already running Synapse and want a polished Flutter client to point your users at, Twake Chat deserves a look. If you’re starting from scratch and want to escape Slack, look at Mattermost or Rocket.Chat first — they have the community depth to keep you from being stuck with a problem and no answers.

Sources

nixFAQ — “Twake App - Superb all in one collaboration platform - First impression”. https://nixfaq.org/2020/12/twake-app-superb-all-in-one-collaboration-platform-first-impression.html
AlternativeTo — “Let’s Chat: Self-hosted chat for small teams”. https://alternativeto.net/software/let-s-chat/about/
AlternativeTo — “Best Slack Alternatives: Top Group Chat Apps in 2026”. https://alternativeto.net/software/slack/?p=2
itsFOSS, Ankush Das — “Meet Twake, A Modern Open-Source Collaboration Platform [Nextcloud Alternative]” (Apr 17, 2021). https://itsfoss.com/twake-app/
Chanty, Lisa Hodun — “Top 10 Self-Hosted Slack Alternatives for Seamless Team Collaboration” (Nov 6, 2025). https://www.chanty.com/blog/self-hosted-slack-alternatives/