1. Core Architecture: SQL-Backed Traditional Stack vs Stateless Vue.js SPA

The foundational divergence between Roundcube and SnappyMail lies in how each application manages state, sessions, and user configuration.

Roundcube Webmail: Operates as a traditional server-side rendered PHP application. Roundcube requires a relational database (MySQL, MariaDB, PostgreSQL, or SQLite) to operate. Every user login creates rows across multiple relational tables—storing user preferences, session tokens, cached folder lists, contact address books, search indexes, and message caches. Whenever an email is opened or a folder refreshed, Roundcube executes database queries alongside IMAP socket operations. While this architecture allows robust server-side caching and administrative control, it introduces significant database I/O contention on high-density servers.

SnappyMail: Built as a modern, stateless webmail proxy. SnappyMail requires no SQL database backend whatsoever. The server-side PHP component is an ultra-lean gateway that connects directly to the IMAP (TCP 993) and SMTP (TCP 465/587) sockets. User preferences, contact lists, and identities can be stored either in lightweight flat JSON files on disk or synchronized directly to the user’s IMAP mailbox via IMAP METADATA (RFC 5464) and private storage folders. The frontend is a snappy, reactive Single Page Application (SPA) written in Vue.js that renders all HTML, MIME structures, and attachments directly inside the user’s web browser.

# Roundcube Architecture: Multi-tiered dependency chain
User Browser ---> Nginx ---> PHP-FPM 8.2 (128MB/worker) ---> MariaDB (InnoDB Session/Cache)
                                                         ---> Dovecot IMAP (TCP 993)
                                                         ---> Postfix SMTP (TCP 587)

# SnappyMail Architecture: Direct stateless socket proxy
User Browser (Vue.js SPA) ---> Nginx ---> PHP-FPM 8.2 (16MB/worker) ---> Dovecot IMAP (TCP 993)
                                                                    ---> Postfix SMTP (TCP 587)
# (Zero database queries; contacts synced to IMAP or flat JSON storage)

2. Memory Footprint & Server Concurrency Under Load

For system administrators managing mail servers on budget VPS or high-density bare-metal clusters, RAM utilization per webmail session dictates total tenant capacity.

• PHP Memory Consumption: Roundcube requires a minimum memory_limit = 64M in php.ini, with 128M to 256M recommended when users view MIME messages with large attachments or search multi-gigabyte mailboxes. SnappyMail runs comfortably with memory_limit = 16M or 32M, consuming a fraction of server RAM per concurrent worker.
• Disk & Asset Footprint: A typical Roundcube installation with default skins and core plugins occupies 60MB to 120MB on disk. SnappyMail’s entire distribution is under 10MB, optimized for micro-containers and fast edge distribution.
• Page Navigation Latency: In Roundcube, switching between folders or opening threads triggers full or partial server roundtrips with HTML re-rendering. In SnappyMail, Vue.js fetches raw JSON over AJAX/REST, rendering message bodies locally in the browser with sub-100ms response times.

3. Security Architecture & OpenPGP Encryption Models

End-to-end email encryption is paramount for executive correspondence and compliance-driven organizations. Roundcube and SnappyMail implement OpenPGP through radically different security philosophies:

4. Mobile Responsiveness, Skins & Plugin Extensibility

User adoption hinges on mobile usability across smartphones and tablets:

Roundcube: Introduced the responsive “Elastic” skin in version 1.4, which significantly improved mobile usability compared to the legacy “Larry” interface. However, Elastic remains an adapted desktop interface with nested menus and slide-out drawers that can feel sluggish on older mobile devices.

SnappyMail: Built from day one with a mobile-first, reactive design. Gesture navigation (swiping to archive or delete), touch-optimized action buttons, and instantaneous dark-mode switching make SnappyMail feel closer to a native iOS/Android mobile client than a webmail page.

Ecosystem & Plugins: Where Roundcube retains a commanding advantage is in third-party plugins. With over 15 years of development, Roundcube offers hundreds of plugins for cPanel password synchronization, vacation auto-responders, Sieve filtering GUIs, custom LDAP address books, and two-factor authentication (TOTP/U2F). SnappyMail features an active, curated plugin repository (including Sieve filters, 2FA, and nextcloud contacts), but its ecosystem is more focused and compact.

5. Roundcube vs SnappyMail Technical Matrix