Threema Work
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Threema GmbH · threema.ch
Compare with Wire (Messaging) → 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.
Threema Work at a glance
- Vendor
- Threema GmbH
- Headquarters
- Incorporated in Switzerland source, captured 16 Nov 2026
- Data hosting
- In the EU; pages mention Switzerland source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Threema Work 3/5, the mean of 6 judges. Threema Work is an end-to-end encrypted Swiss messenger; its strongest and weakest scores share one cause. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Threema Work is an end-to-end encrypted Swiss messenger; its strongest and weakest scores share one cause. Encryption and access is the top score, a flat 9, on open-source apps with reproducible Android builds, Cure53 audits and the vendor's statement that not even Threema can read message content. The weakest scores are messaging core at 2 to 4 and governance and discovery at 2 to 4: the vendor states transcripts cannot be created through the management cockpit or the API; external archiving relies on users exporting their own chats; and we found no public information on message search or threading. The governance spread is a genuine split: the works-council judge's 4 welcomes an organisation unable to read employee conversations; the compliance counsel's 2 notes the regulator's record lives on handsets. Deployment control scored 6 to 8 on a self-hosted OnPrem plan with air-gapped operation; sovereignty scored 7 to 8 on the vendor's own hardware, with Switzerland outside the EU and a named US subprocessor. Pricing transparency is a flat 6: both cloud tiers priced publicly, OnPrem only on request.
Speaks for it
- End-to-end encryption of text and voice messages, media, calls, profile pictures, group names and the group member list, with the vendor stating not even Threema has access
- Open-source apps with reproducible Android builds, a formal security proof of the Ibex protocol and Cure53 audits
- Self-hosted OnPrem plan with white-labeling of all apps and air-gapped operation, plus self-hostable Threema Safe key backups
- Hosting on the vendor's own hardware in two Zurich data centers of an ISO 27001-certified colocation partner, with named subprocessors the customer can disable
- Public per-user cloud pricing — Core at EUR 3.00 and Professional at EUR 5.00, monthly per user with annual payment stated — and a 30-day trial for 30 users without payment data
Held against it
- We found no public information on message search, threaded replies or mentions, so a past decision is not shown to be findable
- Transcripts cannot be created through the management cockpit or the API, and external archiving relies on users exporting their own chats
- We found no public information on configurable message retention, legal hold, discovery export or an administrative audit log
- The OnPrem tier is priced only as custom, and Azure Active Directory synchronisation carries an unstated additional charge
- We found no public information on contact identity verification, and the captured pages give different company names for the server operator, the imprint showing Threema AG
Best for
- You need audited, end-to-end encrypted messaging for sensitive conversations — encryption and access scored a flat 9
- Your works council requires that neither the employer nor the vendor can read employee conversations — the vendor states not even Threema has access, and transcripts cannot be created centrally
- You want Swiss hosting on the vendor's own hardware or an air-gapped self-hosted deployment — and the vendor states it is not subject to the US CLOUD Act
- You push one-to-many alerts into the app from your own systems — the Gateway and Broadcast APIs are documented, with named integrations including Grafana and Mattermost
Avoid if
- You must produce message transcripts centrally for audits, eDiscovery or litigation — the vendor states they cannot be created through the management cockpit or the API
- You need a published price for self-hosting before talking to sales — the OnPrem tier is priced only as custom
- You require an EU member-state contracting party — Threema AG is Swiss and the processing agreement is governed by Swiss law
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 1 of 5 |
| Encryption & access control | 4.5 of 5 |
| Retention, discovery & co-determination | 1.5 of 5 |
| Deployment & data custody | 3.5 of 5 |
| Integrations & extensibility | 2.5 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 3 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
Group chats, direct messaging, edit and delete, emoji reactions, polls, and encrypted files of any type up to 100 MB are all documented, and the one-to-many channel with topic feeds and muting is real. But we found no public information on message search, threaded replies, mentions or channel archiving — which is exactly what I need to find last spring's decision — so it stays below the level where search over history is documented. 1 2 7 8 11
The Security Officer
Group chats, direct messages, end-to-end encrypted file sharing of any file type up to 100 MB, polls, emoji reactions and message editing are documented, with Broadcast feeds and bots for one-to-many delivery and subscribe or unsubscribe commands on the vendor's channel. We found no public information on message search, threaded replies, mentions or a persistent channel model, so the documented daily surface is a secure messenger's rather than a searchable team archive. 1 2 1 7 8
The Works Council Advocate
Persistent group chats, direct messages, end-to-end encrypted file sharing of any type up to 100 MB, polls, message editing and deletion, emoji reactions and an availability status are documented across mobile, desktop and web apps. We found no public information on message search, threaded replies, mentions or an internal channel model — the documented "Channel" is a vendor news feed with subscribe and unsubscribe commands — so the pages never show a buyer how a decision made eighteen months ago would be found again. 1 2 1 7 8
The Compliance Counsel
Group chats, voice and video calls, file sharing up to 100 MB, polls, emoji reactions and editable messages are documented, which takes this past a basic group messenger. We found no public information on threaded replies, mentions, or search across message history, and the only export route documented is a user manually exporting a chat — so I cannot treat this as a searchable record of decisions. 1 1 7 11
The Platform Engineer
Group chats, direct messages, polls, emoji reactions, edit-and-delete and file sharing of any type up to 100 MB are documented, plus voice, video and group calls and a broadcast-style channel with topic feeds users subscribe and unsubscribe to. We found no public information on message search, threaded replies or mentions, so whether an eighteen-month-old decision can be found again is not answerable from the captured pages. 1 1 7 8
The Skeptic
Group chats, file sharing with files of any type up to 100 MB, emoji reactions, message editing and polls are documented. We found no public information on search over message history, threading, mentions, or a documented history limit, and the only channel mechanism described is Threema's own news feed with per-topic subscription and mute. On this record the daily surface is a classic messenger, and nothing captured shows how a decision from eighteen months ago would be found again. 1 1 7 8
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
End-to-end encryption is the default mode, covering messages, media, calls, profile pictures and even group member lists, and the vendor states plainly that not even Threema can read message content. The apps' source code is public with reproducible Android builds, the Ibex protocol carries a formal security proof, Cure53 audited the apps, two-factor authentication and MDM-based central access control are listed, and key backups can be self-hosted with documented scrypt and NaCl handling. The only element of the top level we found no public information on is an identity-verification feature. 1 4 9 10 2
The Security Officer
End-to-end encryption is the default mode covering messages, media, calls, profile pictures, group names and the member list, and the vendor states plainly that message content is visible only to sender and recipient — not even Threema has access. The cryptography is open source with reproducible builds on Android, carries a formal security proof of the Ibex protocol and regular independent audits, and key backup is protected by a password-derived scrypt and NaCl encryption that users can host on their own server. We found no public information on device or contact verification between users, which keeps this just short of the top level. 2 1 4 9 10 11
The Works Council Advocate
End-to-end encryption is the first-class default for text, voice, media, calls, profile pictures, group names and member lists, with the vendor stating plainly that message content is visible only to sender and recipient — not even Threema has access. The cryptography is open and tested: public app source with reproducible Android builds, a formal proof of the Ibex protocol, Cure53 audits, and a password-derived, optionally self-hosted Threema Safe for key backup; two-factor authentication and MDM-based central access control cover administration. We found no public information on contact identity verification, which is the one element of the top level the captured pages do not show. 1 2 1 4 9 10
The Compliance Counsel
End-to-end encryption is the product's spine and the vendor says it plainly: message content is visible only to sender and recipient, "not even Threema has access". It is backed by open-source apps with reproducible builds, a formal proof of the Ibex protocol, Cure53 audits, Perfect Forward Secrecy, and Threema Safe for cross-device key recovery that can sit on the customer's own server; two-factor authentication and MDM give an administrator revocation levers. I hold back the final point only because we found no public information on contact identity verification. 2 1 4 9 10
The Platform Engineer
End-to-end encryption is the default mode for text, voice, media, calls, profile pictures, group names and member lists, with the vendor stating plainly that not even Threema has access to message content — backed by open-source apps, a cryptography whitepaper, reproducible Android builds, a formal security proof of the Ibex protocol from July 2023 and Cure53 audits. Key recovery runs through Threema Safe with scrypt derivation and NaCl encryption, optionally self-hosted, and two-factor authentication plus MDM-based central access control are on the plans. I hold back the last point only because contact identity verification is not documented on these pages. 1 2 1 4 9 10
The Skeptic
The encryption claim survives the hunt: end-to-end encryption is documented for text and voice messages, media, calls, profile pictures, group names, the group member list and files, and the vendor states plainly that message content is visible only to sender and recipient — not even Threema has access. The apps are open source with reproducible builds, the Ibex protocol carries a formal security proof, and cross-device key backup via Threema Safe is documented down to the algorithms with a self-hostable backup server. We found no public information on contact identity verification; two-factor authentication and MDM-based access control are priced in. 2 1 4 7 9 10
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
The captured pages state that transcripts cannot be created through the management cockpit or the API because of the end-to-end encryption, and that external archiving for auditing means asking users to export their own chats — a subpoena would land on individual phones, not on an admin console. Organisation-level user administration exists, data is returned or deleted at the customer's choice when the contract ends, and users control their own availability status, which keeps this just above the bare minimum; we found no public information on configurable message retention, a discovery export or an admin audit trail. 11 6 1
The Security Officer
The vendor states that, because of the end-to-end encryption, transcripts cannot be created through the management cockpit or the API, and that external archiving for auditing or reporting is achieved by asking users to export their chats. The published data processing agreement carries retention schedules in an annex, return or deletion of personal data at the customer's choice, breach notification, and audit rights granted once per year at the customer's expense. We found no public information on central retention configuration, legal hold, eDiscovery export or an administrative audit trail; an off-hours policy and user-controlled availability status are documented. 1 6 11
The Works Council Advocate
The vendor itself states that transcripts cannot be created using the management cockpit or the API because of end-to-end encryption, and that external archiving for auditing means asking users to export their own chats — a council can welcome that the organisation cannot covertly central-read conversations. What is documented for co-determination is an off-hours policy, an availability status, and the customer's ability to switch off the functions that require subprocessors through configuration; we found no public information on configurable organisation-wide message retention, an administrative audit log, or organisation-wide control of read receipts and activity analytics. 1 2 1 6 11
The Compliance Counsel
The vendor states that, due to end-to-end encryption, transcripts cannot be created through the management cockpit or the API, and that a company needing external archiving must ask its users to export their own chats — so the record a court or regulator would demand lives on employee handsets, not with the organisation. We found no public information on message retention policies, legal hold, or an administrative audit trail. The management cockpit and an unusually detailed processing agreement, with a once-yearly audit right and return-or-deletion at contract end, keep this above the floor. 11 6 1 2
The Platform Engineer
The vendor itself states that, due to end-to-end encryption, transcripts cannot be created using the management cockpit or the API, and external archiving for audit relies on asking users to export their own chats — the archive is a device-side object, not an organisational one. The data processing agreement covers retention of the processor's own minimal data, return-or-deletion at the customer's choice, one audit per calendar year at the customer's cost and a 14-day window to object to new subprocessors, and off-hours policy and availability status are the co-determination-relevant switches on show. We found no public information on organisation-wide message retention configuration or legal-hold and eDiscovery export. 2 1 6 11
The Skeptic
The sentence a works council will look for is on the record: due to the end-to-end encryption, transcripts cannot be created through the management cockpit or the API, and external archiving for auditing is described as asking users to export their own chats. Organisation-level administration exists for users, groups and broadcasts, but we found no public information on configurable retention for workspace messages, legal-hold or discovery export, or an admin audit log — the retention figures published concern website visitor data, not the message archive. 2 1 6 11 3
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
An OnPrem self-hosting plan with air-gapped operation and white-labelling of all apps sits alongside the cloud service, the mobile and desktop apps are open source with a documented backup-and-restore migration path, and Threema Safe backups can run on the customer's own server. The self-hosted plan is quoted only as CUSTOM behind a sales contact, and we found no public information on a complete organisational export including files and metadata — which the end-to-end architecture makes structurally hard. 2 1 1 10 14 6
The Security Officer
An OnPrem plan with self-hosting, air-gapped operation and white-labeling of all apps is offered with its own support tier, and the key-backup server can be the customer's own. The data processing agreement commits to returning or deleting personal data at the customer's choice when the contract ends, the apps' source code is public, and Threema Libre is distributed through F-Droid with a documented backup-and-restore migration path. OnPrem pricing is available only through sales contact, and we found no public information on server-side source availability or federation. 1 2 6 10 14
The Works Council Advocate
An OnPrem plan offers self-hosting with full control over infrastructure and data, white-labelling of all apps and air-gapped operation, and the Threema Safe backup can run on the customer's own server. The apps are open source with publicly viewable code, Threema Libre ships via F-Droid from the vendor's own repository with a documented backup-and-restore migration, and on termination personal data is returned or deleted at the customer's choice. We found no public information on feature parity between the cloud and self-hosted editions. 1 2 1 4 6 10 14
The Compliance Counsel
Self-hosting is real: an on-premises edition is sold as its own plan with air-gapped operation, white-labeling and a six-hour support response, and the processing agreement obliges Threema to return or delete data at the customer's choice when the contract ends. Open-source apps with reproducible builds, a documented backup-and-restore migration to Threema Libre, and a self-hostable key-backup server make exit credible. We found no public information on a complete export of messages, files and metadata, and the captured pages do not establish that the server code itself is open. 1 2 1 6 10 14
The Platform Engineer
Self-hosting is a supported, sold deployment rather than a hobby build: the OnPrem plan offers self-hosting, white-labeling of all apps and air-gapped operation, and the Work apps are open source with the source code listed among the documents handed over under the agreement. Threema Safe backups can be self-hosted on the customer's own server. We found no public information on a complete organisational export of the message archive or on open protocol federation — messages live on devices and users export their own chats, with the agreement covering return or deletion of the data the processor holds. 2 6 9 10 11
The Skeptic
Self-hosting exists as a separate OnPrem plan with white-labeling and air-gapped operation, and key backups can run on the customer's own server, but the OnPrem tier is a sales conversation and its parity with the hosted service is not documented. The contract provides return-or-deletion of personal data at the customer's choice at contract end rather than a documented full export of messages, files and metadata, and we found no public information on a migration path in or out; the client apps are open source, while nothing captured describes the server that way. 1 2 4 6 10 14
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
There is a documented Threema Gateway API for sending, receiving and processing messages from a company's own software, a Broadcast API with documentation for feeds, distribution lists and groups, an admin API for automated administration, and a list of named integrations including Wazuh, Userlike, IncaMail and the open-source Grafana and Mattermost projects. We found no public information on webhooks, an app framework, SCIM provisioning, rate limits or a sandbox, and the AI bridge is only announced as coming soon. 15 16 2 6
The Security Officer
A documented API dispatches broadcast messages and manages feeds, distribution lists and groups, an admin API automates administration, and Threema Gateway embeds sending, receiving and processing Threema messages in third-party software. Named integrations include Grafana, Mattermost, Wazuh, IncaMail, Userlike, Whappodo and a xenForo two-factor plugin, and Broadcast includes bots and scheduled messages. We found no public information on webhooks, an app framework with interactive components or SCIM provisioning; directory synchronisation with Azure Active Directory is offered at an additional charge. 2 6 15 16
The Works Council Advocate
A documented Threema Gateway API lets companies send, receive and process Threema messages from their own software, a Broadcast API dispatches messages and manages feeds, distribution lists and groups, and there is an API for automated administration alongside MDM support, bots and AAD synchronisation at an additional charge. Named integrations include IncaMail, Userlike, Wazuh, Whappodo and an xenForo two-factor plugin; we found no public information on an app framework, SSO or SCIM provisioning. 2 1 15 16
The Compliance Counsel
A documented Broadcast API, an API for automated administration, and the Threema Gateway for two-way message integration — with named adopters including Mattermost, Grafana, IncaMail and Wazuh — form a genuine integration surface. We found no public information on an app framework with interactive components, event subscriptions, SCIM provisioning or documented rate limits; Azure AD synchronisation is offered at an additional charge whose amount is not stated. This is messaging plumbing, not a platform. 2 6 15 16
The Platform Engineer
There is a real, buildable API surface: Threema Gateway for sending, receiving and processing messages from third-party software, a documented Broadcast API for feeds, distribution lists and groups, an admin API for automated administration, and bots in the Broadcast feature set, plus named integrations including Wazuh, IncaMail, Userlike and open-source projects like Grafana and Mattermost building on the Gateway. Directory synchronisation with Azure Active Directory is offered at an additional charge. We found no public information on an app framework with interactive components, SSO or SCIM provisioning, documented rate limits or a sandbox. 2 6 15 16
The Skeptic
A documented API exists for broadcast dispatch and for managing feeds, distribution lists and groups, plus a gateway to send, receive and process Threema messages from third-party software, an admin API for automated administration, bots among the broadcast features, and named integrations including Grafana, Mattermost and IncaMail. We found no public information on an app directory, webhooks, SCIM provisioning, rate limits or a sandbox; API access sits in the Professional tier and Azure Active Directory synchronisation carries an unspecified additional charge. 2 6 15 16
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
The contracting entity is Threema AG of Pfäffikon, running company-owned servers in two ISO 27001-certified data centers in Zurich, with an Article 27 GDPR representative in Bonn, a published data processing agreement whose Annex 3 lists subprocessors with locations, and the customer able to disable the functions that require them — including the one named US service, hCaptcha. The vendor also states it is not subject to the US CLOUD Act, and a self-hosted option exists on top. Swiss rather than EU jurisdiction and that single named US subprocessor keep this one notch short of the fully sovereign end of the scale. 6 3 3 5 4
The Security Officer
Threema AG of Pfäffikon, Switzerland runs its own servers in two ISO 27001-certified data centers in Zurich for all essential Threema Work functions, publishes a data processing agreement under Swiss law that acknowledges GDPR, names an EU representative in Bonn and a UK representative, and offers a self-hosted OnPrem edition; the captured pages give different company names for the server operator, with the imprint showing Threema AG. Subprocessors are named with locations — Aivie in Zurich, Livestorm hosted in Ireland, Myra in Munich, and hCaptcha of Intuition Machines in the USA — the customer can disable the functions that require them, and group calls may use media routers abroad. This is a strongly European chain, with the American captcha service and the foreign media routers as the named exceptions. 2 3 5 6 13 3
The Works Council Advocate
The contracting entity is Threema AG in Pfäffikon with an EU representative under Art. 27 GDPR, hosting runs on the vendor's own servers in two ISO 27001-certified data centers in Zurich, and a published data processing agreement carries a subprocessor annex with Aivie in Switzerland, Livestorm in Ireland, Myra in Germany and hCaptcha in the USA — the customer can disable the functions that need these subprocessors. Group-call media routers abroad are named and see no participant identities, and the vendor is not subject to the CLOUD Act. The residency statement covers only the essential functions of the work apps and Switzerland is not an EU member state, which is why this lands one step below the fullest level. 3 4 6 13 3
The Compliance Counsel
The vendor is a Swiss company on its own hardware in two ISO 27001-certified Zurich data centres, processing core functions exclusively in Switzerland, with an Article 27 GDPR representative in Bonn and a published processing agreement carrying a subprocessor register with locations — Aivie in Zurich, Livestorm hosted in Ireland, Myra in Germany. Residual exposures are named rather than buried: hCaptcha operates in the USA, and media routers abroad can carry group-call traffic. The agreement's audit right, the 14-day objection window to new subprocessors, and the stated freedom from the CLOUD Act carry weight with me; Switzerland is not the EU and one subprocessor is American, which caps it. 3 4 5 6 13 3
The Platform Engineer
The chain is unusually well evidenced: hosting exclusively on Threema's own servers in two ISO 27001-certified data centres in Zurich, a Swiss contracting entity with an Art. 27 GDPR EU representative in Bonn and a UK representative, and a published data processing agreement with a subprocessor annex naming locations — Idea 2 in Switzerland, Livestorm in Ireland, Myra in Germany — while non-European processing is named rather than hidden: hCaptcha in the USA and media routers abroad for group calls, which the vendor states cannot see participant identities. The customer can disable the functions requiring subprocessors, the vendor states it is not subject to the US CLOUD Act, and the OnPrem plan removes the hosting question entirely. 2 3 4 6 13 3
The Skeptic
The contracting entity is Threema AG in Pfäffikon, Switzerland, with an Article 27 GDPR representative in Bonn; hosting runs on the vendor's own hardware in two named Zurich data centers, and freedom from the US CLOUD Act is stated outright. A data processing agreement is published with a subprocessor annex, and the chain is named with locations — including the US hCaptcha service and media routers abroad for group calls — with the customer able to switch off the functions that require them. What holds this below the top: Switzerland is not the EU, the ISO 27001 certificate belongs to the colocation partner rather than the vendor, and the self-hosted edition is priced only on request. 2 3 4 5 6 13 3
Pricing transparency
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
Both main plans are priced publicly — EUR 3.00 monthly, per user for Core with annual payment, and EUR 5.00 monthly, per user for Professional — with per-plan user caps, SLA percentages, support response times, gateway credits and a 30-day trial for 30 users without payment data. The self-hosted plan is quoted only as CUSTOM, and VAT treatment and a minimum subscription term are not stated, so the annual invoice for a self-hosted deployment cannot be computed from public pages. 2 4 1
The Security Officer
Core at EUR 3.00 monthly, per user and Professional at EUR 5.00 monthly, per user are published with annual payment stated and compared across availability guarantees, support response times, user limits, gateway credits and API access. A 30-day trial for 30 users requires no payment data and has no automatic renewal, and Private is EUR 6.00 one-time for individuals. The on-premises tier is priced as custom on request, and we found no public information on VAT treatment, minimum subscription term, or history and storage limits per plan. 1 2 1 4
The Works Council Advocate
Core at EUR 3.00 per user monthly with annual payment, Professional at EUR 5.00 per user monthly with annual payment and a Private licence at EUR 6.00 one-time are public, with a comparison covering user limits, gateway credits, broadcast licences, SLA levels and support response times, plus a 30-day trial for 30 users without payment data or automatic renewal. The self-hosted OnPrem plan is listed only as custom pricing, the AAD synchronisation is an unspecified additional charge, and we found no public information on VAT treatment or the minimum subscription term for the paid tiers. 1 2 1 4 6
The Compliance Counsel
Both cloud tiers are priced publicly — EUR 3.00 monthly per user for Core (capped at 200 users) and EUR 5.00 monthly per user for Professional, billed annually, with SLA, support response times and gateway credits listed per tier — so the cloud invoice for a given headcount is computable. The on-premises edition is priced only as "CUSTOM", the Azure AD synchronisation carries an unstated "additional charge", and VAT treatment is not stated on the captured pages. The processing agreement does fix a one-year term with three months' notice and automatic renewal. 1 2 6
The Platform Engineer
The main tiers are priced publicly — Core at EUR 3.00 monthly, per user and Professional at EUR 5.00 monthly, per user, both with annual payment stated — alongside per-tier features, guaranteed availability of 99.5% versus 99.9%, support response times, gateway credits and a 30-day trial for 30 users without payment data. The OnPrem plan is priced only as "CUSTOM", the Azure AD synchronisation surcharge is unnamed, and we found no public information on VAT treatment. The agreement sets a one-year term with automatic renewal and three months' notice, and bills audit work and data-subject-request support to the customer. 1 2 4 6
The Skeptic
Core at EUR 3.00 and Professional at EUR 5.00 monthly per user are public with annual payment stated, and the per-tier boundaries are listed: user caps, gateway credits, SLA percentages, support response times and a 30-day trial for 30 users without payment data. The exclusions are the ones I read for: the OnPrem tier is listed as custom-priced, Azure Active Directory synchronisation is an additional charge without a figure, and we found no public information on VAT treatment, storage or history limits, or the price of audit and data-subject-request support, which the contract puts on the customer. 1 2 4 6
European sovereignty — proven facts
3 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 CH
unverified
Why unverified?A security FAQ page refers to 'Threema GmbH' running the servers, but the imprint and privacy policy consistently identify Threema AG, Pfäffikon SZ, Switzerland as the single company with no parent-subsidiary structure. |
2/2 pts | 5 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Hosting is exclusively in Switzerland (not an EU/EEA member state, though counted as such), the statement is limited to Threema Work processing for its 'essential functions', and the website privacy policy separately discloses transfers to third-party services such as Livestorm SAS (Ireland) and Myra (Germany). |
4/4 pts | 6 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?Self-hosting is offered only as a separate 'OnPrem' plan with custom pricing and a contact-sales process, while the standard plans are cloud subscriptions. |
1/1 pts | 2 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Threema Work
Is Threema Work European?
Yes. whats-best.ai classifies Threema Work as EU-Made. Its vendor, Threema GmbH, is incorporated in Switzerland, per the vendor’s page captured 16 Nov 2026.
Where does Threema Work store data?
Threema Work stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Switzerland as hosting location, per the vendor’s page captured 9 Nov 2026.
Does Threema Work have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Threema Work?
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: Threema Work alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. A security FAQ page refers to 'Threema GmbH' running the servers, but the imprint and privacy policy consistently identify Threema AG, Pfäffikon SZ, Switzerland as the single company with no parent-subsidiary structure.
- Weak sourcing — Hosting location. Hosting is exclusively in Switzerland (not an EU/EEA member state, though counted as such), the statement is limited to Threema Work processing for its 'essential functions', and the website privacy policy separately discloses transfers to third-party services such as Livestorm SAS (Ireland) and Myra (Germany).
- Weak sourcing — Hosting options. Self-hosting is offered only as a separate 'OnPrem' plan with custom pricing and a contact-sales process, while the standard plans are cloud subscriptions.
- 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 compliance 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
- 3 legal 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
- 2 subprocessors 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (17)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page threema.ch Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 2 Pricing threema.ch Checked 16 Nov 2026 Details →
- 3 Privacy policy threema.ch Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 4 Security / trust page threema.com Checked 16 Nov 2026 Details →
- 5 Imprint threema.com Checked 16 Nov 2026 Details →
- 6 Data processing agreement (dpa) threema.com Checked 16 Nov 2026 Details →
- 7 Channels, threads & search — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 8 Channels, threads & search — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 9 Encryption & access control — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 10 Encryption & access control — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 11 Retention, discovery & co-determination — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 12 Retention, discovery & co-determination — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 13 Deployment & data custody — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 14 Deployment & data custody — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 15 Integrations & extensibility — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 16 Integrations & extensibility — found from sitemap threema.com Checked 1 Oct 2026 Details →
- 17 Structured-data backfill: markup only, no text or screenshot threema.ch Checked 8 Nov 2026 Details →