Twake Mail

Linagora created Twake Mail as a cross-platform mobile client built around the modern JMAP standard. The project grew out of the company's broader digital sovereignty initiative to deliver an independent workplace suite that bypasses proprietary cloud ecosystems. Today it provides organizations with an open, protocol-driven email client that avoids the high latency and vendor surveillance common to legacy mobile setups.

Why Twake Mail instead of Gmail

Gmail bundles email hosting, ad tracking, and client interfaces into a commercial stack that centralizes company data on Google servers. Twake Mail separates the interface from data custody, communicating through open JMAP standards rather than proprietary sync APIs. While Gmail indexes inbox contents to power commercial services, Twake Mail routes communications exclusively through your chosen server, preventing metadata leakage and third-party profiling. Default platform options like Apple Mail similarly keep users tied to proprietary ecosystems and traditional, chatty IMAP synchronization.

The tradeoff centers on operational control versus managed convenience. Gmail removes server maintenance and mobile push plumbing at the expense of privacy and platform dependence. Twake Mail requires your team to run or lease a JMAP-compatible mail server, such as Apache James or Stalwart, which introduces administrative overhead. For agencies and operations leads handling confidential client work, that hosting responsibility delivers complete jurisdiction over storage, audit trails, and communication policies across the entire team fleet.

What it does well

• JMAP protocol support (RFC 8620 and RFC 8621) batches multiple data operations into single HTTP requests, reducing mobile battery drain and network overhead.
• Cross-platform Flutter implementation provides uniform navigation, message threading, and mailbox layout across Android and iOS fleets.
• Privacy-first data routing guarantees that message content, drafts, and contacts remain isolated from advertising trackers and external analytics.
• Direct pairing with self-hosted mail backends like Apache James gives operations teams uncompromised custody of encryption keys and mail storage.
• Multi-device containerized webmail images allow system administrators to run matching browser-accessible webmail for desktop users via standard Docker workflows.