Your webmail is slow because the protocol underneath it is from 1986
Most self-hosted mail platforms — and most commercial ones too — still speak IMAP under the hood, a protocol designed for dial-up connections checking mail once an hour. Every action (open a folder, search, mark as read) is a separate round trip, which is why "enterprise webmail" so often feels like it's loading against its will. FanMail is built on JMAP (JSON Mail Access Protocol) end to end, via the open-source Stalwart Mail Server — a protocol designed from the start for a web client, not retrofitted onto one.
What that actually changes for the person reading email
- Batched operations — moving, tagging, and marking a hundred messages is one request, not a hundred.
- Push by design — new mail appears without the client polling the server every few minutes pretending to be "real-time."
- A composer that doesn't fight the protocol — drafts, attachments, and threading are native JMAP objects, not IMAP flags bent into a UI.
Why this matters more once you're self-hosting
A commercial suite can paper over a slow protocol with enough caching servers and CDN tricks. A self-hosted platform running on infrastructure you actually pay for doesn't get that luxury — the protocol choice shows up directly in how the mailbox feels at 10,000 users, not just at a demo with three test accounts.
Proven at real scale, not a lab number
FanMail is running in production at 10,000-mailbox scale as a full IceWarp replacement, with the built-in admin panel handling day-to-day server management without a separate ops tool. That's the actual test JMAP has to pass — not a synthetic benchmark, a university's entire mail traffic.
