Open-source webmail, honestly reviewed. No marketing fluff, just what you get when you self-host a PHP email client.

TL;DR

What it is: Free, open-source (LGPL-2.1) webmail aggregator written in PHP that pulls together multiple email accounts — IMAP, SMTP, JMAP, and Exchange Web Services — into one browser interface [1][5].
Who it’s for: Privacy-conscious users managing multiple email accounts who want a self-hosted web interface instead of trusting Gmail, Fastmail, or any managed webmail client with their messages.
Cost savings: Software is free. You run it on a VPS or your own server. The comparison isn’t “replace Gmail” — Cypht is a client, not an email host — it’s “replace Fastmail’s web interface” or “stop giving Google a front-row seat to your inbox.”
Key strength: Module-based architecture built entirely from plugins, extremely lightweight (~50KB per page load, 3 HTTP requests), and one of the few clients that supports IMAP, JMAP, and Exchange Web Services in the same app [5].
Key weakness: 1,451 GitHub stars after years of development signals a small community, limited third-party reviews exist, and the project appears to be maintained primarily by a single founder. Not the tool for a non-technical founder who needs hand-holding [1][2].

What is Cypht

Cypht (pronounced “sift”) is a self-hosted webmail aggregator. The tagline from the README and every source that covers it is the same: “All your email, from all your accounts, in one place. Cypht is like a news reader, but for E-mail.” [1][5]

That framing is worth taking literally. Cypht doesn’t replace your email accounts — it doesn’t host mail, doesn’t have its own SMTP relay, and doesn’t provide addresses. What it does is give you a single web interface that aggregates existing IMAP/SMTP accounts, with the same combined-view philosophy that RSS readers apply to blog feeds. You connect your accounts, and Cypht shows combined inboxes, combined unread counts, combined flagged views — across all of them simultaneously [5].

Built by Jason Munro (previously the developer behind Hastymail and HastyMail3, which is why the project is sometimes listed as HM3), Cypht’s entire architecture is module-based. The README states plainly: “Cypht is an application built entirely of plugins, or as we call them, module sets.” Every feature — IMAP connectivity, SMTP sending, contacts, RSS reading, LDAP authentication, GitHub notifications — is a module that the framework loads on demand [1][5].

The project sits at 1,451 GitHub stars and 207 forks [1]. That’s low for a project that’s been around since at least 2015. Roundcube, the dominant self-hosted webmail client, sits at a multiple of that. For context: low stars don’t mean a bad project, but they mean a smaller community finding bugs, writing guides, and building modules.

Why People Choose It

The third-party review landscape for Cypht is thin. No deep independent reviews surfaced in research — most coverage is from software directory listings (AlternativeTo, SaaSHub) rather than hands-on writeups. That absence is itself signal: this is a tool with a committed but small user base, not a breakout self-hosted project generating Reddit threads and YouTube tutorials.

From what the available sources show, the users who land on Cypht are typically looking for one of a few specific things:

The multi-account aggregator. If you manage three or four separate email accounts — a personal address, a business address, a consulting address — most webmail clients treat each as a separate login. Cypht’s central design decision is to show combined views: one unified inbox, one unified unread count, across all connected accounts simultaneously [5]. Roundcube doesn’t do this. Gmail does if everything is forwarded to Google. Cypht does it without Google.

Protocol breadth. Most self-hosted webmail clients speak IMAP/SMTP. Cypht also supports JMAP (JSON Meta Application Protocol, a newer standard with more efficient syncing) and Exchange Web Services (EWS) — which means it can connect directly to Microsoft Exchange and Office 365 accounts without relying on a legacy connector [1][5]. For businesses that have some users on Google Workspace and others stuck on Exchange, that’s genuinely useful.

Minimal resource footprint. The LinuxLinks coverage [5] documents this in concrete terms: pages load with 3 HTTP requests totaling roughly 50KB gzipped. The server-side memory peak per request is 4–5MB. The PHP module loader only parses files needed for the current request. For someone running this on a small VPS alongside other services, those numbers matter.

Privacy through self-hosting. The same reason you’d self-host anything: your email traffic doesn’t pass through a third-party company’s servers. Cypht connects your browser directly to your IMAP server. No vendor intermediary reading your messages to serve ads or train models [1].

Features

Based on the README and the LinuxLinks feature coverage [5]:

Core email:

Combined inbox, unread, sent, and flagged views across all connected accounts [5]
Standard IMAP folder browsing and management [5]
SMTP sending with flexible profile configuration (tie IMAP accounts to SMTP accounts, set per-account signatures and reply-to) [5]
Move and copy emails between accounts [5]
Compose in plain text, HTML, or Markdown [5]
JMAP support for faster cross-device sync [5]
Exchange Web Services (EWS) for Office 365 / Exchange accounts [1]

Search and filtering:

Search across all accounts simultaneously with a simple form [5]
Advanced multi-account search via a dedicated module [5]
Sieve filter support — create server-side rules to automatically move, copy, or delete messages based on sender, subject, keywords, or recipient [5]
Save search parameters for repeated use [5]

UI and performance:

~50KB per page load, 3 HTTP requests, parallel AJAX data fetching [5]
Validated HTML5 output, local session storage for content caching [5]
Right-to-left language support [5]
Data-URL-inlined icons (no extra HTTP requests for icons, and they can all be disabled) [5]
Snooze feature to defer emails to a later time [5]

Authentication and sessions:

IMAP authentication (log in with your email credentials)
LDAP authentication
Database authentication (included schema)
Dynamic authentication based on email domain (auto-discovery)
Roll-your-own via the site module [5]
Sessions stored in any PDO-compatible database or flat files [5]

Extensibility:

Module system for IMAP, SMTP, LDAP contacts, WordPress, GitHub, and more [5]
Available via Composer for developers [1]
Docker image available on Docker Hub [1]

The built-in RSS reader is a genuine differentiator — it’s not a checkbox feature grafted on, but part of the founding concept. The same aggregator logic that pulls email from multiple accounts also pulls RSS feeds, and they share the same combined views [5]. Whether that’s useful depends on whether you want your email client doubling as a feed reader, but it’s consistent with the design philosophy.

Pricing: Self-Hosted Cost Math

Cypht has no SaaS tier. The software is free (LGPL-2.1). You self-host it or you don’t use it.

The cost comparison is different from a tool like Zapier or Notion. Cypht doesn’t replace a paid email hosting service — you still need an IMAP/SMTP host (Google Workspace, Fastmail, Migadu, your own mail server). What Cypht replaces is the web interface those providers give you.

The practical question is: does paying for Fastmail or Proton’s hosted webmail interface make sense when Cypht can give you a self-hosted interface against the same underlying IMAP accounts?

Self-hosted Cypht:

Software: $0
VPS to run it: $4–6/month (a 1GB Hetzner or Contabo VPS handles Cypht’s light footprint easily)
You still pay for email hosting separately (Migadu starts at $4/month, Fastmail at ~$3/user/month)

Managed webmail clients (for comparison — data not available in sources):

If you use Fastmail purely as a webmail client at $3–5/user/month, Cypht on a shared VPS is cheaper if you’re managing 2+ accounts
If you’re using Google Workspace at $6/user/month, you can’t replace the hosting with Cypht — but you could replace the web interface

Honest caveat: For a single email account on a provider you’re happy with, replacing their webmail interface with Cypht doesn’t save you meaningful money. The financial case is strongest when you’re aggregating multiple paid accounts and want to replace multiple webmail interfaces with one self-hosted interface that talks IMAP to all of them.

Deployment Reality Check

Docker Hub has an official Cypht image [1]. The install documentation lives at http://cypht.org/install. The GitHub README points to Composer for developers.

What you need:

A PHP-capable web server (Apache or nginx) or Docker
A database (MySQL, PostgreSQL, SQLite — any PDO-compatible store)
Your existing IMAP/SMTP credentials for the accounts you want to aggregate

What the 403 on the official website means: The website scrape returned HTTP 403, suggesting either aggressive bot blocking or intermittent availability issues with the official site [website scrape data]. For a tool you’re evaluating as infrastructure, a 403 on the project website is a yellow flag. The GitHub repository appears actively maintained (last updated April 14, 2026 per AlternativeTo [1]).

Single-maintainer risk: The project’s founder Jason Munro is credited throughout. The AlternativeTo listing shows 153 open issues [1]. Cypht has monthly community meetings (documented in the wiki) which suggests organized development, but the 1,451-star count and limited third-party documentation indicate you’ll be solving problems yourself more often than you’d like.

What can go sideways:

No deep independent setup guides surfaced in research — if you hit a configuration problem, you’re primarily working from the official docs and GitHub issues
The website returning 403 means docs might be intermittently inaccessible; bookmark the GitHub wiki as backup
The module system means some features require finding, installing, and configuring the right module — not plug-and-play for non-technical users

Realistic time estimate: 1–2 hours for a technical user comfortable with PHP app deployment. For a non-technical founder, this is not a first self-hosting project. Deploy Roundcube first, or have someone set this up for you.

Pros and Cons

Pros

LGPL-2.1 license. Genuinely free. You can use it commercially, embed it in products, and the license is more permissive than GPL alternatives [1].
Multi-account aggregation as the core design. Not a feature bolted on — combined views across all accounts are what the tool was built for from day one [5].
JMAP + EWS support. Few self-hosted webmail clients speak both modern JMAP and Exchange Web Services. If you have Exchange accounts in the mix, Cypht is one of the few self-hosted options that handles them [1][5].
Minimal resource footprint. ~50KB page loads, 4–5MB memory per request. Runs comfortably on small shared infrastructure alongside other services [5].
Module system. Every feature is a module. Custom functionality doesn’t require forking the codebase — write a module [1][5].
Built-in RSS aggregation. Combined views for email and feeds in the same interface, if that’s how you work [5].
Sieve filter support. Server-side mail filtering from the web interface [5].
Docker available. One-command deployment path exists [1].

Cons

Very small community. 1,451 stars and limited independent coverage means fewer guides, fewer Stack Overflow answers, and fewer contributors catching edge-case bugs [1][2].
Single-maintainer project. No evidence of a company or large team behind it. Project longevity depends heavily on Jason Munro’s continued involvement.
No deep independent reviews available. Research turned up directory listings, not hands-on evaluations. You can’t find “I ran this for six months and here’s what broke” articles the way you can for Roundcube or n8n.
Official website was inaccessible during research. HTTP 403 on http://cypht.org [website scrape data]. If docs go down, you’re on GitHub and GitHub wiki only.
Not a replacement for your email host. Newcomers sometimes expect a webmail aggregator to host their email. Cypht doesn’t. You still need IMAP hosting somewhere [5].
PHP-based deployment. If you’re already running a PHP web server, this is fine. If you’re not, you’re adding a language runtime and configuration surface.
No mobile app. Web interface only — responsive design assumed but not explicitly confirmed in any source.

Who Should Use This / Who Shouldn’t

Use Cypht if:

You manage 3+ separate email accounts and want unified combined views without routing everything through Gmail
You have a mix of IMAP, Exchange, or JMAP accounts and need a single client that speaks all three protocols [1][5]
You want a lightweight, module-extensible self-hosted webmail interface and are comfortable with PHP server administration
You want to stop paying for multiple webmail subscription tiers and consolidate to a single self-hosted interface
You’re a developer who wants to write custom modules in PHP without forking the core

Skip it (consider Roundcube instead) if:

You need a single well-documented, widely-supported self-hosted webmail client with a large support community
You’re a non-technical founder deploying your first self-hosted app — Roundcube has more guides, more Cloudron/YunoHost packages, and more troubleshooting resources
You want a polished, actively-marketed UI — Roundcube’s interface is more developed and has commercial-grade plugin marketplaces

Skip it (stay on managed webmail) if:

Your email provider’s interface does what you need and you have no interest in server administration
You manage a single email account — the aggregation case doesn’t apply
Your compliance requirements don’t allow infrastructure you manage yourself

Skip it (consider Mailpile or Proton Bridge) if:

End-to-end encryption is the primary requirement — Cypht doesn’t appear to address PGP or S/MIME in the available sources

Alternatives Worth Considering

Roundcube — the dominant self-hosted webmail option. More stars, more documentation, more Cloudron packages, more commercial hosting support. Single-account focused but supports identities and external accounts. The safer default for non-technical users [2].
SnappyMail — actively maintained fork of RainLoop. Lighter than Roundcube, simpler configuration. Flagged as discontinued on AlternativeTo but the project is still active on GitHub [2].
SOGo — if you need groupware alongside webmail: shared calendars, address books, CardDAV/CalDAV. More infrastructure to run, but adds collaboration features Cypht doesn’t have [2].
Horde Groupware — similar groupware angle to SOGo, longer history, reportedly flagged as discontinued in some directories [2][3]. Evaluate maintenance status carefully.
Mailpile — privacy and encryption-focused webmail client. Also flagged as discontinued in some directories [2]. Check the GitHub before committing.
AfterLogic WebMail Lite — lighter alternative, free community edition, simpler setup [3].

For a non-technical founder who just wants self-hosted webmail and doesn’t need multi-account aggregation, the realistic choice is Roundcube. It has more documentation, more pre-built packages, and a larger community finding and fixing bugs. Cypht is the better choice if the aggregation use case is real and JMAP/EWS support matters.

Bottom Line

Cypht solves a specific problem well: if you have multiple email accounts across different providers — including Exchange — and want a single self-hosted web interface that shows them together, Cypht is one of very few free options built around that exact use case. The LGPL-2.1 license, sub-50KB page loads, and protocol breadth (IMAP, JMAP, EWS) are real differentiators. The trade-offs are equally real: a small community, limited independent documentation, and a project that appears to rest significantly on a single maintainer. For a non-technical founder, Roundcube is the lower-risk self-hosted webmail entry point. For a developer or technical operator managing a mixed account environment who needs aggregated views across protocols, Cypht is worth the evaluation.

If deployment is the blocker, that’s exactly what upready.dev handles — one-time setup, you own the infrastructure.

Sources

AlternativeTo — Cypht: All your E-mail, from all your accounts, in one place. https://alternativeto.net/software/cypht/about/
AlternativeTo — Rainloop Alternatives: Top 13 WebMail Providers (includes Cypht listing). https://alternativeto.net/software/rainloop/
SaaSHub — Cypht Alternatives & Competitors. https://www.saashub.com/cypht-alternatives
SaaSHub — HEY Alternatives & Competitors (includes Cypht listing). https://www.saashub.com/hey-alternatives
LinuxLinks — Cypht: webmail aggregator (detailed feature overview). https://www.linuxlinks.com/cypht-webmail-aggregator/