Wire
:wavy_dash: Overview of the open source code for Wire observed · 2026-08-28
Health v2 · maintenance only
59/100
- Activity 60
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3821
- days_rel: n/a
- days_push: 240
- n_releases_24m: 0
Adoption not part of the score
2544 stars · 179 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Wire is an open-source, end-to-end encrypted messaging and collaboration platform whose server components are written primarily in Haskell. The wire-server repository contains the backend services (accounts, conversations, push notifications, asset storage, SSO) needed to self-host the full Wire messenger for web, desktop, and mobile clients.
Use cases
- self-host a secure end-to-end encrypted messenger for my organization
- run a private team chat server with SSO and SCIM user management
- deploy an encrypted messaging backend on Kubernetes with Helm charts
- host a messaging platform for government or regulated industries with data sovereignty
- set up push notification and WebSocket services for a chat app
- provide secure file sharing and conferencing backend for enterprise teams
When to choose
- you need full control over your messaging infrastructure with on-premises or self-hosted deployment
- compliance requirements (HIPAA, government, critical infrastructure) demand data sovereignty and auditable open-source code
- you need enterprise features like SAML SSO, SCIM provisioning, and MLS end-to-end encryption at scale
- you want a European-built messaging platform with a mature multi-service architecture
When to avoid
- you just want a simple chat app for a small team without server operations expertise
- you lack experience running Haskell services and Kubernetes clusters
- you need lightweight single-binary deployment rather than a multi-service microservice stack
- you primarily need consumer-style federation with other messengers, which is still on the roadmap
Facets
service · maturity active
http-server websocket auth authorization caching proxy security self-hosted api-gateway middleware messaging-platforms security privacy self-hosted backend apis developer-tools self-hosted cloud secure-messenger end-to-end-encryption messaging-server haskell mls sso push-notifications federation helm-charts enterprise-messaging linux docker kubernetes web-server
5 sources
- readme: https://github.com/wireapp/wire · fetched 2026-08-28 · 387731945492
- homepage: https://wire.com · fetched 2026-08-29 · bdb83e40f2b3
- site_page: https://wire.com/en/features · fetched 2026-08-29 · e684879cc31e
- site_page: https://wire.com/en/about-us · fetched 2026-08-29 · 8134cb9d107b
- site_page: https://wire.com/en/pricing · fetched 2026-08-29 · d138632b3059
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| wireapp/wire | main | 59 |
| wireapp/wire-server | backend | 97 |
| wireapp/wire-webapp | frontend | 100 |
| wireapp/wire-desktop | frontend | 99 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem