One engine, two editions
The community and enterprise editions share one codebase and implement the same protocols and core features — both run the same in-house Mailezine engine. The enterprise edition adds operations and compliance capabilities for multi-user deployments, not a paywall around the basics.
Mail core
| Capability | Community | Enterprise |
|---|---|---|
| Three-pane webmail (threads, shortcuts, offline PWA) | ✓ | ✓ |
| SMTP / IMAP / POP3 with implicit TLS | ✓ | ✓ |
| External account aggregation (fetch) | ✓ | ✓ |
| Real-time push (SSE / Web Push) | ✓ | ✓ |
| Sieve filter editor | ✓ | ✓ |
| Recall, burn-after-read, scheduled send, mail merge | ✓ | ✓ |
| Large attachments and full-text search | ✓ | ✓ |
| ActiveSync (native push, remote wipe) | — | ✓ |
| Delegation (send / manage on behalf) | — | ✓ |
Collaboration
| Capability | Community | Enterprise |
|---|---|---|
| Personal calendar + ICS subscriptions | ✓ | ✓ |
| Personal cloud drive | ✓ | ✓ |
| Contacts with CardDAV / CalDAV sync | ✓ | ✓ |
| Shared team calendars | 1 read-only share | ✓ Unlimited |
| Drive share links | 3 active links | ✓ Unlimited |
| Organization announcements | — | ✓ |
Security & compliance
| Capability | Community | Enterprise |
|---|---|---|
| Anti-spam baseline + DKIM / DMARC (reputation, DNSBL, lists) | ✓ | ✓ |
| Rspamd scanning (checkv2 verdicts, junk headers, reject) | ✓ | ✓ |
| Rspamd self-learning (Bayesian + fuzzy) | — | ✓ |
| Macro scanner (attachment VBA analysis) | ✓ | ✓ |
| 2FA, Passkey sign-in, app tokens, remote-image blocking | ✓ | ✓ |
| PGP signing and encryption | ✓ | ✓ |
| Mail-data backup (engine snapshots, config export) | ✓ | ✓ |
| S/MIME certificate signing and encryption | — | ✓ |
| Compliance archive (capture, retention, review, export) | — | ✓ |
| Outbound DLP (keywords, approval) | — | ✓ |
Management & identity
| Capability | Community | Enterprise |
|---|---|---|
| Admin console (domains, users) | ✓ | ✓ |
| Domain health checks (MX / SPF / DMARC / DKIM compare, blocklists) and DNS wizard | ✓ | ✓ |
| Client autoconfig (autoconfig / autodiscover / MTA-STS) | ✓ | ✓ |
| Delta Chat chat client (scan-to-login QR) | ✓ | ✓ |
| Admin digest email and traffic reports | — | ✓ |
| White-label branding (login page & console) | — | ✓ |
| One-click DKIM setup and rotation | ✓ | ✓ |
| Audit log | ✓ | ✓ + CSV export |
| AD / LDAP directory sync | — | ✓ |
| SSO (OIDC federated login) | — | ✓ |
| AI assistant (centrally governed model config) | — | ✓ |
Architecture & scale
| Capability | Community | Enterprise |
|---|---|---|
| Mailezine engine (single binary, 4.4× measured throughput) | ✓ | ✓ |
| Single-node storage (SQLite/MySQL/PostgreSQL control plane, Pebble KV, local FS) | SQLite by default | ✓ |
| Distributed storage (MySQL control plane, TiDB KV, RustFS/S3) | — | ✓ |
| Multi-instance HA (lease-based failover) | — | ✓ |
| Fully multi-active engine (every replica serves every account; per-message delivery claims, crash take-over, scale by adding replicas) | — | ✓ |
| Stateless control-plane replicas (backend / frontends scale out) | — | ✓ |
| Commercial support (SLA, onboarding) | GitHub | ✓ |
Enterprise-only, at a glance
Enterprise-only: ActiveSync · delegation · S/MIME · compliance archive · outbound DLP · AD/LDAP sync · SSO · white-label branding · audit CSV export · announcements · AI assistant · Rspamd self-learning · admin digest email · traffic reports · unlimited calendar/drive sharing · distributed storage, HA, multi-active engine & control-plane scaling · commercial support
On open source, honestly
What does AGPL-3.0 mean for my deployment?
Your obligations are triggered only when you redistribute a modified version or offer it as a network service to external users — in which case those users are entitled to the corresponding source. Deploying it internally for your own staff triggers no source-disclosure obligation at all. We follow the AGPL text as written, with no extra interpretation.
Will existing open-source features turn paid?
No. The community edition's boundary is defined by what the enterprise edition adds, never by what the community edition takes back — no rug-pull license changes. Every ✓ in the tables above is committed to stay in the community edition for the long term.
Why aren't the enterprise features open source?
Frankly: sponsorships alone cannot sustain full-time development of a mail system. Enterprise license revenue funds community-edition development and maintenance — and the community edition already includes features most paid mail products charge for.