Introducing Flectar Mail: Email, made fast again
A native, open-source email client built in Rust. No WebViews, even for rendering email HTML.
Email is one of those applications we keep open all day. It shouldn't take hundreds of megabytes of memory just to check an inbox, and it shouldn't feel like navigating a website wrapped in a desktop window.
We've been working on something different.
Today, we're introducing Flectar Mail, our open-source email client built from the ground up around a simple idea: email should feel fast again.
It's native, lightweight, local-first, and designed to bring email, calendars, contacts, and files together without a browser engine weighing everything down.
And the source code is now public.
Why build another email client?
Flectar Mail didn't actually start as a native desktop application.
Our original approach was web-based. We later explored bringing that experience to the desktop with Tauri, and while we got quite far, we kept running into the same problem: the result never quite felt like the application we wanted to use every day.
We wanted instant startup, responsive navigation, smooth interaction with large mailboxes, and exceptionally low resource consumption.
Eventually, we decided that making another web-based email client wasn't going to get us where we wanted to go.
So we changed direction.
Instead of trying to optimize away the overhead of a browser-based architecture, we decided to remove that architecture altogether.
Native Rust, all the way down
Flectar Mail is written in Rust, with its interface built using Slint and our own cross-platform component system.
But the unusual part isn't the interface.
Flectar Mail doesn't use WebViews at all. Not even to display HTML emails.
Email bodies are rendered using Blitz, a Rust HTML/CSS renderer from the Dioxus ecosystem. This allows us to keep the application native without embedding Chromium, WebKit, or another browser runtime just to show a message.
The result is an email client designed to remain responsive while keeping resource consumption exceptionally low.
This approach also gives us more control over how untrusted email content is handled. Email scripts aren't executed, remote images are blocked by default, and we don't expose a full browser environment to incoming messages.
It's a different architecture, and one we're excited to keep developing.
More than an inbox
We don't think a modern email client should stop at sending and receiving messages.
Flectar Mail already brings together multiple email accounts, unified inboxes, conversation threads, calendars, contacts, and file storage.
It supports IMAP, SMTP, and JMAP for email, CalDAV and CardDAV for calendars and contacts, and JMAP/WebDAV-backed file storage.
You can switch between full and minimal workspace layouts, customize colors and themes, organize accounts into profiles, and distinguish messages from different accounts using color indicators.
Account-specific HTML signatures are supported, along with desktop OpenPGP/MIME signing and encryption through GnuPG.
And because Flectar Mail is local-first, synchronized mail and calendar data remain accessible when you're offline.
Our goal isn't to build the smallest possible application by removing everything useful. It's to build an application that stays lightweight while giving you the tools you actually need.
Built for desktop and mobile
We're developing Flectar Mail for Linux, Windows, macOS, Android, and iOS using a shared native UI stack.
Preview builds are already available for the major desktop platforms, along with experimental Android builds. iOS is also part of our development roadmap.
We want the experience to feel familiar across devices without maintaining completely different applications for every platform.
Why we're going open source
Email is complicated. Much more complicated than it looks.
Between IMAP, JMAP, MIME, synchronization, authentication, and decades of unusual HTML markup, there are countless edge cases that only become apparent when real people start using an application with their own accounts.
That's one of the reasons we've decided to develop Flectar Mail in public.
The project is available under the AGPLv3, and we want people to be able to inspect it, improve it, contribute translations, report problems, and help decide where it goes next.
We're also working with technologies that have room to grow themselves. In particular, we maintain several compatibility improvements on top of Blitz and hope to contribute as much of that work upstream as possible.
If we can help improve Rust-native HTML rendering while building a better email client, that's a win for more than just Flectar.
Available now, still evolving
Flectar Mail is currently in alpha.
It's already usable, but there's plenty of work ahead. HTML email rendering remains the most experimental part of the project, and particularly complex messages may not display perfectly yet.
We're actively improving compatibility, refining the interface, and incorporating feedback from the first people using the application.
There's also one important limitation for Gmail and Microsoft users: our official OAuth applications are still going through verification. In the meantime, you can use your own Google Cloud or Microsoft Entra OAuth registration, or connect supported accounts through standard email protocols.
We'd rather be transparent about what's ready and what isn't than pretend the project is already finished.
Come build it with us
The project has only been public for a short time, but we're already seeing people test it, contribute improvements, offer translations, and share ideas for what an email client could become.
That's exactly what we hoped would happen.
Whether you're looking for a lightweight alternative to your current email client, interested in native Rust applications, or simply curious about a project trying something different, we'd love to have you involved.
Download a preview, explore the source code, report a bug, or help translate Flectar Mail into your language.
Email, made fast again.
And we're just getting started.