The six-judge panel splits rather than settles. Wire is ahead on encryption and access, 9.5 to 8.5, 6 judges lean Wire, 0 ties; on deployment control, 7.7 to 7.3, 3 lean Wire, 1 Threema Work, 2 tie; and on sovereignty, 5.2 to 5.0, 4 lean Wire, 2 Threema Work. Threema Work holds the higher governance and discovery mean, 2.5 to 2.3, with 1 lean and 5 ties. Messaging core (2.2 each), integrations (4.0 each) and pricing transparency (5.2 each) are even. Weighted totals also split: security officer 6.2 vs 5.2, works council 5.4 vs 5.0, compliance counsel 4.6 vs 4.5 and skeptic 5.0 vs 4.6 favor Wire; messaging team lead 4.3 vs 4.1 and platform engineer 5.8 vs 5.6 favor Threema Work. Both list a Swiss legal entity, unknown ownership and EU-only residency; subprocessor exposure differs: EU-only for Threema Work, US Cloud Act for Wire.
Choose Threema Work if
Your platform engineering team leads the evaluation: its weighted total is 5.8 for Threema Work against 5.6 for Wire.
Your messaging team lead signs off: the weighted total is 4.3 for Threema Work against 4.1 for Wire.
You need air-gapped, self-hosted operation with white-labeling: the deployment control verdict for Threema Work evidences self-hosting, air-gapped operation and white-labeling on its OnPrem tier, and 1 judge leans Threema Work on that criterion.
Your procurement requires subprocessor exposure within the EU: Threema Work's sovereignty attribute is EU-only for subprocessor exposure, while Wire's is US Cloud Act.
Choose Wire (Messaging) if
You need end-to-end encryption as the default for text, voice, video and files: Wire's encryption and access mean is 9.5 against 8.5, with 6 judges leaning Wire and 0 ties.
Your security officer makes the call: the weighted total is 6.2 for Wire against 5.2 for Threema Work.
Your works council weighs in: its weighted total is 5.4 against 5.0, and the governance verdict credits deletion-on-delivery plus consent-based, self-hosted analytics.
You want servers in Germany and Ireland with a published subprocessor list: 4 judges lean Wire on sovereignty, 5.2 against 5.0.
Your compliance counsel and the skeptic judge both review the buy: their weighted totals favor Wire at 4.6 vs 4.5 and 5.0 vs 4.6.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Skeptic
Reads for the message-history cap, the tier where SSO appears, and what "unlimited" excludes. Has seen "end-to-end encrypted" mean direct messages only, on request, with search disabled — and wants that sentence found rather than assumed.
Threema Work
Wire (Messaging)
This judge's pick
Criterion by criterion
Channels, threads & search
Threema Work
Flat group chats with reactions, polls, message editing and file sharing, but no channels, no threads, no mentions, and not one word about search — and given the zero-knowledge claim the vendor structurally cannot search the archive server-side, so an eighteen-month-old decision is unfindable by design. No conversation export is evidenced either. Structure sits below the anchor-3 bar (no channels, no documented search); feature richness sits above rubric level 0, so I split at 2.
Wire (Messaging)
The evidence evidences group chats up to 500 people, file sharing and self-deleting messages — and not one word about channels, threads or search; that word never appears, so a decision made eighteen months ago is retrievable by nothing this sheet shows. Worse, messages are deleted from Wire's servers 'immediately upon delivery', so there is barely an archive to search. A flat-messenger profile with ephemeral history, well below the channels-and-threads anchor.
Encryption & access control
Threema Work
The sentence I hunt for is actually here: end-to-end encryption is the default mode with the vendor stating plainly what it cannot decrypt ('not even Threema has access'), backed by Perfect Forward Secrecy, open source, independent audits, 2FA and PIN-protected chats. Held at 8, not 10, because identity verification and key handling are asserted as principles rather than documented mechanisms, and SSO appears in no tier at all — the closest is AAD sync at an unstated 'additional charge'.
Wire (Messaging)
The sentences I hunt for exist verbatim: content is 'encrypted on the sender's device and decrypted only on the recipient's device' across text, voice, video and files, and 'Wire does not have access to encryption keys and does not use backdoors' — backed by MLS, an open standard, 100% open source on GitHub, manual device verification plus automatic certificate-based ID Shield, and encrypted history backup. Docked one point because admin-revocable session management is never named and the trade-offs of E2EE for search/discovery are not spelled out.
Retention, discovery & co-determination
Threema Work
Every retention statement in the evidence governs the vendor's website — cookies, server logs, support forms — while the messaging archive gets no retention policy, no audit log, no legal hold, no discovery export; under zero-knowledge the vendor cannot produce an eDiscovery output even under subpoena. The lone works-council gesture is an off-hours policy, real but lonely. That is rubric level 0 plus one point.
Wire (Messaging)
As a legal object there is almost nothing: no configurable retention, no admin export, no audit log, no legal hold — the only retention rule on file is the server deleting messages upon delivery, which is the opposite of a discovery posture. The works-council side is genuinely clean, to be fair: consent-based self-hosted Countly analytics, a no-automated-decision-making declaration and no productivity scoring anywhere.
Deployment & data custody
Threema Work
OnPrem is a first-class tier with air-gapped operation and white-labeling, and the cloud service runs on Threema's own servers in Zurich — custody is genuinely transferable. It stays at 8 because 'Open Source' is a bare bullet with no scope stated, the migration path and complete export in and out of OnPrem are undocumented, and OnPrem is priced only as 'CUSTOM' — the vendor does not yet document the exit it enables.
Wire (Messaging)
Open-source code on GitHub, 'comprehensive on-premises deployment support' and federation listed at enterprise tier are real custody options, not slideware. But the evidence never documents an export or migration path out, so the exit story is assumed rather than evidenced, and on-prem sits behind a custom-priced enterprise conversation.
Integrations & extensibility
Threema Work
There are real server-side APIs — admin API, broadcast API, bots, feeds, scheduled messages — but nothing lives in the chat itself: no webhooks, no slash commands, no app framework, no SCIM, and no SSO in any tier; AAD sync is directory replication at an extra, unquoted charge and AIBRIDGE is 'coming soon'. That covers roughly half of the anchor-5 list, so I split between 3 and 5.
Wire (Messaging)
Exactly one integration is named (GitHub), bot deployment appears as an admin-console line, and SSO/SCIM is evidenced — beyond that, silence: no documented REST API, no webhooks, no framework, no rate limits, no sandbox. 'MS Teams alternative' is a use-case slogan, not an integration surface.
European sovereignty
Threema Work
The contracting entity is Threema AG, Switzerland, under Swiss FADP with GDPR only 'may additionally apply' and an Art. 27 representative in Bonn — an entity outside the EU is rubric level 3's own wording, and the pipeline's computed 3 agrees. Own-server hosting in Zurich is stable but not EU, and the only named subprocessor (Livestorm, Ireland) touches webinars, not the messaging service; no full subprocessor list is published.
Wire (Messaging)
Servers named in Germany and Ireland and a full subprocessor table with locations and DPF/SCC legal bases — Stripe in the USA is named rather than hidden, which is better than most. But the contracting entity is Swiss, not EU, Wire Germany GmbH is only an Article 27 representative, ownership is unknown, and the self-hosted option that would remove the question is gated behind unpriced Enterprise.
Pricing transparency
Threema Work
Core at EUR 3 and Professional at EUR 5 per user monthly with annual payment stated is computable — but the data-sovereignty capability sits in an OnPrem tier priced only 'CUSTOM' and AAD sync is 'additional charge' with no figure, so a compliance-conscious buyer cannot derive their annual invoice. VAT treatment and minimum term are unstated. That is rubric level 5 almost verbatim.
Wire (Messaging)
Per-user maths is public and clean up to 100 people — €7.45/person/month billed annually, €8.94 monthly, and SSO/SCIM included at that tier rather than enterprise-gated. But federation, data sovereignty, ID Shield and on-prem all sit in 'Wire for Enterprise — Custom', VAT treatment and minimum term are never stated, so the invoice for the regulated 300-person buyer this product courts is a sales conversation.
Sovereignty, side by side
Dimension
Threema Work
Wire (Messaging)
Legal entity
Not determined
Incorporated in CH
Ownership
Not determined
Not determined
Data residency
Not determined
EU only
Subprocessors
Not determined
US CLOUD Act reach
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
Compliance · Supervisory authority
Federal Data Protection and Information Commissioner (FDPIC) · Switzerland1