whats-best.ai
Search Sign in

Business Instant Messaging

Wire (Messaging)

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Wire Swiss GmbH · wire.com

Compare with Threema Work → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Platform Engineer

Weighted verdict

Would rather run it than rent it, and wants to know whether that is a supported deployment or a hobby build. Cares about open protocols, federation, a plugin system with real permissions, and an upgrade path that does not orphan the customisations.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Platform Engineer

Channels, threads & search

How this is scored

The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.

0 — Flat group chats with no threads; search covers recent messages only, and history is capped.

3 — Channels and direct messages with basic search, but threading is awkward or absent and file handling is a plain attachment list.

5 — Public and private channels, real threads, mentions and reactions, file sharing with previews, and full-text search across the whole 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 a documented history limit or none at all.

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.

Report an error

The Platform Engineer

The evidence gives me group conversations up to 500 (2000 with MLS), file sharing, self-deleting messages and custom folders, but not one word on threading, mentions, reactions, or search — and search that finds an eighteen-month-old decision is architecturally doubtful when servers delete message payloads on delivery. Threading absent and search unevidenced puts this at the basic-chats anchor, nothing higher. 2 4

Report an error

Encryption & access control

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 — Transport encryption only, undocumented; no role model beyond admin, guests indistinguishable from members.

3 — TLS and encryption at rest with vendor-held keys, basic roles, and guest access that mostly works.

5 — The above plus configurable roles per channel, SSO, guest accounts with scoped visibility, and a clear statement of what the vendor can read.

8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, device verification, session management an admin can revoke, 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.

Report an error

The Platform Engineer

This is the full ten: end-to-end encryption as the default mode for text, voice, video and files, MLS as the underlying open protocol co-developed publicly, open-source code on GitHub, certificate-based identity verification via ID Shield, encrypted history backup for multi-device key survival, and a plain vendor statement that Wire has no access to keys and no backdoors. SSO/SAML, SCIM and password-gated guest roles round out access control. 1 2 3 4

Report an error

Retention, discovery & co-determination

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.

0 — No retention policy, no export beyond a manual copy, no audit log, and presence or activity analytics that cannot be disabled.

3 — Manual export of some data and a global history limit, but no per-channel retention, no audit log and no admin control over analytics.

5 — Configurable retention per channel or workspace, admin export in a documented format, an audit log of administrative actions, and status or presence that a user can control.

8 — Legal-hold and eDiscovery export including edits and deletions, retention executed per policy and evidenced, full admin audit trail, and 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 no individual-level productivity scoring anywhere in the product.

Report an error

The Platform Engineer

The archive as a legal object barely exists here: retention means self-deleting messages and a purpose-based deletion rule, with no per-channel retention, no audit log, no legal hold, and no export-for-discovery capability evidenced anywhere in the evidence. Credit where due on the works-council side — analytics is self-hosted, consent-based Countly with no vendor data sharing and no productivity scoring — but eDiscovery and audit are simply silent, and that caps it at the bottom anchor that matches. 2 4

Report an error

Deployment & data custody

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 — Cloud-only, proprietary, with export limited to a partial archive.

3 — Cloud-only, but with a documented full export in an open-ish format.

5 — A private-cloud or dedicated-instance option, or a self-hosted edition that lags the cloud significantly; full export documented.

8 — A genuine self-hosted edition close to feature parity, or 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.

Report an error

The Platform Engineer

This is the part I came for: 100% open-source code on GitHub, an on-premises deployment offered with 'comprehensive' support, real federation over MLS, and a deployment-options page — custody can plausibly be the customer's. What keeps it off the top anchor is that on-prem and data sovereignty sit behind a custom-priced Enterprise tier rather than a documented self-hosting path, and the evidence is silent on any export or migration route in and out. 1 2 3

Report an error

Integrations & extensibility

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 — No API, no webhooks, no bots.

3 — Incoming webhooks and a handful of native integrations; no bot framework, no documented limits.

5 — Documented REST API, incoming and outgoing webhooks, slash commands, a bot account model, and SSO.

8 — A proper app framework with interactive components, event subscriptions with retries, 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.

Report an error

The Platform Engineer

There is a bot capability the admin console can deploy and one named native integration (GitHub), plus SSO and SCIM — but no documented REST API, no webhooks, no slash commands, no rate limits, and nothing resembling an app framework with auditable permissions. That lands between the webhook-only anchor and the documented-API anchor: real bot accounts and provisioning, but the extensibility surface is unevidenced and probably a partner conversation. 1 2

Report an error

European sovereignty

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.

0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.

3 — EU data residency offered for message content while metadata, search indexes or support tooling remain non-EU, or the contracting entity sits outside the EU.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — notifications, AI features, analytics — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, full subprocessor list published, 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.

Report an error

The Platform Engineer

Hosting is EU as standard (servers in Germany and Ireland, AWS EU) and the subprocessor list is genuinely published down to Stripe in the USA with DPF certification named — better than most. But the contracting entity is Wire Swiss GmbH, with Wire Germany GmbH existing only as an Article 27 representative, so the EU-entity condition fails, and the sovereignty pipeline could not confirm data residency on the vendor's own pages; the on-prem option that would moot all this is gated behind Enterprise sales. 3 4

Report an error

Pricing transparency

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 per-user headline exists, but the tier where retention control, SSO or compliance export begins is unstated.

5 — Per-user prices public with billing period stated, but at least one commonly needed capability (unlimited history, SSO, eDiscovery) sits in an unpriced enterprise tier.

8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries, 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.

Report an error

The Platform Engineer

Free (5 users), SMB at €7.45/person/month annually or €8.94 monthly with billing period stated and SSO/SCIM included — but everything a compliance-driven buyer actually wants priced (federation, ID-Shield, data sovereignty, on-prem deployment support) sits in an unpriced Enterprise tier above 100 people. VAT treatment, storage limits, guest pricing and minimum term are all unstated, so the annual invoice is not computable from public pages alone. 2

Report an error

European sovereignty — proven facts

3 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency EU only ⚠ unverified 3/3 pts 3 Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 4 Report an error

Where this could be wrong

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.

Do you know more about Wire (Messaging)? Tell us Report an error on this page

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage wire.com Checked 15 Sep 2026 Details →
  2. 2 Pricing wire.com Checked 15 Sep 2026 Details →
  3. 3 Security page wire.com Checked 15 Sep 2026 Details →
  4. 4 Privacy policy wire.com Checked 30 Sep 2026 Details →
  5. 5 Imprint wire.com Checked 30 Sep 2026 Details →
  6. 6 Channels, threads & search — found from sitemap wire.com Checked 1 Oct 2026 Details →
  7. 7 Channels, threads & search — found from sitemap wire.com Checked 1 Oct 2026 Details →
  8. 8 Encryption & access control — found from sitemap wire.com Checked 1 Oct 2026 Details →
  9. 9 Encryption & access control — found from sitemap wire.com Checked 1 Oct 2026 Details →
  10. 10 Retention, discovery & co-determination — found from sitemap wire.com Checked 1 Oct 2026 Details →
  11. 11 Retention, discovery & co-determination — found from sitemap wire.com Checked 1 Oct 2026 Details →
  12. 12 Deployment & data custody — found from sitemap wire.com Checked 1 Oct 2026 Details →
  13. 13 Integrations & extensibility — found from sitemap wire.com Checked 1 Oct 2026 Details →
  14. 14 Integrations & extensibility — found from sitemap wire.com Checked 1 Oct 2026 Details →