Who Twake Mail is for#
Self-hosted workplace email evaluation
Use Twake Mail when evaluating open source email infrastructure for a workplace suite with privacy and collaboration requirements.
JMAP client and server deployments
Use it when you want a JMAP-oriented mail stack with an official Flutter client and server-side Twake Mail features.
The problem it solves#
Teams that want private workplace email need more than a webmail skin. They need a server they can operate, a modern client path, and collaboration features such as shared mailboxes and labels without handing every mailbox to a proprietary provider.
How it solves it#
Apache James-based backend
The backend adapts Apache James for Twake Mail and adds server features needed for collaborative workplace email.
JMAP client companion
The official tmail-flutter repository provides the mobile and web client layer that connects to a JMAP server.
Collaborative mail features
The backend README lists encrypted mailboxes, team mailboxes, filtering, forwarding, labels, contacts autocomplete, and push subscriptions.
Strengths and trade-offs#
Strengths
- Product-owned repositoriesThe Twake Workplace README links tmail-backend and tmail-flutter as the official Twake Mail server and client repositories under LINAGORA.
- Clear AGPL evidenceGitHub reports AGPL-3.0 for both the backend and Flutter client, and both repositories expose root LICENSE files.
Trade-offs
- -Multi-repo product scopeThe current OSA item model stores one primary GitHub repo, so the listing uses backend telemetry and marks coverage ambiguous instead of implying full client and server coverage.
- -Operational email complexityTeams still need to operate mail infrastructure and understand JMAP, Apache James, and deployment-specific dependencies.
Twake Mail vs alternatives#
Primary repo: https://github.com/linagora/tmail-backend Companion client repo: https://github.com/linagora/tmail-flutter Coverage note: backend-primary telemetry is ambiguous for the full client/server product.
Install and self-host#
Clone the backend repo, then follow the server deployment docs for your target environment.
git clone https://github.com/linagora/tmail-backend.git
cd tmail-backend
git submodule update --initWhat it's built on#
- Languages
- JavaScala
FAQ#
Why is repository coverage marked ambiguous?
Twake Mail is split across tmail-backend for the server and tmail-flutter for the client, while OSA can store only one primary GitHub repo for telemetry.
Which repo is the primary GitHub repo?
The listing uses tmail-backend as the primary repo because it contains the Twake Mail server work and Apache James extensions.
Does Twake Mail have an official client repo?
Yes. LINAGORA maintains tmail-flutter as the official Flutter client for Twake Mail mobile and web users.
Similar open-source tools#
Galae Email
Self-hosted email server stack forked from Mailcow
Outline
Team wiki and knowledge base with realtime collaboration
Inbox Zero
AI email assistant that drafts replies and clears your inbox
Nextcloud
Hiroba
Open-source virtual office for remote teams. See who's around, walk ov
Twake Chat
Matrix team chat with a companion identity server