Comparez ginlo Business et Wire sur les capacités, la juridiction, les garanties et l'adéquation pour les acheteurs européens.
Tous deux listés comme alternatives à: Microsoft Teams, Slack, WhatsApp
Germany· Groupware
Needs review
Shortlist when you need a German-entity, Germany-hosted encrypted business messenger with Management Cockpit (AD/LDAP, policies, remote wipe) and free external reach via ginlo Private. Skip when you require open source, self-hosting, or published independent crypto audits—consider Wire or Nextcloud Talk instead.
Switzerland· Groupware
Needs review
Shortlist Wire when you need always-on E2EE collaboration (MLS), Swiss legal entity, open-source clients/server, and a credible path from EU cloud to on-prem/federation. Skip when you need deep Microsoft 365/Slack app ecosystems or a pure non-AWS/US-SaaS subprocessor footprint—consider Nextcloud Talk or a Germany-hosted managed messenger such as ginlo Business instead.
Les lignes surlignées diffèrent entre les deux produits.
| Caractéristique | ginlo Business | Wire |
|---|---|---|
| Pays d'origine | Germany | Switzerland |
| Catégorie | Groupware | Groupware |
| Open source | Non | Oui |
| Auto-hébergé | Non | Oui |
| Siège | Germany | Switzerland |
| Entité légale | ginlo.net Gesellschaft für Datenkommunikationsdienste mbH (ginlo.net GmbH), Rupert-Mayer-Str. 44, 81379 Munich | Wire Swiss GmbH (CHE 432.881.146), Untermüli 9, CH-6300 Zug; EU rep Wire Germany GmbH, Berlin |
| Droit applicable | Non indiqué | Swiss law (business ToU for non-US use); jurisdiction Zurich |
| Maison mère / contrôle US | Aucune maison mère US connue | Aucune maison mère US connue |
| Exposition CLOUD Act (indicative) | Moyen | Moyen |
| Hébergement / résidence | Vendor GTC require server and storage in a German computer centre certified to ISO 27001 based on BSI IT-Grundschutz; privacy notice states processors such as German data-centre operators, internet/line providers, and payment providers, and asserts no third-country processing by ginlo. Host operator names are not published. Mobile push uses platform channels (e.g. Apple Push Notification, Google Cloud Messaging) per GTC. | Cloud: servers in Germany and Ireland per security pages; DPA lists Amazon Web Services EMEA SARL for hosting (EU). Other subprocessors include Google Cloud EMEA (email), Zendesk, HubSpot, Salesforce (Germany processing location stated), Stripe (USA/SCCs), Box, ContractHero, Countly (Germany), Wire Germany GmbH. On-prem customers host in their own environment. |
| Résumé | German-hosted secure business messenger from Munich-based ginlo.net GmbH: E2EE chat, files, and A/V calls with Management Cockpit admin for AD/LDAP, policies, and external ginlo Private contacts. | Swiss open-source secure messenger from Wire Swiss GmbH: always-on E2EE messaging, calls, and files (MLS), cloud or on-premises, for regulated teams and public sector. |
| Tags |
| En un coup d'œil | ginlo Business | Wire |
|---|---|---|
| HQ | Munich, Germany | Zug, Switzerland (Wire Swiss GmbH) |
| Legal entity | ginlo.net GmbH (HRB 254209) | Non indiqué |
| Deployment | Managed SaaS (not self-hosted) | EU cloud and/or on-prem / private cloud |
| Hosting (vendor claim) | Germany computer centre; no ginlo-initiated third-country transfer | Non indiqué |
| Admin | Optional Management Cockpit (AD/LDAP/CSV, policies, MDM hooks) | Non indiqué |
| Commercial model | Seat licences; optional trial (see vendor for current terms) | Non indiqué |
| EU representative | Non indiqué | Wire Germany GmbH, Berlin |
| Product | Non indiqué | E2EE messenger + calls + files; optional Drive |
| Open source | Non indiqué | Yes (clients GPL-3; server AGPL-3) |
| Hosting (cloud) | Non indiqué | DE/IE regions; AWS EMEA (per DPA) |
| Key capabilities | ginlo Business | Wire |
|---|---|---|
| EU-operated (Germany) | Oui | Non indiqué |
| End-to-end encryption (claimed) | Oui | Non indiqué |
| Germany hosting (claimed) | Oui | Non indiqué |
| AD/LDAP admin cockpit | Oui | Non indiqué |
| Managed SaaS | Oui | Non indiqué |
| Not open source | Oui | Non indiqué |
| E2EE + MLS | Non indiqué | Oui |
| Open source | Non indiqué | Oui |
| On-prem / self-host | Non indiqué | Oui |
| Swiss HQ | Non indiqué | Oui |
| EU cloud regions | Non indiqué | Oui |
| ISO 27001/27701 (claimed) | Non indiqué | Oui |
Full encryption design for chat and files
Vendor GTC describe a full-encryption architecture: no unencrypted messages stored on ginlo servers, decryption keys only on authorised messenger clients, and encryption in transit plus on devices and intermediate server storage. Practical for regulated orgs replacing email for sensitive threads—confirm cipher suite details in procurement docs.
Management Cockpit with AD/LDAP and MDM hooks
Central admin for licences, CSV/AD/LDAP user import, department keywords, password and attachment policies, corporate design, groups, and info channels. Leaver accounts can be blocked and communications deleted quickly when devices are lost—built for IT ops without requiring a messaging platform engineer.
Business to ginlo Private external bridge
Employees on paid Business seats can message external contacts on free ginlo Private without charging those outsiders. Suits practices, schools, and authorities that need secure outbound reach beyond the licensed tenant.
Multi-device sync, channels, and A/V conferences
Use up to ten devices per account with server-side sync while messages remain available; announcement/content channels for org-wide updates; audio/video conferences with screen sharing; self-deleting and scheduled messages plus QR identity checks and ginlo ID without exposing a phone number.
Germany-hosted managed service
Contracting party is ginlo.net GmbH in Munich; GTC require the server and storage in a German computer centre certified to ISO 27001 based on BSI IT-Grundschutz, with no ginlo-initiated third-country transfer. Managed SaaS only—no public self-host option.
Always-on MLS / E2EE for chat, calls, and files
Messaging, conference calls, and in-app file shares are end-to-end encrypted by default—no toggle. Wire markets full-product MLS (IETF Messaging Layer Security) for scalable group key exchange, alongside Proteus/Double Ratchet heritage for pairwise messaging and SRTP/DTLS for calls. Suits orgs that reject optional encryption modes.
Guest rooms and external collaboration
Invite outsiders into E2EE conversations via guest rooms in the browser without requiring a full account download, plus external team members with lifecycle controls (removal drops their history access). Practical for contractors, clients, and inter-org projects that must stay off consumer WhatsApp.
Cloud, on-premises, air-gap, and federation
Run managed Wire Cloud or deploy on-premises/private cloud—including air-gapped networks—with optional federation between isolated Wire backends and admin control over which backends may interconnect. Aimed at governments and CNI that cannot accept pure SaaS only.
Enterprise identity: SSO, SCIM, and admin policy
Enterprise tier adds SAML-based single sign-on, SCIM provisioning, and granular admin controls (for example enforce app lock, restrict self-deleting messages). Built for complex directories rather than only self-serve SMB signup.
Open-source clients, server, and crypto
Wire publishes client, server (wire-server, AGPL-3.0), and core-crypto components on GitHub for independent review. Multi-device accounts (up to 8 devices) with ID Shield certificate-based device verification reduce manual fingerprint workflows while keeping device trust visible.
| Assurance & compliance | ginlo Business | Wire |
|---|---|---|
| Independent security / no-logs audit | Not found Marketing mentions regular security audits; no public independent audit report located on vendor site. | Partial Vendor publishes Security/Privacy whitepapers and states external pen tests and ISO audits in TOMs; public third-party audit PDFs (e.g. historic Kudelski/X41 claims in secondary sources) were not re-verified as current primary evidence during this draft. |
| ISO 27001 | Vendor claimed Claimed for the hosting computer centre based on IT-Grundschutz (BSI); no public certificate number/PDF found. | Vendor claimed Asserted on Wire security marketing page; request certificate in procurement. |
| SOC 2 / SOC 3 | Not found | Not found No public SOC 2/3 claim located on security/legal pages during research. |
| GDPR / EU data protection | Vendor claimed EU/German entity; public privacy notice under GDPR; supervisory authority BayLDA referenced. | Vendor claimed Swiss FADP controller; GDPR for EU/EEA individuals; EU Art. 27 representative Wire Germany GmbH; public privacy policy and DPA. |
| US CLOUD Act exposure (indicative) | Partial German entity, no known US parent, Germany hosting claimed; residual exposure via APNs/FCM push paths and unnamed processors. Not legal advice. | Partial Swiss entity / no known US parent, but AWS EMEA hosting and US-parent SaaS subprocessors (Stripe, HubSpot, Salesforce, Zendesk corporate groups; APNs/FCM push). Not legal advice. |
| Data processing agreement (B2B) | Not found Privacy policy published; standalone B2B DPA download not found on public site—confirm in procurement. | Vendor claimed Public Art. 28 GDPR Processing Agreement with TOMs and Annex 2 subprocessor list (updated March 12, 2025 on page). |
| EU AI Act | Not applicable Secure messaging product; not AI-centric. | Not applicable Secure messaging/collaboration product; not marketed as an AI system core offering. |
| BSI IT-Grundschutz (hosting) | Vendor claimed ISO 27001 based on IT-Grundschutz claimed for data centre in marketing and GTC. | Non indiqué |
| ISO 27701 | Non indiqué | Vendor claimed Asserted alongside ISO 27001 on security page; not independently verified here. |
| Cyber Essentials (UK) | Non indiqué | Vendor claimed Asserted on security page as UK government-backed baseline certification. |
| Considerations & known limitations | ginlo Business | Wire |
|---|---|---|
| Limited public audit and cert artefacts | Medium ISO 27001/IT-Grundschutz and regular audits are vendor-asserted; no public audit PDF or cert registry entry found. Procurement should request evidence under NDA. | Non indiqué |
| Closed managed SaaS only | Medium No self-host or open-source server path. Exit and independent verification depend on vendor cooperation and export tooling. | Non indiqué |
| Mobile push via Apple/Google | Low GTC reference Apple Push Notification and Google Cloud Messaging for new-message signals. Content is claimed E2EE, but delivery metadata still touches US platform infrastructure. | Non indiqué |
| Processors described by category only | Medium Privacy policy lists German data centres, line providers, and payment providers without naming operators. Harder to complete CLOUD Act / transfer diligence from public sources alone. | Non indiqué |
| External parties must use ginlo | Low The Private bridge helps, but contacts still need ginlo Private installed—unlike email or WhatsApp ubiquity. | Non indiqué |
| AWS EMEA + US-parent SaaS subprocessors | Non indiqué | Medium Even with DE/IE regions and a Swiss controller, cloud tenants depend on AWS EMEA and several US-group tools for hosting, CRM, support, or payments. On-prem reduces hosting dependency but not necessarily all vendor-side SaaS. |
| Wire Drive is not client-side E2EE | Non indiqué | Medium DPA distinguishes messenger E2EE from Drive encryption-at-rest with possible operator access. Misclassifying Drive as zero-knowledge chat storage creates compliance risk. |
| ISO / Cyber Essentials need certificate proof | Non indiqué | Low Certifications are prominently claimed on marketing pages but should be validated with current certificates and scope statements before audit reliance. |
| Mobile push via APNs/FCM | Non indiqué | Low Standard mobile delivery path involves Apple/Google push infrastructure for wake-ups; Wire states content is not shared. F-Droid build available to avoid FCM. |
When: You need open-source components, MLS roadmap, or private-cloud/on-prem options
Consider: Wire (Swiss secure collaboration)
Wire is commonly shortlisted for enterprise secure messaging with more deployment flexibility than pure SaaS messengers.
When: You already run a self-hosted collaboration hub and want chat inside that stack
Consider: Nextcloud Talk (Germany)
Pairs with Nextcloud Files/Groupware; different product shape than a standalone dual Business/Private messenger.
When: You need mass consumer reach more than organisational sovereignty
Consider: WhatsApp Business or Microsoft Teams
Higher network effects; weaker EU-sovereignty and admin story for sensitive regulated chat.
When: You want a German managed business messenger with AD/LDAP cockpit and no self-host requirement
Consider: ginlo Business
Stronger Germany-hosting contract language; weaker open-source/on-prem story than Wire
When: Chat is secondary to self-hosted files, calendars, and groupware you already run
Consider: Nextcloud (Talk / groupware)
Broader collaboration suite; different crypto/admin model than Wire MLS messenger
When: You need the Microsoft 365 or Slack ecosystem more than E2EE-by-default
Consider: Microsoft Teams or Slack
Richer workplace integrations; weaker default E2EE and European sovereignty story