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 Compliance Counsel
Will one day have to produce this archive, edits and deletions included, to a regulator or a court. Wants legal hold, an export a lawyer can work from, retention per channel, and an audit trail that survives the admin who made the change.
Threema Work
Wire (Messaging)
This judge's pick
Criterion by criterion
Channels, threads & search
Threema Work
Flat group chats, direct messages, file sharing, polls and reactions are evidenced, but no channels, no threads, no mentions, and no search capability appears anywhere in the registry. For a decision made eighteen months ago, the evidence gives me nothing to find it with.
Wire (Messaging)
Nothing on the evidence evidences a channel model, threading, or search at all — it names group conversations (up to 500 participants), file sharing and self-deleting messages, and stops there. For a criterion that turns on finding a decision from eighteen months ago, silence on search is decisive, and self-deleting messages plus server-side deletion on delivery point the wrong way for an archive.
Encryption & access control
Threema Work
End-to-end encryption is the first-class mode, not an option: zero-knowledge with the vendor stating plainly it cannot read content, Perfect Forward Secrecy, open source, and regular independent audits, with MDM central access control and two-factor authentication. Only the missing documentation of identity verification and cross-device key management keeps this off the top anchor.
Wire (Messaging)
This is the rare case where the vendor states plainly what it cannot reach — 'Wire does not have access to encryption keys and does not use backdoors' — backed by fully open source MLS cryptography, certificate-based identity verification (ID Shield), manual device verification, encrypted history backup and password-protected guest links. End-to-end encryption is the default mode for text, voice, video and files, not an optional bolt-on.
Retention, discovery & co-determination
Threema Work
No message retention policy, no per-channel retention, no discovery export, no audit log and no legal hold is evidenced — the only retention facts concern website visitor data such as contact forms, cookies and server logs. Zero-knowledge architecture means the vendor cannot produce my archive at subpoena time and no client-side export is offered to compensate, while edit and delete of messages carries no history.
Wire (Messaging)
There is no evidenced admin export, no legal hold, no audit log of administrative actions and no customer-configurable retention — the only retention statements are the vendor's own privacy-policy deletion clocks (90-day logs, 365-day usage data). Worse, server-side message copies are deleted on delivery and self-deleting messages are a marketed feature, so a subpoena would find nothing to produce; only consent-based self-hosted Countly analytics and the absence of any productivity scoring keep this just off the floor.
Deployment & data custody
Threema Work
Custody is genuinely available: an OnPrem plan with self-hosting, air-gapped operation, white-labeling and its own 6-hour support tier, on own servers in named Zurich data centres. But the OnPrem licence is priced only as CUSTOM and no export or migration path in and out is documented, so the exit story is unproven.
Wire (Messaging)
Custody is genuinely obtainable: the source code is fully open on GitHub, with comprehensive on-premises deployment support, federation and data-sovereignty editions — self-hosting removes the vendor from my archive entirely. What the evidence never evidences is a documented export or migration path in and out, which the top anchor demands and my exit planning requires.
Integrations & extensibility
Threema Work
There is real surface: an integration API, Broadcast API with bots and feeds, an admin API, MDM and AAD sync. But no webhooks, no slash commands, no SSO statement, no documented rate limits or sandbox, and the AI bridge is still 'coming soon'.
Wire (Messaging)
The admin console can deploy third-party integrated bots and SSO with SCIM provisioning is priced into the SMB tier, but the evidence evidences no REST API, no webhooks, no slash commands and no documented limits — a single listed GitHub integration is the entire visible catalogue.
European sovereignty
Threema Work
The vendor's own pages state own servers in two ISO 27001-certified data centres in Zurich, a named Swiss controller, an Art. 27 GDPR representative in Bonn, and one named subprocessor (Livestorm, hosting in Ireland) — stronger custody than the pipeline's 'unknowns' suggest. But the contracting entity sits outside the EU and no full subprocessor list for the messaging service is published.
Wire (Messaging)
Message hosting sits in Germany and Ireland with a published, located subprocessor list in which the one US processor (Stripe) is named alongside its transfer safeguards — but the contracting entity is Wire Swiss GmbH in Zug, Wire Germany GmbH exists only as an Article 27 representative, and ownership is unknown. The on-premises and data-sovereignty editions are the escape hatch that keeps this above the middle of the scale.
Pricing transparency
Threema Work
Core (EUR 3/user/month, annual payment) and Professional (EUR 5/user/month) are public with tier boundaries like gateway credits and support response times. The deployment I would actually buy — OnPrem — is CUSTOM, AAD sync is 'additional charge' with no figure, and VAT treatment and minimum term are unstated, so the annual invoice is not computable.
Wire (Messaging)
Free and SMB tiers are priced per person with billing periods stated (€7.45 annual, €8.94 monthly) and SSO/SCIM included at the paid tier — but everything a regulated buyer like me actually needs, data sovereignty, federation, on-premises support, sits in unpriced 'Custom' Enterprise terms, and VAT treatment plus history and storage limits are unstated.
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