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 Works Council Advocate
Knows that a chat log is a record of who spoke to whom at what hour. Wants presence a person controls, no individual activity scoring anywhere, retention that deletes rather than hides, and analytics that can be switched off across the organisation.
Threema Work
Wire (Messaging)
This judge's pick
Criterion by criterion
Channels, threads & search
Threema Work
Group chats, reactions, polls and file sharing are confirmed, but the evidence shows no threads, no channels, no mentions, and no search capability at all — eighteen months back, a decision here is found by scrolling, if the client still holds it. External communication is only a 'coming soon' EasyConnect. This sits between the flat-chats anchor and the basic-search anchor, closer to the bottom.
Wire (Messaging)
Messaging, file sharing, audio/video messages and 500–2000-participant chats are confirmed, but the evidence is silent on channels, threading, mentions and search entirely — I cannot confirm a decision from eighteen months ago could be found again. A chat log nobody can search is not a record, it is a rumour. Scored just above the flat-chat floor for what is evidenced, held down by what is not.
Encryption & access control
Threema Work
End-to-end encryption is not an option, it is the product, with the vendor stating plainly that 'not even Threema has access', plus Perfect Forward Secrecy, open source code and regular independent audits. I dock a point only because the evidence is silent on device verification, cross-device key handling and admin session revocation — everything else here is what I would demand in a works agreement.
Wire (Messaging)
This is the rubric level 10 case in full: MLS end-to-end encryption as the only mode, open source on GitHub, ID Shield automatic certificate-based device checks so ordinary people survive key management, and the vendor stating plainly it has no access to keys and no backdoors. Multi-device E2EE across 8 devices, SSO/SAML and SCIM, guest links with passwords and password-restricted guest roles complete the picture.
Retention, discovery & co-determination
Threema Work
The only retention numbers in the whole sheet are for website cookies, forms and truncated IP logs — nothing on message retention policy, admin export, eDiscovery or an audit log for the product itself. On the plus side for co-determination: no activity analytics or individual scoring is evidenced anywhere, and there is an off-hours policy plus availability status, which is exactly the presence control I ask for. Absence of the legal-tooling half pulls this down to just above the manual-copy anchor.
Wire (Messaging)
The deletion posture is what I fight for: messages leave the servers on delivery, retention is purpose-bound, self-deleting messages exist, and the vendor confirms no automated decision-making, no profiling and consent-based, self-hosted Countly analytics that share nothing — no individual activity scoring anywhere. But the legal-object half is absent from the evidence: no audit log of administrative actions, no documented admin export, no eDiscovery or legal hold, and an availability status with no evidenced user control. Deletion by default keeps it above the middle; the missing audit trail keeps it below it.
Deployment & data custody
Threema Work
OnPrem self-hosting with air-gapped operation, white-labeling and an admin API is genuine custody, not a checkbox, and the cloud runs on the vendor's own servers in named Zurich data centres. But the evidence evidences no export or migration path in or out, no federation, and OnPrem is priced 'custom' rather than sold as a first-class public deployment — so a real exit is asserted, not documented.
Wire (Messaging)
Custody is genuinely achievable: 100% open source code on GitHub, comprehensive on-premises deployment support 'every step of the way' in the government offering, plus federation and multi-tenancy. What holds it back is that the evidence documents no export or migration path — an exit is implied by self-hosting rather than written down — and on-prem sits in an unpriced enterprise tier. Seven, not eight.
Integrations & extensibility
Threema Work
There is a real API surface — integration API, admin API, Broadcast API with bots and feeds, MDM, metered gateway credits — but no webhooks, no slash commands, no app framework, no SCIM, no documented rate limits or sandbox, and directory sync with AAD costs extra without a stated price. This is automation plumbing above the webhook anchor, well short of the documented-API-platform anchor.
Wire (Messaging)
Admins can deploy third-party integrated apps (bots), GitHub is listed, and SSO with SCIM provisioning is real — but that is the whole integrations story the evidence tells. No documented REST API, no webhooks, no slash commands, no rate limits, no sandbox. Just enough to be more than a closed app, nowhere near a platform.
European sovereignty
Threema Work
The contracting entity Threema AG is Swiss, not EU — they even need an Art. 27 GDPR representative in Bonn — and hosting is on their own servers at a named ISO 27001 colocation partner in Zurich, which is geographically European but contractually outside the EU. Only one subprocessor (Livestorm, Ireland, webinars) is disclosed, and the pipeline itself marks product subprocessor exposure unknown. Switzerland on own infrastructure is better than most non-EU setups, but the entity and the undisclosed chain keep this just above the bottom anchors.
Wire (Messaging)
The substance is largely there: servers in Germany and Ireland, a full published subprocessor list with locations, and the one US processor (Stripe) named with its transfer safeguards and DPF certification. But the contracting entity is Wire Swiss GmbH in Zug, with Wire Germany GmbH existing only as an Article 27 representative — the anchor's named failing condition — and ownership is unknown. European in substance, not in contracting party; five.
Pricing transparency
Threema Work
Core at EUR 3 and Professional at EUR 5 per user per month, with annual billing stated, lets a buyer compute the SaaS invoice for any headcount. But the compliance-relevant choices — self-hosted OnPrem at 'custom', and AAD sync as an unpriced additional charge — sit behind a sales conversation, and minimum term and VAT treatment are unstated; only a 30-day trial is public.
Wire (Messaging)
Free (5 people), SMB at €7.45/person/month annual or €8.94 monthly with SSO, SCIM and guest roles included, billing period stated — so a 100-person invoice is computable. But every organisation above 100 people, which is where the works councils I represent live, gets 'Custom', holding federation, data sovereignty and on-prem hostage to a sales conversation, and VAT, minimum terms and guest pricing are unstated. A clean five, no more.
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