Wire (Messaging)
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 Wire Swiss GmbH · wire.com
Compare with Threema Work → 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.
Wire (Messaging) at a glance
- Vendor
- Wire Swiss GmbH
- Headquarters
- Incorporated in Switzerland source, captured 16 Nov 2026
- Data hosting
- In the EU; pages mention Germany and Ireland source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 19 Oct 2026
- Panel verdict
- The AI panel rates Wire (Messaging) 3.5/5, the mean of 6 judges. Wire, from Wire Swiss GmbH of Zug, is end-to-end encrypted messaging for regulated organisations, and the judges' scores cluster in narrow bands: strong on cryptography, weak on retention and discovery. how scores are made
- As of
- Vendor pages captured 19 Oct 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
Wire, from Wire Swiss GmbH of Zug, is end-to-end encrypted messaging for regulated organisations, and the judges' scores cluster in narrow bands: strong on cryptography, weak on retention and discovery. Encryption and access is the high point at 9-10, where encryption is the default on every plan, built on the MLS standard with the source on GitHub, and the vendor states it has no access to encryption keys and uses no backdoors. Deployment control scores 7-9 for documented on-premises and air-gapped operation on a codebase claimed 100% open source, and integrations 7-8 for an open SDK whose apps sit inside encrypted conversations. Governance and discovery is the low point at 3-4 and messaging core 4-5: no public information on administrative export, audit logs, legal hold or eDiscovery, custom retention scoped to the Private Cloud edition, and cross-platform backups marked "Coming soon". Pricing transparency is 5-6, with the small-team tier priced and self-hosting "Custom". Sovereignty scores 7-8 on servers stated in Germany and Ireland; no criterion spans more than two points, and no genuine split emerged.
Speaks for it
- End-to-end encryption by default on every plan for messages, files and calls, built on the MLS IETF standard with source on GitHub
- Vendor states it has no access to encryption keys and uses no backdoors, with device fingerprints, new-device alerts and certificate-based ID Shield verification
- Documented on-premises deployment including air-gapped operation, with all data and keys stated to stay under customer control
- Open integrations SDK whose apps act as members of end-to-end encrypted conversations, with the server seeing only encrypted data
- Public small-team pricing at €7.45 per person/month, annual payment or €8.94 per person/month, monthly payment, for up to 100 people
Held against it
- No public information on an administrative export of workspace data, an audit trail of administrative actions, legal hold or eDiscovery export
- Custom retention policies scoped to the Private Cloud deployment, with encrypted messages deleted from servers as soon as they are delivered
- No documented export or migration path out, with cross-platform backups and end-to-end encrypted history sharing marked "Coming soon"
- On-premises, private cloud and federation restricted to the Enterprise tier marked "Custom", with on-premises setup stated at 12-20 weeks
- Conversation search documented as available in groups only, with no public information on threaded replies or mentions
Best for
- Your organisation needs end-to-end encrypted messaging by default, on cryptography it can review in open source
- You are a regulated buyer able to take the Enterprise tier and run air-gapped on-premises with all data and keys under customer control
- Your developers need to build integrations to internal systems such as Jira or CI pipelines inside encrypted conversations
- You lead a team of up to 100 people and want SSO and SCIM on a tier with public per-user prices
Avoid if
- Your compliance duties require legal hold or discovery export — the documented posture deletes encrypted messages from servers upon delivery
- Your team depends on chat history as a knowledge base — cross-platform backups are "Coming soon" and search is documented within groups
- You must compute your invoice in advance for more than 100 people or any self-hosted deployment — those tiers are "Custom"
- You have no Kubernetes or Cassandra operations capability — on-premises installation, operation and maintenance are the customer's responsibility
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 2 of 5 |
| Encryption & access control | 5 of 5 |
| Retention, discovery & co-determination | 2 of 5 |
| Deployment & data custody | 4 of 5 |
| Integrations & extensibility | 4 of 5 |
| European sovereignty | 4 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
Public and private end-to-end encrypted channels, private groups, one-to-one messaging and encrypted file sharing are documented, but conversation search is only available within group conversations and global user search is a public-cloud matter. I found no public information on threaded replies, message editing history or pinned and saved items, and both cross-platform backups and end-to-end encrypted history sharing are marked "coming soon", so nothing here yet shows the archive working as a knowledge base. 2 6 7 2
The Security Officer
Public and private end-to-end encrypted channels, group and one-to-one conversations, encrypted file sharing, read receipts and conversation search are documented, and guest areas with password-protected links and custom permissions give external collaboration clear boundaries. We found no public information on threaded replies, mentions, search filters by channel or date, or message editing history, and cross-platform backup of the history is marked as coming rather than here, so the archive as a working knowledge base is not what these pages show. 6 7 14 2
The Works Council Advocate
Public and private encrypted channels, one-to-one and group chats, file sharing and conversation search are documented, with groups up to two thousand on MLS. We found no public information on threaded replies, mentions, or search filters by channel, person and date, and cross-platform backups and encrypted history sharing are shown as coming soon — so finding a decision from eighteen months ago is not something these pages promise. Read receipts and an availability status exist as features, which I note as a monitoring surface elsewhere. 6 7 2
The Compliance Counsel
Public and private end-to-end encrypted channels, group and one-to-one messaging, encrypted file sharing and conversation search are documented, which carries it past a basic group chat. We found no public information on threaded replies, mentions, search filters by channel, person or date, or a human-readable export of a conversation, and cross-platform history backup and end-to-end encrypted history sharing are each stated as coming soon. For a decision made eighteen months ago, the search and export evidence on these pages is thin. 2 6 7 2
The Platform Engineer
Public and private end-to-end encrypted channels, group chats, one-to-one messaging, file sharing and conversation search are documented, but I found no public information on threaded replies, mentions or filtered search by channel, person and date. The captured pages themselves mark cross-platform backups and E2EE history sharing as coming soon, so the eighteen-month archive story is partly a promise rather than a shipped feature. 6 7 2
The Skeptic
Public and private end-to-end-encrypted channels, one-to-one and group messaging, and file sharing are documented, with groups up to 500 (2000 with MLS enabled). But the daily surface thins out beyond that: conversation search is documented as available in groups with global user search tied to the public cloud, and we found no public information on threaded replies, mentions, message editing history, pinned items, or channel archiving. Cross-platform backup of chat history is marked "Coming soon", so the archive as a working knowledge base is not something the captured pages evidence. 6 2 7
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 on every plan, built on the open MLS standard with the source fully open, and the vendor states plainly that it has no access to encryption keys and uses no backdoors. Identity verification is covered twice — manual device fingerprints with new-device alerts, and automatic certificate-based ID Shield — alongside forward secrecy, post-compromise security and post-quantum readiness; the one gap is that encrypted history sharing and cross-platform backups are still "coming soon", so key management across devices with history intact is not yet fully evidenced. 4 7 8 2
The Security Officer
End-to-end encryption is the default on every plan, built on the MLS IETF standard with the source fully open on GitHub, local key storage, encryption at rest, forward secrecy and post-compromise security. Identity verification is what I look for: manual device fingerprints, alerts when a verified contact uses a new device, and certificate-based ID Shield checks against your identity provider that spare ordinary users manual comparisons, plus a plain statement that the vendor has no access to encryption keys and uses no backdoors. The one dent is that cross-platform backups of key material and history sharing are both marked as coming soon, which is the seam where users lose their own archive. 3 4 6 7 8 9 12 2
The Works Council Advocate
This is the standard a works council hopes for: messages, files and calls are end-to-end encrypted by default on every plan, the cryptography is open source on the MLS standard, and the vendor states plainly it has no access to encryption keys and cannot read the communication. Device fingerprints, new-device alerts and automated certificate-based identity checks tied to the identity provider give verification ordinary staff can survive, with up to eight devices in sync. Forward secrecy, post-compromise security and post-quantum-ready cipher suites are documented too. 7 4 8 3 2
The Compliance Counsel
End-to-end encryption is documented as the default on every plan, built on the open MLS standard, and the vendor states plainly that it has no access to encryption keys, uses no backdoors, and cannot see customer communication. Identity verification is covered by device fingerprints with new-device alerts and automatic certificate-based checks, while single sign-on, SCIM, password-protected guest links and administrative restriction of file sharing and guest links are listed as controls. 2 3 4 7 8 9 2
The Platform Engineer
End-to-end encryption is the default on every plan, built on the MLS IETF standard that Wire co-founded, with the source fully open on GitHub, keys stored locally, and the vendor stating plainly that it has no access to encryption keys and uses no backdoors. ID Shield automates certificate-based device verification so ordinary users are not hand-checking fingerprints, up to eight devices sync per account with cross-signed verification, and guest links are password-protected with admin-level restrictions on file sharing and guest access. This is encryption as the product's first-class mode with open cryptography, not a marketing adjective. 3 4 6 7 8 9 2
The Skeptic
End-to-end encryption is the default on every plan for messages, files and calls, built on the MLS IETF standard with the source on GitHub, and the vendor states plainly that it has no access to encryption keys and uses no backdoors. Identity verification is real rather than decorative — manual device fingerprints, an alert when a verified contact uses a new device, and certificate-based ID Shield tied to the identity provider — with SSO and SCIM arriving on the paid tier. The soft spots: two-factor authentication and admin session revocation are not documented, and the captured pages give different figures on history backup, with cross-platform backups marked "Coming soon". 4 7 9 3 2 6
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
Custom retention policies are documented but scoped to the Private Cloud deployment, alongside native self-deleting messages and an admin console covering members, guests, file-sharing and guest-link restrictions. I found no public information on organisation-wide export of workspace data, an audit log of administrative actions, legal hold or discovery export, and with cross-platform backups still marked "coming soon" an organisation's hold on its own archive rests on those retention settings alone. 2 6 12
The Security Officer
Retention is configurable in the Private Cloud edition, messages are deleted from the vendor's servers upon delivery, native self-deleting messages exist, and analytics runs consent-based on a self-hosted EU tool with automated decision-making stated as not used. We found no public information on admin export of workspace data, an audit or activity log of administrative actions, or legal-hold and discovery export — the pieces a subpoena and a works council will actually ask for. 4 6 12
The Works Council Advocate
Deletion here is real rather than hidden: message payloads leave the servers upon delivery, logs are kept at most ninety days, self-deleting messages are native, and custom retention policies exist — but only for the Private Cloud tier. No automated decision-making, no profiling, no sale of analytics, and product analytics run on a self-hosted, consent-based European tool with no data shared with the vendor. We found no public information on an admin export in a documented format, an audit trail of administrative actions, or an organisation-wide switch for read receipts, the availability status or analytics. 4 12 6
The Compliance Counsel
Custom retention policies are documented for the private cloud deployment only, messages are stated to be deleted from servers immediately upon delivery, and logs are kept at most ninety days. We found no public information on an administrative export of workspace data in a documented format, legal hold, eDiscovery, or an audit trail of administrative actions; read receipts and availability status appear as features with no organisation-wide switch-off documented. The stated absence of profiling and automated decision-making is welcome, but it does not substitute for a discovery story. 2 4 6 12
The Platform Engineer
Retention is documented mostly as server-side hygiene — messages deleted from servers on delivery, logs held at most 90 days — with custom retention policies scoped only to the Private Cloud edition, and I found no public information on an admin export format, legal hold, eDiscovery or an administrative audit trail. The works-council-friendly parts are real though: the privacy policy states no automated decision-making, and product analytics runs on a self-hosted, consent-based EU tool with no data shared to the vendor. 4 6 10 12
The Skeptic
Retention is configurable, but the sentence that says so scopes custom retention policies to the Private Cloud deployment, and the privacy policy describes encrypted messages deleted from Wire's servers as soon as they are delivered — a deletion posture, not a discovery one. We found no public information on admin export of workspace data, an audit log, legal hold, or eDiscovery export. Read receipts and availability status exist as features and the vendor's own analytics run on consent, but nothing documents switching presence or read receipts off organisation-wide. 12 4 6
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
Wire Cloud, a dedicated private cloud on Azure, AWS, StackIT or another provider, and an on-premises edition that runs air-gapped with all data and keys under customer control are all offered, on a codebase the vendor calls 100% open source on GitHub, with MLS stated to protect every feature in both cloud and on-premises versions. Federation across back-ends and on-premises sit on the top Enterprise tier; I found no documented export or migration path out, and cross-platform backups are "coming soon", so what an exit actually looks like is not spelled out. 3 7 8 12 2
The Security Officer
Custody is genuinely on offer: the code is stated fully open source, on-premises deployment including air-gapped operation is documented down to Kubernetes and Cassandra requirements with all data and keys under customer control, private cloud runs on named providers, and secure federation spans organisational back-ends. On-premises and private cloud sit on the top tier behind a sales contact, and we found no public information on a documented export format for moving an archive in or out, which is the page an exit story needs. 3 7 8 9 12 2
The Works Council Advocate
On-premises and private cloud deployments are documented with air-gapped operation, Kubernetes and Cassandra requirements and the statement that all data and keys stay fully under customer control, with every feature said to be MLS-protected in both cloud and on-premises versions. The source is claimed fully open and verifiable on GitHub, and federation across organisational back-ends exists as an Enterprise feature. We found no public information on a documented export or migration path in and out, and the self-hosted route appears only on the top tier behind a sales contact. 12 8 3 2
The Compliance Counsel
On-premises and private cloud deployment are documented with air-gapped operation, named infrastructure requirements and all data and keys stated to remain under customer control, alongside a fully open-source codebase from protocol to application on GitHub and documented federation across back-ends. We found no public information on a documented export or migration path out, which is what an exit ultimately turns on; the deployment pages also show on-premises appearing on the Enterprise tier only, with interested customers directed to sales. 2 6 9 12 2
The Platform Engineer
This is the deployment story I look for: source code stated as 100% open and on GitHub, an on-premises edition with named infrastructure requirements (Kubernetes, Cassandra, DMZ for calling, air-gapped support), private cloud deployable on Azure, AWS or StackIT, and federation with granular controls across back-ends. The honesty is in the small print — on-prem and private cloud sit on the Enterprise tier, setup runs 12-20 weeks, and installation, operation and maintenance are the customer's responsibility — and I found no public information on a documented export or migration path out. 1 3 7 8 12 2
The Skeptic
On-premises deployment is documented in operational detail — Kubernetes and Cassandra requirements, air-gapped operation, and the statement that all data and keys stay fully under customer control — with private cloud on Azure, AWS or StackIT and MLS protection stated across cloud and on-premises versions. The source is claimed 100% open source on GitHub, and federation is listed, though on the top Enterprise tier and described as federation with Wire Cloud. What we did not find is the exit: no documented full export of messages, files and metadata, and both cross-platform backups and end-to-end-encrypted history sharing are marked "Coming soon". 12 3 8 2 7
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
An open Integrations SDK in JavaScript, TypeScript, Java and Kotlin lets apps act as full members of encrypted conversations — interactive approvals with buttons, event-driven reactions into GitHub, Jira and CI/CD pipelines — and Wire ships and maintains first-party apps (Poll, Reminder, GitHub) itself, which is more than listing other people's. SSO and SCIM are standard on the paid tier; I found no public information on an app directory, documented rate limits, a developer sandbox, or a versioned API with a deprecation policy. 2 13 14
The Security Officer
This is a real app framework, not a badge wall: an open-source SDK in JavaScript, TypeScript, Java and Kotlin with documentation, examples and sample apps, an event-driven model with full API references, interactive approval buttons, integrations the vendor itself maintains (polls, reminders, GitHub), and apps that act as members of end-to-end encrypted conversations where the server sees only ciphertext. SSO and SCIM provisioning are documented; we found no public information on rate limits, a developer sandbox, or an API versioning and deprecation policy. 2 7 9 13 14
The Works Council Advocate
A genuine app framework: an Integrations SDK with documentation, sample apps and full API references, where event-driven apps act as members of end-to-end encrypted conversations and the server only ever sees encrypted data — automation without a listening operator. Interactive approval buttons, CI/CD and monitoring alerts into channels, vendor-maintained first-party apps for polls, reminders and GitHub, plus single sign-on and SCIM provisioning are documented. We found no public information on documented rate limits, a sandbox, or a versioning and deprecation policy for the API. 14 13 2 7
The Compliance Counsel
An integrations SDK is documented in JavaScript, TypeScript, Java and Kotlin with full API references, sample apps and an event-driven model, and apps act as members of encrypted conversations so the server sees only encrypted data, with interactive approval buttons and actions into GitHub, Jira and pipelines, plus vendor-maintained first-party apps for polls, reminders and GitHub. Single sign-on and SCIM provisioning are listed in the administrative controls. We found no public information on documented rate limits, a sandbox, or API versioning with a deprecation policy. 2 7 13 14
The Platform Engineer
An open-source SDK across JavaScript, TypeScript, Java and Kotlin where apps act as members of end-to-end encrypted conversations and the server only ever sees encrypted data — a permission boundary with real teeth — plus event-driven triggers into GitHub, Jira and CI pipelines, interactive approval buttons, SSO and SCIM provisioning, and vendor-maintained first-party apps (Poll, Reminder, GitHub) rather than a bare directory listing. I found no public information on API versioning, a deprecation policy, documented rate limits or a sandbox, which is what separates a platform from a framework. 2 7 13 14
The Skeptic
The Integrations SDK is publicly available to any developer, in JavaScript, TypeScript and on the JVM, with full API references, documentation, sample apps and an event-driven model — and apps sit inside end-to-end encrypted conversations with the server seeing only encrypted data. Wire maintains its own first-party apps (polls, reminders, GitHub with webhooks) and customers can build against internal systems such as Jira and pipelines; SSO and SCIM provisioning are on the paid tier. We found no public information on rate limits, API versioning, a deprecation policy, or a sandbox. 13 14 2
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
Servers are stated to sit in Germany and Ireland, a subprocessor list with locations is published (one US payment processor named), and the contracting entity in Zug plus an Article 27 EU representative in Berlin are documented. Self-hosting with customer-held keys removes the question entirely for those on the top tier; the captured pages give different figures for the company's seat (Zug in the imprint, Berlin in the GitHub profile), and I found no public information on a published data processing agreement. 4 5 8 9 12
The Security Officer
Servers in Germany and Ireland are stated, the imprint names a Swiss entity with a designated EU representative in Berlin, and a subprocessor list is published with locations — European throughout except payment processing via Stripe in the USA, named as such. Certifications are published, and the on-premises option can remove the question entirely; we found no public information on a published data processing agreement, and the EU-residency claim sits in marketing pages while the captured pages give different signals about the hosting providers behind it. 3 4 5 8 9 12
The Works Council Advocate
Servers are stated to sit in Germany and Ireland, an EU representative in Berlin is named, and a subprocessor list is published with locations — Stripe in the USA for payments is the one non-EU entry, and EU-US Data Privacy Framework certification is named for HubSpot and Google. On-premises operation with customer-held keys, and BSI approval as an instrument for German digital sovereignty, largely removes the question where that tier is available. The residency claim rests on marketing pages rather than a published data processing agreement, and the hosting providers are named only through the subprocessor list. 4 8 12 7
The Compliance Counsel
The contracting entity is Wire Swiss GmbH in Zug with Wire Germany GmbH registered as the GDPR representative and operating affiliate, servers are stated to sit in Germany and Ireland, and a subprocessor list with locations is published, naming one US processor for payments with transfer safeguards described through adequacy, standard contractual clauses and the Data Privacy Framework. German government use and BSI approval as an instrument for German digital sovereignty are documented. The residency claim rests on marketing copy and the captured pages give different signals about the hosting provider, while on-premises deployment, which would remove the question, sits behind the Enterprise tier and a sales contact. 3 4 5 7 8 9
The Platform Engineer
Servers in Germany and Ireland, a published subprocessor list with locations where the only United States entry is Stripe for payment services, transfer safeguards through adequacy and standard contractual clauses, ISO 27001/27701 plus BSI approval, and an on-premises option that removes the custody question entirely. The contracting entity is Wire Swiss GmbH in Zug with a designated German EU representative in Berlin; the captured pages give different statements on where the company is headquartered, and the hosting providers behind the marketing claims are not individually named there. 3 4 5 7 8 12
The Skeptic
The contracting entity is Wire Swiss GmbH in Zug, with Wire Germany GmbH designated as the Article 27 EU representative, and servers are stated to sit in Germany and Ireland. A subprocessor list is published with locations — ten processors, nine located in the EU or Germany and Stripe in the USA — with adequacy, standard contractual clauses and Data Privacy Framework certification named as safeguards. What holds this below the top band: the EU-only hosting claim appears in marketing copy while the listed hosting certifications include FedRAMP and FIPS 140-2, and we found no public information on a published data processing agreement for customers. 5 4 8 9
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
The Free tier for up to 5 people and the SMB tier at "€7.45*) per person/month, annual payment or €8.94 per person/month, monthly payment" for teams up to 100 people are public, with the main features listed per tier and the deployment pages spelling out which cost components each deployment adds. Enterprise and on-premises licensing are "Custom", so a 150-person buyer or an on-premises buyer cannot compute the invoice from public pages, and I found no stated VAT treatment, minimum term or storage and history limits. 2 12 2
The Security Officer
The free and small-team tiers are priced publicly — €7.45 per person/month, annual payment or €8.94 per person/month, monthly payment — with the billing period and the feature boundaries of each tier listed, so an organisation of up to 100 people can compute its invoice. Enterprise, Partners, private cloud and on-premises are all custom-priced sales conversations, and we found no public information on VAT treatment or storage and history limits per plan. 2 12 2
The Works Council Advocate
The Free tier and the SMB tier at €7.45 per person per month on annual payment, or €8.94 on monthly payment, for up to one hundred people, are public with each tier's features listed. Enterprise, Partners, private cloud and on-premises are all custom-priced, with only the cost components and setup times described, so an annual invoice for a large headcount cannot be computed from public pages. The custom retention policies a works agreement would ask for sit in that unpriced tier, and VAT treatment is not stated. 2 2 12
The Compliance Counsel
Per-user prices are public for the small-team tier with both billing periods stated, features are listed per tier, and the deployment page names the first-year cost components for cloud, private cloud and on-premises. The Enterprise tier, which is where the retention, federation and deployment options sit, is custom-priced, and we found no public information on minimum term, VAT treatment or a priced self-hosted licence. A buyer who needs the compliance features cannot compute the invoice from these pages. 2 12 2
The Platform Engineer
Free (up to 5 people) and SMB at €7.45 per person/month with annual payment or €8.94 per person/month with monthly payment (up to 100 people) are public, with features and support tiers listed per plan, and the deployment page at least names the cost components — subscription only for cloud, subscription plus licence, setup and implementation for on-premises. Enterprise, self-hosted licensing and every on-prem figure are "Custom", and I found no public information on storage or history limits per tier or VAT treatment, so the annual invoice is computable only for the small-team cloud case. 2 12 2
The Skeptic
Per-user prices are public with the billing period stated — €7.45 per person/month, annual payment or €8.94 per person/month, monthly payment, for teams up to 100 people — with a free tier capped at five people and features listed per tier. The tier boundaries are legible: end-to-end encryption sits on every plan while SSO and SCIM arrive on the paid SMB tier, but federation, data sovereignty and every self-hosted option sit on the Enterprise tier marked "Custom". We found no public information on VAT treatment, minimum term, storage limits or guest pricing, and the first-year cost for private cloud and on-premises names licence, setup and implementation fees without public amounts. 2 2 12
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?The imprint names a single company with no parent statement, but the GitHub organization README instead says the company is headquartered in Berlin, conflicting with the Swiss seat. |
2/2 pts | 5 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?The claim appears only in marketing copy on the security and MLS pages, not in a DPA or subprocessor list, and the unnamed hosting providers hold US federal certifications (FedRAMP, FIPS 140-2) suggesting an American provider. |
4/4 pts | 3 Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?On-premises and private cloud deployment appear only on the top Enterprise tier and the FAQ says interested customers must contact sales. |
1/1 pts | 2 Report an error |
| Open source |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Wire (Messaging)
Is Wire (Messaging) European?
Yes. whats-best.ai classifies Wire (Messaging) as EU-Made. Its vendor, Wire Swiss GmbH, is incorporated in Switzerland, per the vendor’s page captured 16 Nov 2026.
Where does Wire (Messaging) store data?
Wire (Messaging) stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany and Ireland as hosting locations, per the vendor’s page captured 16 Nov 2026.
Does Wire (Messaging) have a free plan?
Yes. Wire (Messaging) has a free plan, per the vendor’s page captured 19 Oct 2026.
What are the best alternatives to Wire (Messaging)?
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: Wire (Messaging) alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 19 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Open source. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The imprint names a single company with no parent statement, but the GitHub organization README instead says the company is headquartered in Berlin, conflicting with the Swiss seat.
- Weak sourcing — Hosting location. The claim appears only in marketing copy on the security and MLS pages, not in a DPA or subprocessor list, and the unnamed hosting providers hold US federal certifications (FedRAMP, FIPS 140-2) suggesting an American provider.
- Weak sourcing — Hosting options. On-premises and private cloud deployment appear only on the top Enterprise tier and the FAQ says interested customers must contact sales.
- 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.
- 32 product 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
- 8 pricing 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
- 7 integrations 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
- 7 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
- 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 hosting 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 support 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 data 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 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 (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage wire.com Checked 19 Oct 2026 Details →
- 2 Pricing wire.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 3 Security page wire.com Checked 16 Nov 2026 Details →
- 4 Privacy policy wire.com Checked 16 Nov 2026 Details →
- 5 Imprint wire.com Checked 16 Nov 2026 Details →
- 6 Channels, threads & search — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 7 Channels, threads & search — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 8 Encryption & access control — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 9 Encryption & access control — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 10 Retention, discovery & co-determination — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 11 Retention, discovery & co-determination — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 12 Deployment & data custody — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 13 Integrations & extensibility — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 14 Integrations & extensibility — found from sitemap wire.com Checked 16 Nov 2026 Details →
- 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →