Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Linagora · twake.app
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Twake at a glance
- Vendor
- Linagora
- Headquarters
- Incorporated in France source, captured 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Twake 2.5/5, the mean of 6 judges. Twake Workplace, the business messaging product of the French vendor LINAGORA, scores strongest on deployment control and encryption and access, and weakest on governance and discovery (a flat 2) and messaging core (a flat 3). how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Twake Workplace, the business messaging product of the French vendor LINAGORA, scores strongest on deployment control and encryption and access, and weakest on governance and discovery (a flat 2) and messaging core (a flat 3). Deployment credit rests on documented custody: Docker-based on-site offers, local installation, self-hosted chat and mail, a public GitHub repository, and chat on the open Matrix protocol with connections to external servers. Encryption credit rests on end-to-end encrypted chats with a recovery key, an encrypted key backup only the user can unlock and per-file media keys; the stated trade-off is that encrypted chats are excluded from search. Governance falls on retention stated only as “as long as necessary” and a user-initiated export of Twake Drive data; we found no public information on admin export, audit logs or legal hold. Sovereignty scores range 4-6 — the vendor states all data is stored in France, but the three named subprocessors come without locations and transfers outside the user's country rest on European Commission standard contractual clauses. Pricing transparency scores 1-2; the pages publish only a free-trial invitation.
Speaks for it
- Deployment control scores 7-8, with Docker-based on-site offers, local installation and self-hosted chat and mail on the customer's own servers documented
- Encryption and access scores 6-8, with end-to-end encrypted chats backed by a recovery key, an encrypted key backup only the user can unlock and per-file media keys
- Chat runs on the open Matrix protocol with connections to external servers, and a public GitHub repository is documented
- LINAGORA, a French company with a published SIRET number and a Data Protection Officer in Issy-les-Moulineaux, is the contracting entity, and the vendor states all data is stored in France
- Bridges to Telegram, Discord and Signal and an OnlyOffice document integration are documented
Held against it
- Governance and discovery scores sit at 2, on retention stated only as “as long as necessary” and a sole user-initiated export of Twake Drive data
- Search runs within a single conversation and excludes encrypted chats, and we found no public information on channels, threads or mentions
- The documented export-and-import round trip covers Twake Drive data only, and we found no public information on a complete export of messages and channel structure
- Documented access settings are user-level (contact visibility, blocked users, a 4-digit mobile PIN), and we found no public information on admin roles, single sign-on or two-factor authentication
- The subprocessors Matomo, Octopush and Tilda Forms are named without published locations, and transfers outside the user's country rest on European Commission standard contractual clauses
Best for
- You need to run your chat platform on your own servers — Docker-based on-site offers, local installation and self-hosted Twake Chat are documented
- Your security review turns on end-to-end encryption with user-held keys — a recovery key and an encrypted key backup only the user can unlock are documented
- You want to reach users on consumer messengers or federate beyond one server — bridges to Telegram, Discord and Signal and connections to external Matrix servers are documented
Avoid if
- You need organisation-wide search of message history — the documented search covers a single conversation and excludes encrypted chats
- Your compliance workflow depends on an administrator-level export, audit log or legal hold — the only documented export is a user-initiated Twake Drive archive
- Your rollout depends on admin roles or single sign-on — the documented access settings are user-level (contact visibility, blocked users, a 4-digit mobile PIN)
- Your team works in channels with threads and mentions — the documented chat surface is direct messages and group chats
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 1.5 of 5 |
| Encryption & access control | 3.5 of 5 |
| Retention, discovery & co-determination | 1 of 5 |
| Deployment & data custody | 4 of 5 |
| Integrations & extensibility | 1.5 of 5 |
| European sovereignty | 2.5 of 5 |
Channels, threads & search
Show reasoningHide reasoning
How this is scored
The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.
0 — Not a team chat: no persistent channels or group conversations, only notifications or one-off messages.
3 — Group chats or channels and direct messages, file sharing, and search over messages.
5 — Public and private channels, threaded replies, mentions and reactions, file sharing with previews, and search across message history.
8 — Cross-organisation or guest channels with clear boundaries, message editing history, pinned and saved items, search with filters by channel, person and date, and unlimited history or a documented history limit per plan.
10 — The archive is a working knowledge base: search that ranks well across years, threads that stay readable, channel lifecycle management (archive, rename, merge) without losing history, and export of a conversation in a form a human can read.
The Team Lead
The documented surface is direct messages, group chats with unread badges and latest-message previews, and file sharing, with search on web and mobile that highlights matches. Search only covers individual conversations and explicitly drops encrypted chats from results, and I found no public information on channels, threads, mentions or pinning. This reads like a consumer-shaped messenger, not the working archive I run a team in. 2 3 4
The Security Officer
Direct and group chats with a latest-message preview, unread badges, file sharing, and word-or-phrase search inside a single conversation on web and mobile, with highlighted results. The search is scoped to one chat and explicitly skips encrypted conversations; we found no public information on channels, threads, mentions, reactions, or search across history. 2 3 4
The Works Council Advocate
Direct messages and group chats with previews, and a search that runs inside a chat on web and mobile — that is the whole documented surface, and it only covers unencrypted messages. I found no public information on organisation-wide channels, threaded replies, mentions, or search filters by person and date. A decision from eighteen months ago lives in whatever each chat kept, and search will not reach it at all if the chat was encrypted. 3 4 2
The Compliance Counsel
Direct messages and group chats are documented with latest-message previews, unread badges, and in-chat search by word or phrase on web and mobile, with matching text highlighted. We found no public information on channels, threaded replies, mentions, or search filters across the whole message history; the documented search works within a conversation and excludes encrypted chats. 2 3 4
The Platform Engineer
The support pages document direct messages, group chats, file sharing, unread badges and word-or-phrase search inside a single conversation, with encrypted chats excluded from search results. We found no public information on public and private channels, threaded replies, mentions or search filters, so this reads as a solid daily chat rather than a searchable archive. 1 3 4
The Skeptic
Direct messages, group chats, file sharing and in-chat search are documented, with highlighted results on web and mobile. The exclusion sentence is in print — encrypted chats won't be included in search results — and search runs within a single conversation rather than across the workspace. We found no public information on channels, threaded replies, mentions, or a documented message-history limit. 1 3 4
Encryption & access control
Show reasoningHide reasoning
How this is scored
What is encrypted and against whom, plus who can reach which room. Judged on documented mechanism, since "encrypted" in this category usually means the vendor holds the keys.
0 — The vendor states that messages are transmitted or stored unencrypted.
3 — Encryption in transit stated, with admin and member roles.
5 — Encryption in transit and at rest stated, admin roles and private channels, guest accounts limited to the channels they are invited to, and SSO or two-factor authentication.
8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, or customer-managed encryption keys; device or session management an admin can revoke, granular permissions per channel, and documented key handling.
10 — End-to-end encryption as a first-class mode — documented or open cryptography, cross-device key management that ordinary users survive, identity verification, and the vendor stating plainly what it cannot decrypt.
The Team Lead
Encryption in transit and at rest are stated, and encrypted chats come with real key handling: a public key that verifies encrypted identity, a recovery key for new devices, and an encrypted key backup only the user can open, with media encrypted per file. The trade-off is named — encrypted chats drop out of search results. What I miss for a company rollout is any documented admin role, SSO or two-factor authentication, or admin-side session revocation. 2 4 6
The Security Officer
Optional end-to-end encrypted chats run on the open Matrix protocol, with media encrypted under a unique per-file key, a recovery key for new devices, a key backup the vendor holds only in encrypted form under a recovery key that is yours alone, and a public key described as verifying your encrypted identity — the trade-off is named honestly, since encrypted chats drop out of search. Unencrypted rooms fall back to AES-256 on the vendor's servers, and we found no public information on sessions an administrator can revoke, SSO or two-factor authentication, or a plain statement of what the vendor cannot decrypt, which is what I need before trusting the sealed rooms. 1 2 4 6
The Works Council Advocate
Encrypted chats are real: media gets a unique key before upload, identity rests on a public key, and a recovery key with an encrypted key backup documents key handling, including the trade-off that encrypted chats drop out of search. The access-control side is user-level only — contact visibility, blocked users, a mobile PIN — and I found no public information on admin roles, SSO or two-factor authentication, or sessions an administrator can revoke. 2 4 6
The Compliance Counsel
Encryption in transit and at rest are stated, and end-to-end encryption exists for encrypted chats with the trade-offs named — those chats are excluded from search and anyone holding the key can read the history. Key handling is documented through a recovery key, an encrypted key backup only the user can unlock, and a public key verifying encrypted identity on the open Matrix protocol; we found no public information on admin-revocable device management or granular per-channel permissions. 1 2 4 6
The Platform Engineer
TLS in transit and AES-256 at rest are stated, and encrypted chats come with real key machinery: a recovery key for new devices, an encrypted key backup sealed with a key only the user holds, a public key that verifies encrypted identity, and the trade-off named plainly since encrypted chats are excluded from search. We found no public information on admin roles, granular per-channel permissions, or admin-revoked sessions, which is the missing half of the story. 1 2 4 6
The Skeptic
Transport encryption (TLS) and at-rest encryption (AES-256 for stored files) are stated, and end-to-end encryption is a real, documented mode rather than a marketing word: keys managed through the open Matrix protocol, a public key for identity verification, a recovery key for new devices, an encrypted key backup only the user can unlock, and media encrypted with a unique key before upload. The trade-off is named in print — encrypted chats are excluded from search results. We found no public information on admin-revocable device sessions, granular per-channel permissions, or single sign-on and two-factor authentication. 2 4 6
Retention, discovery & co-determination
Show reasoningHide reasoning
How this is scored
The archive as a legal object: retention policies, export for discovery, audit, and the monitoring features a works council will ask to have switched off under BetrVG §87(1) no. 6.
0 — A messenger with no organisation-level administration: each user controls their own history, and the organisation has no central export or retention.
3 — Admin export of workspace data or a history setting, with users controlling their own status.
5 — Configurable retention for messages and files, admin export of workspace data in a documented format, and an audit log or activity log of administrative actions.
8 — Per-channel retention executed per policy, legal-hold and eDiscovery export including edits and deletions, a full admin audit trail, and presence, read receipts or activity analytics switchable off organisation-wide.
10 — Built to pass a works agreement and a subpoena on the same day: granular retention with documented deletion, discovery export a lawyer can use, complete audit, and individual productivity scoring stated as not part of the product.
The Team Lead
Retention is a privacy-policy sentence — kept only as long as necessary — rather than a setting an administrator configures, and the only export documented is a user pulling their own Twake Drive data via an emailed download link. I found no public information on organisation-level export, configurable retention, audit logs, legal hold or eDiscovery. For a subpoena or a works agreement, this is thin. 2 7
The Security Officer
Retention is a privacy-policy sentence — personal data kept only as long as necessary — and the one documented export is a per-user archive of Twake Drive data delivered as an email download link, not an organisation-wide export of messages. We found no public information on configurable retention, admin export of workspace data, audit logs, legal hold, or organisation-wide switching of presence and read receipts. 2 7
The Works Council Advocate
Retention is a single sentence — only as long as necessary — with no configurable policy and no documented deletion mechanism, and the only export documented is a user-initiated archive of Drive data, not an administrative export of chat history. There is an analytics platform described as offering insights into user behavior and application usage, and I found no public information on switching analytics off organisation-wide, on any audit log, or on legal-hold and discovery export. 2 7
The Compliance Counsel
What the captured pages show is a user-initiated export of Twake Drive data delivered by email as an archive, plus a retention statement that personal information is kept only as long as necessary — a fixed commitment, not a configurable policy. We found no public information on admin-level workspace export, per-channel retention, legal hold, eDiscovery including edits and deletions, or an audit log of administrative actions; user-level privacy settings such as contact visibility and blocked users are documented. 2 6 7
The Platform Engineer
What is documented is a vendor statement that data is retained only as long as necessary, plus a per-user export of Twake Drive data delivered by email download link, with an import that overwrites after a warning. We found no public information on configurable retention, workspace-wide admin export, audit logs, or organisation-wide opt-outs, and the privacy policy names Matomo as the analytics platform with no switch documented. 2 7
The Skeptic
The privacy policy states a retention principle — personal information kept "only for as long as necessary" — and individuals can export their own Twake Drive data as an archive delivered by email, with an import path that overwrites after confirmation. That export is user-level and drive-specific; we found no public information on organisation-wide retention configuration, admin export of messages, audit logs, legal hold, or organisation-wide switches for the analytics and SMS subprocessors a works council would ask about. 2 7
Deployment & data custody
Show reasoningHide reasoning
How this is scored
Whether the customer can hold their own archive: self-hosting, private cloud, open source, federation, and what an exit actually looks like.
0 — The terms state that the customer's messages cannot be exported or are not returned when the account ends.
3 — Cloud service with an admin export of messages and files.
5 — Cloud service with a documented full export of messages, files and channel structure, or a choice of hosting region, a dedicated instance or a private-cloud option.
8 — A self-hosted edition close to feature parity, or an open-source core with a documented upgrade path, plus complete export including files and metadata.
10 — Custody is the customer's: open-source or source-available server, self-hosting supported as a first-class deployment, open protocol or federation, and a migration path in and out that the vendor documents rather than resists.
The Team Lead
This is where Twake is strong: an open-source platform, Docker-based self-hosting, Twake Chat installable on your own servers, and the Matrix protocol with connections to external servers. The exit story is the weak leg — the documented export and import path is per-user Twake Drive data, and I found no public information on a complete workspace export including channel structure and metadata. 1 2 7
The Security Officer
Custody is genuinely on offer: an open-source platform with a public GitHub repository, on-site offers using Docker, Twake Chat installable on your own servers, files on your own server, and chat connections to external Matrix servers. What keeps this short of the top is the exit — the only documented export is the user-level Twake Drive archive, and we found no public information on a documented full export of messages, files and channel structure for migration. 1 2 7
The Works Council Advocate
Custody is genuinely available: the platform is published as open source, installs on the customer's own servers via Docker, and chat runs on the open Matrix protocol with connections to external servers. What keeps this short of the top is exit — the only documented export-and-import round trip covers Drive data from a personal settings menu, not the message archive with its files and metadata. 1 2 7
The Compliance Counsel
Twake is described as an open-source platform with a public GitHub repository, and self-hosting is documented through on-site offers using Docker, local installation, and running chat and mail on the customer's own servers. Chat runs on the open Matrix protocol and connects to external servers; the documented migration path covers user drive data via export link and import with overwrite, and we found no public information on a complete workspace export with channel structure and metadata. 1 2 7
The Platform Engineer
This is the part that decides it for me: the platform is stated open source with a public GitHub repository, installs on your own servers through on-site Docker offerings, and chat runs on the open Matrix protocol with connections to external Matrix servers — actual federation, and Twake Mail installs on own infrastructure too. The migration story is thinner: the documented export and import covers Twake Drive data, and we found no public information on a complete organisation-wide export or an upgrade path that protects customisations. 1 2 7
The Skeptic
Custody options are unusually well documented: Docker-based installation on the customer's own servers, local install of the workplace, self-hosted editions of chat and mail, an open-source repository, and the open Matrix protocol with connections to external servers — the policy even warns that external servers are outside Twake's control. What an exit looks like is only partly documented: the export and import path covers Twake Drive data, and we found no public information on complete export of messages, channel structure and metadata. 1 2 7
Integrations & extensibility
Show reasoningHide reasoning
How this is scored
Bots, webhooks, app framework, identity — whether the chat becomes the place work is noticed, and whether that is buildable without a partner agreement.
0 — A closed messenger: no integrations, webhooks, bots or API.
3 — Incoming webhooks or a handful of named integrations.
5 — An app directory or a list of native integrations with common tools, a documented API, incoming webhooks and bots or slash commands.
8 — A proper app framework with interactive components, event subscriptions with retries, SSO and SCIM provisioning, documented rate limits and a sandbox.
10 — A platform: versioned API with a deprecation policy, an app directory or plugin system with permissions a customer can audit, and integrations the vendor maintains rather than lists.
The Team Lead
The named extensibility points are bridges to Telegram, Discord and Signal, an OnlyOffice integration for documents, JMAP for mail, and a public GitHub repository. I found no public information on a documented API, incoming webhooks, bots or an app directory, so the chat is not yet the buildable surface my team's automations would need. 1 2
The Security Officer
A handful of named integrations: bridges to Telegram, Discord and Signal, an OnlyOffice integration for documents, and JMAP mail servers. We found no public information on a documented API, webhooks, bots or slash commands, an app directory, or SSO and SCIM provisioning. 1 2
The Works Council Advocate
A handful of named integrations — bridges to Telegram, Discord and Signal, OnlyOffice for documents, JMAP mail — plus GitHub access for developers. I found no public information on a documented API, webhooks, bots or an app directory, so the chat cannot be judged as a buildable platform. 1 2
The Compliance Counsel
The homepage names bridges carrying messages through Telegram, Discord and Signal, and an OnlyOffice integration for document management — a handful of named integrations. We found no public information on a documented API, webhooks, bots or slash commands, or an app directory in the captured pages. 1
The Platform Engineer
The documented extensibility is bridges to Telegram, Discord and Signal plus an OnlyOffice document integration — genuinely useful federation at the transport level, but still a handful of named integrations. We found no public information on a documented API, webhooks, bots, slash commands or an app framework, though the Matrix and JMAP protocols leave the door open. 1 2
The Skeptic
The named integrations are bridges to Telegram, Discord and Signal plus OnlyOffice for document editing, alongside the vendor's own mail and drive products under one account. We found no public information on a documented API, webhooks, bots or slash commands, an app directory, or single sign-on and provisioning for third-party tools. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the archive and its metadata live, who the contracting entity is, which subprocessors touch it. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — EU data residency for message content, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (notifications, AI features, analytics) is unstated or partly non-EU.
8 — EU hosting on named infrastructure covering content and metadata, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that removes the question.
The Team Lead
LINAGORA is a French contracting entity with a French data protection officer, and the vendor's page states all data is stored in France. The subprocessors are named — Matomo, Octopush and Tilda Forms — but without locations, and the policy acknowledges transfers outside the user's country under European Commission standard contractual clauses. I found no public information on a published data processing agreement or named hosting infrastructure. 1 2
The Security Officer
The contracting entity is LINAGORA, a French simplified stock company with a published SIRET and a Data Protection Officer in Issy-les-Moulineaux, the vendor states that all data is stored in France with GDPR compliance, and three subprocessors are named with their purposes. But the subprocessor locations are not published, transfers outside the user's country rest on standard contractual clauses, and we found no public information on a published data processing agreement or named hosting infrastructure. 1 2
The Works Council Advocate
The contracting party is LINAGORA, a French company with a French Data Protection Officer, and the vendor's pages state that all data is stored in France — but the three named subprocessors (Matomo, Octopush, Tilda Forms) come without locations, and transfers outside the user's country are contemplated under standard contractual clauses. I found no public information on a published data processing agreement or the infrastructure behind the French hosting statement. 1 2
The Compliance Counsel
All data is stated to be stored in France, the contracting entity LINAGORA is a French company with a named Data Protection Officer, and three subprocessors — Matomo, Octopush and Tilda Forms — are published, though without locations. Transfers outside the user's country are acknowledged with European Commission standard contractual clauses as the safeguard; we found no public information on the named hosting infrastructure or a fully European subprocessor chain. 1 2
The Platform Engineer
LINAGORA is the contracting entity, a French company with a French DPO address, and the vendor page states all data is stored in France; the privacy policy names Matomo, Octopush and Tilda Forms as subprocessors and deploys European Commission standard contractual clauses for transfers outside the user's country. We found no public information on the infrastructure behind the French-storage claim, subprocessor locations, or a published data-processing agreement. 1 2
The Skeptic
Two European elements are proven: the contracting entity is LINAGORA, a French company with a SIRET number and a French Data Protection Officer, and the vendor's own page states all data is stored in France. The chain frays after that — the subprocessors Matomo, Octopush and Tilda Forms are named without locations, and the policy acknowledges transfers outside the user's country under standard contractual clauses without naming destinations. We found no public information on a published data processing agreement or the named infrastructure behind the France claim. 1 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual invoice for their headcount — including the retention, compliance and guest features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier per user.
5 — Per-user prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries (retention, SSO, eDiscovery), minimum term and VAT treatment stated; self-hosted licensing priced too where offered.
10 — Complete price computability: annual invoice derivable for a given headcount and deployment choice, including guest users, storage and any per-instance licence.
The Team Lead
The only pricing-related statement captured is an invitation to try for free; I found no public information on tiers, per-user prices, billing periods or what compliance features cost. I cannot compute an annual invoice for my headcount from these pages. 1
The Security Officer
The only commercial information the captured pages give is a free-trial offer. We found no public prices, no tiers, no per-user figures and no billing periods, so a buyer cannot begin to compute an annual invoice from what is published. 1
The Works Council Advocate
The only pricing-related statement on the pages captured is an invitation to try it for free. I found no public prices, tiers or billing periods, so a buyer cannot begin to compute an annual invoice — including retention or compliance features — from these pages. 1
The Compliance Counsel
The only pricing-related statement found is an invitation to try it for free; we found no public prices, tiers, billing periods or per-user figures in the captured pages. An annual invoice for a given headcount cannot be computed from what is published. 1
The Platform Engineer
The only public pricing signal we found is a free-trial invitation on the homepage; we found no public per-user prices, tier list or billing terms on the pages read, so an annual invoice cannot be worked out from public information alone. 1
The Skeptic
The only pricing fact the captured pages yield is a free-trial invitation — "Essayez gratuitement dès maintenant". We found no public information on per-user prices, tiers, billing period, history or storage limits, or the tier in which single sign-on or compliance features appear, so an annual invoice cannot be computed from the public pages alone. 1
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in FR | 2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Twake
Is Twake European?
Not determined: the vendor’s pages as captured do not say where Twake is based. Its vendor, Linagora, is incorporated in France, per the vendor’s page captured 17 Nov 2026.
Where does Twake store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Twake have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Twake?
As of 19 Nov 2026, the panel rates Stackfield (3.5/5), Mattermost (3.5/5) and Element (3.5/5) highest among the other 27 Business Instant Messaging products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Stackfield (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Twake alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page twake.app Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage twake.app Checked 17 Nov 2026 Details →
- 3 Channels, threads & search — found from sitemap support.twake.app Checked 17 Nov 2026 Details →
- 4 Channels, threads & search — found from sitemap support.twake.app Checked 17 Nov 2026 Details →
- 5 Encryption & access control — found from sitemap support.twake.app Checked 17 Nov 2026 Details →
- 6 Encryption & access control — found from sitemap support.twake.app Checked 17 Nov 2026 Details →
- 7 Retention, discovery & co-determination — found from sitemap support.twake.app Checked 17 Nov 2026 Details →