Self-hosted webmail, honestly reviewed. No marketing fluff — just what you actually get when you run this on your own server.

TL;DR

What it is: A lightweight, PHP-based webmail client — the actively maintained fork of RainLoop, which its original developers abandoned [1][2].
Who it’s for: Sysadmins, privacy-conscious users, and homelab owners who want a clean browser-based interface for an existing email account. Non-technical founders who want to own their email workflow without paying for Fastmail or ProtonMail premium [1][4].
What it is NOT: A mail server. You still need IMAP/SMTP hosting somewhere — SnappyMail is only the front-end client you point at that server [1].
Cost: Zero for the software (AGPL-3.0). A $5/mo VPS can run it alongside your actual mail stack [1][4].
Key strength: Minimal footprint. ~138 KB initial download with Brotli, up to 99 Lighthouse performance score on mobile, no database required [website scrape][2].
Key weakness: Small community (1,552 GitHub stars), AlternativeTo erroneously marks it as “Discontinued” — which it isn’t given commits as recent as March 2026, but the confusion signals thin mindshare [2][5].

What is SnappyMail

SnappyMail is a web-based IMAP/SMTP email client written in PHP. You deploy it on a server, point it at your existing mail provider or self-hosted mail stack, and you get a fast, clean webmail UI accessible from any browser. It does not run a mail server. That distinction matters, and the TechAddressed tutorial makes it explicit upfront: “SnappyMail is a web-based IMAP/SMTP email client… [it] does not setup a server for you to host your own mail.” [1]

The project is a fork of RainLoop Webmail, a once-popular open-source webmail client that stagnated around 2020. When RainLoop’s developers stopped maintaining it, a developer under the handle the-djmaze forked it and rebuilt most of it from scratch. The fork strips out dated dependencies (jQuery, jQuery UI, Modernizr, CKEditor, OpenPGP.js v2), upgrades the rest (PHP 7.4+, ES2020, OpenPGP.js v5, native HTML5 drag-and-drop), and removes a raft of privacy-unfriendly integrations — Gravatar, Facebook, Google, Twitter, DropBox, Sentry — that RainLoop had accumulated [README].

The Awesome Privacy listing describes it plainly: “Simple, modern, fast web-based mail client. This is an IMAP-only fork of RainLoop that mitigates a severe RainLoop vulnerability and adds several new features.” [2] That vulnerability angle matters for anyone still running old RainLoop instances — SnappyMail was the security upgrade the community built for itself.

As of this review the project sits at 1,552 GitHub stars with 193 forks, actively maintained with commits in 2025 and 2026 [2]. That’s a small project by any measure — compare Roundcube’s 173 AlternativeTo likes or Thunderbird’s 20 million monthly active users [3][5]. But small is not the same as dead.

Why people choose it

Over RainLoop: This is the obvious first comparison, since SnappyMail is RainLoop — fixed. Anyone still on RainLoop is running unpatched vulnerabilities and unmaintained PHP 5-era code. SnappyMail is the migration path, and a straightforward one since it’s a semi-drop-in replacement. Plugins aren’t compatible (the extension API changed), but the data is [4][README].

Over Roundcube: Roundcube is the other major self-hosted webmail option and has a much larger community (173 likes on AlternativeTo vs. 7 for SnappyMail) [5]. The practical trade-off: Roundcube requires a database (MySQL/PostgreSQL/SQLite), has more plugins, and has more community-tested deployment guides. SnappyMail needs no database and boots faster, which matters on constrained hardware like a Raspberry Pi or a shared VPS [4][README]. If you’re already running a database for something else, Roundcube’s database requirement costs you nothing. If you want the minimum viable stack, SnappyMail wins.

On privacy: The Awesome Privacy listing recommends SnappyMail in its “Also Consider” tier for email clients, specifically citing its open-source status and privacy posture [2]. The README’s changelog is unusually explicit about what was removed: Gravatar (leaks email hashes to a third party), Sentry (error tracking that phones home), social login providers, background video support, and the X-Mailer header that fingerprints the app [README]. Whether that matters depends on your threat model, but it’s a legitimate differentiator from webmail clients that quietly report usage data.

Performance: The website claims ~138 KB download on mobile with Brotli compression and a 99/100 Lighthouse score [website scrape]. The README’s removal of jQuery, jQuery UI, underscore, polyfills, and multiple animation libraries is what makes this possible — modern browsers support everything natively that those libraries once provided [README]. For users on slow connections or older mobile devices, that matters.

Features

Based on the README and source articles:

Core email functionality:

IMAP and SMTP support (no POP3 — removed in the fork) [README]
Responsive interface that works on mobile without a separate mobile app [README][website scrape]
Dark mode, including an option to strip background/font colors from incoming messages for proper dark mode rendering [README]
Multiple email account support in a single interface [1]
Folder management [4]
Address book with MySQL/MariaDB utf8mb4 support [README]
Service worker for desktop-style push notifications [README]
Keyboard shortcuts [README]

Security and encryption:

AGPL-3.0 license — source must remain open if you distribute [2][4]
PGP support via OpenPGP.js v5 (a significant upgrade from the v2 in RainLoop) [README]
Sodium and OpenSSL encryption support [README]
Auth failure logging to syslog with Fail2ban integration instructions [README]
Password hashing via password_hash/password_verify [README]
Fetch Metadata Request Headers checks [README]
Admin password protection [README]

Sieve and filtering:

Advanced Sieve scripts editor — server-side mail filtering built into the UI [README][2]
Support for a broad range of IMAP RFCs [README][website]

Integrations and extensibility:

Plugin system supporting .phar packages [README]
Nextcloud integration (plugin available) [README]
Kolab groupware support [README]
Docker support with published image (djmaze/snappymail) [1][2]
REST API listed in canonical features [merged profile]

What’s not there:

No calendar, no contacts-sync-to-CalDAV/CardDAV built in (SOGo handles that, SnappyMail doesn’t) [5]
No mobile app — it’s a web client accessed through a browser
No built-in mail server — you bring your own SMTP/IMAP [1]
Most RainLoop plugins are not compatible due to changed plugin APIs [4]

Pricing: software cost vs. infrastructure math

SnappyMail is free software under AGPL-3.0 [2][4]. There is no SaaS tier, no premium version, no paid support channel. The cost question is entirely about the email hosting you point it at.

If you self-host your full email stack (SnappyMail + Postfix/Dovecot or Mailcow/Mailu):

SnappyMail itself: $0
VPS to run everything: $5–15/mo on Hetzner, Contabo, or similar
Domain: ~$12/yr
Total: roughly $6–16/mo depending on VPS size and redundancy

If you use SnappyMail as a client against hosted email (DreamHost, Migadu, Fastmail, etc.):

SnappyMail: $0
Hosted email: $0–$5/mo depending on provider (Migadu starts at $19/yr for unlimited domains)
VPS for SnappyMail: adds $3–5/mo, or run it on the same box as other services

The comparison case is against paid webmail interfaces:

Fastmail: $3/mo per user (their webmail is the product)
ProtonMail: free tier limited, paid from $3.99/mo
Tutanota/Tuta: free tier limited, paid from €3/mo

If you’re paying $4–5/mo for a hosted webmail service primarily for the web interface — not the privacy guarantees or hosted infrastructure — and you already manage a VPS for other reasons, running SnappyMail for $0 on that VPS is straightforward math. If you’re paying for ProtonMail specifically for its encryption model and Swiss jurisdiction, SnappyMail doesn’t replicate that — it’s a different product category.

Deployment reality check

The TechAddressed Docker Compose tutorial [1] is the most detailed third-party deployment resource available. The honest summary: this is a beginner-accessible deployment if you’re already comfortable with Docker.

What you need:

A Linux server (VPS, Raspberry Pi, homelab box — anything running Docker)
Docker and docker-compose installed
Your IMAP/SMTP server credentials from your email host
A domain and reverse proxy (Caddy or nginx) if you want HTTPS and a clean URL
No database — SnappyMail stores its data in flat files [README][4]

No-database is the real convenience win. The flat-file storage means you can back up your SnappyMail config with a single rsync and restore it on a new server in minutes. Roundcube users dumping a MySQL database for the same operation will appreciate the difference [4][README].

What can go sideways:

The tutorial notes [1] that you need to know your email host’s IMAP and SMTP settings — server hostnames, encryption types, and ports. Most providers publish these, but if yours doesn’t, you’re debugging before you even start.
SnappyMail is a semi-drop-in for RainLoop, not a full drop-in. Existing RainLoop plugin configurations will not carry over [4].
AlternativeTo lists the project as “Discontinued” [5], which as of this writing is incorrect — commits landed in March and June 2025 and March 2026 [2] — but that incorrect label may cause hesitation if you’re evaluating tools alongside colleagues who Google it.
The project is maintained primarily by one developer (the-djmaze). That’s bus-factor risk. There are 193 forks and a small community of contributors, but this isn’t a foundation-backed project with paid maintainers [2].

Realistic time estimate: Technical user following the TechAddressed guide: 30–45 minutes to a working instance. Non-technical user with no Docker experience: budget 2–4 hours and expect to read some error messages. If you’ve never touched a server command line, the Docker path is learnable but not instant.

Pros and cons

Pros

No database required. Flat-file config and storage makes setup, backup, and migration simpler than every alternative that requires MySQL or PostgreSQL [4][README].
Tiny footprint. ~138 KB mobile boot with Brotli, Lighthouse scores up to 99 — this is what happens when you rip out jQuery and polyfills [website scrape][README].
Privacy-forward by design. The fork explicitly removed Gravatar, Sentry, social integrations, and the X-Mailer fingerprint header. These are deliberate choices, not marketing [README][2].
Active maintenance. Commits as recent as March 2026, v2.38.2 released, vulnerability patches applied [2][README]. RainLoop is dead; this isn’t.
Proper PGP support. OpenPGP.js v5 is a genuine upgrade over what RainLoop shipped. If you need end-to-end encryption for mail you’re already self-hosting, this is baked in [README].
Sieve scripts editor. Server-side mail filtering with a built-in advanced editor is a feature Roundcube requires plugins for [README].
Multiple account support. One SnappyMail instance, multiple email accounts in one interface [1].
AGPL-3.0 license — source must stay open, you can audit every line [2][4].

Cons

Small community. 1,552 stars, 7 AlternativeTo likes. Compare to Roundcube’s substantially larger ecosystem. When something breaks at 2am, your support options are GitHub issues and forum luck [2][5].
One primary maintainer. The project health depends heavily on the-djmaze continuing to care. This is not a criticism — it’s a fact to weigh for a long-term bet [2][README].
Incorrectly labeled as discontinued. AlternativeTo’s “Discontinued” badge [5] will confuse anyone who finds it through that channel. The project is alive, but perception matters when you’re pitching it internally.
Not a mail server. Easy to miss in documentation. If your mental model is “I’ll install SnappyMail and have email,” you’ll hit a wall before you start [1].
RainLoop plugin incompatibility. The extension API changed; existing RainLoop plugins don’t work [4]. If your RainLoop setup relied on specific plugins, you’ll need to either find SnappyMail equivalents or write them.
No calendar or groupware. If you want CalDAV/CardDAV integration in a unified interface, look at SOGo or Nextcloud [5]. SnappyMail can connect to Nextcloud via plugin but isn’t a groupware replacement.
Limited third-party documentation. The TechAddressed tutorial is one of the only detailed third-party guides [1]. Roundcube has years of community-written docs; SnappyMail is mostly the official wiki and the GitHub issues.

Who should use this / who shouldn’t

Use SnappyMail if:

You’re migrating off RainLoop and want the path of least resistance — SnappyMail is the continuation of that project [1][4].
You want a webmail client that needs zero database overhead and as small a footprint as possible.
Privacy defaults matter to you: you want software that doesn’t embed Gravatar, Sentry, or social trackers by default [README][2].
You’re already running a VPS with email hosting and want a clean web UI for it without adding another service dependency.
You need a reasonably modern PGP experience in a webmail client [README].

Skip it (consider Roundcube) if:

You want the largest self-hosted webmail community with the most plugins, themes, and documented guides.
You’re already running a database for other services and the no-database argument doesn’t move you.
You want CalDAV/CardDAV contact sync and calendar integration as part of the same tool.

Skip it (consider Nextcloud Mail) if:

You’re already running Nextcloud. Their built-in mail client integrates directly with your Nextcloud contacts, calendar, and files — deploying a separate SnappyMail instance creates redundancy without gain.

Skip it (stay on hosted webmail) if:

You have no VPS and no interest in managing one. Fastmail at $3/mo handles the infrastructure for you and is well-maintained.
Your threat model requires encrypted-at-rest mailbox storage under a privacy-law jurisdiction — ProtonMail’s Switzerland hosting is a structural guarantee that running SnappyMail against a generic VPS provider doesn’t replicate.
You’re not technical and don’t have someone technical available to help. The setup is manageable, but it’s not a “click install” experience.

Alternatives worth considering

From the AlternativeTo listings and the Awesome Privacy database:

Roundcube — the obvious alternative. More community, more plugins, requires a database, similar PHP-based architecture. Default webmail interface on most cPanel hosts. If you want the safest bet for a self-hosted webmail client, this is probably it [5].
SOGo — groupware server with webmail, CalDAV, and CardDAV. More complex to run, but if you need calendar and contact sharing alongside email, it’s the right tool [5].
Nextcloud Mail — if you’re on Nextcloud, just use this. No reason to run a separate service [README integration note].
Mailpile — listed as an alternative but marked Discontinued on AlternativeTo [5]. Do not start a new deployment on it.
Thunderbird — desktop client, not a webmail client. Relevant if your users don’t need browser-based access. Has far more active development and 20 million monthly users [3].
FairEmail / K-9 Mail — Android-only email clients, not web-based. Relevant for mobile-first setups where a native app beats a mobile browser [2].
RainLoop — the parent project. Abandoned, unpatched, do not use [1][2].

For a non-technical founder choosing between these for a small team: the realistic shortlist is SnappyMail vs Roundcube. SnappyMail if you want the lighter footprint and no database. Roundcube if you want the larger community and don’t mind the database dependency.

Bottom line

SnappyMail earns its place by doing one thing well: providing a fast, private, no-database webmail UI for an existing email account. It’s what RainLoop should have been if its developers had kept going, and the fork’s changelog — removing Gravatar, Sentry, jQuery, and a dozen other dead-weight dependencies — reflects a developer who actually cared about the outcome rather than just keeping the lights on. The trade-offs are real: small community, one primary maintainer, thin third-party documentation, and an incorrect “Discontinued” label on AlternativeTo that will slow adoption. It is not a mail server, not a groupware suite, and not a replacement for hosted email with structural privacy guarantees. But for the specific use case — you have an email account, you want a clean web interface you control, you want it to be fast and privacy-respecting — SnappyMail is a legitimate choice, and often the lightest-weight path available.

If you want it deployed and configured without the DIY time, that’s exactly the kind of one-time setup upready.dev handles for clients. You own the result; we do the afternoon of work.

Sources

TechAddressed — “Self Hosting SnappyMail Is Simple With Docker Compose”. https://www.techaddressed.com/tutorials/snappymail-docker-compose/
Awesome Privacy — “SnappyMail | Email Clients | Communication” (GitHub metadata: 1,580 stars, v2.38.2, AGPL-3.0, last updated 17 Apr 2026). https://awesome-privacy.xyz/communication/email-clients/snappymail
Awesome Privacy — “Mozilla Thunderbird | Email Clients | Communication” (reference for Thunderbird community scale). https://awesome-privacy.xyz/communication/email-clients/mozilla-thunderbird
LinuxLinks — “SnappyMail — web-based email client”. https://www.linuxlinks.com/snappymail-web-based-email-client/
AlternativeTo — “Rainloop Alternatives: Top 13 WebMail Providers” (SnappyMail listing: 7 likes, AGPL-3.0, erroneously marked Discontinued). https://alternativeto.net/software/rainloop/