Roundcube vs SOGo: Which Open-Source Webmail to Deploy

The Roundcube vs SOGo webmail question looks like a choice between two web interfaces. It is not. Roundcube is a webmail client — it reads and writes IMAP, and that is its whole job. SOGo is a groupware server that happens to include a webmail interface, and the interface is the smallest part of what you are installing.

That distinction decides almost everything downstream: what your phones can sync, what you have to back up, and how much a major-version upgrade costs you. This guide compares the two on capability dimensions you can verify on each project's own pages. We have not run a controlled bake-off of both stacks under identical load, and any page claiming to have done so should be read carefully.

The verdict up front#

Deploy Roundcube when mail is the requirement and calendaring is somebody else's problem. It is a single PHP application in front of an IMAP server. If your users already have calendars in Nextcloud, Google Workspace or a standalone CalDAV server, adding SOGo buys you a second calendar system to reconcile, which is worse than having one.

Deploy SOGo when you need shared calendars, shared address books and phones that sync without asking anyone to install a third-party app. SOGo's native ActiveSync is the single feature that most often settles the argument, because it is what lets an iPhone or an Outlook profile pull mail, calendar and contacts over one account rather than three.

For a small team on a self-hosted mail server, SOGo is usually the right default — and mailcow's decision to ship it as the built-in webmail and CalDAV/CardDAV interface is a reasonable signal of that. For a single-purpose mail host, a hosting control panel, or a deployment where you are the only person who will ever fix it, Roundcube's smaller surface is worth more than SOGo's feature list.

Roundcube vs SOGo at a glance#

The table reads best as two columns of scope rather than two columns of quality. Roundcube is not missing calendars the way a product is missing a feature; it is not a calendar server, and never claimed to be.

Where Roundcube wins#

Roundcube wins on surface area. It is one PHP app talking to an IMAP server you already run. Its own feature list is deliberately narrow: drag-and-drop message management, a full address book with groups and LDAP connectors, a responsive skin for multiple devices, and PGP support. There is no calendar in that list, and that is a design decision rather than an omission.

That narrowness is why it is the default webmail in so many hosting panels. A control-panel vendor wants a webmail that installs next to whatever mail stack the customer already has, does not own any data of its own worth losing, and can be upgraded without a migration plan. Roundcube fits that shape and SOGo does not.

It also wins on extensibility. The plugin ecosystem is one of the oldest in open-source webmail and covers the long tail — sieve rule editors, password changing, two-factor, per-domain branding. If your requirement is unusual and specific, the odds are better that a Roundcube plugin exists than that SOGo has a setting for it.

• One application to patch, one config file to reason about
• Runs against any IMAP server without owning its own data store
• Mature plugin ecosystem for the long tail of requirements
• Skin system, including a responsive skin, if the interface has to match a brand
• PGP support in the client for users who want end-to-end encryption

Where SOGo wins#

SOGo wins the moment a second person needs to see your calendar. It describes itself as a fully supported groupware server focused on scalability and open standards, and it supports native clients through CalDAV, CardDAV and GroupDAV. Those three protocols are what turn a mail server into something a team can actually run on.

The sharper win is native Microsoft ActiveSync. SOGo implements it itself, which means an iPhone, an iPad or an Android mail app can be set up as an Exchange-style account and get mail, calendar and contacts over one connection. Roundcube cannot do this and should not be expected to — it is a web page, not a sync protocol endpoint.

Shared access is the third win. Calendars and address books have owners and ACLs, so delegation, a shared team calendar and a shared contacts list are configuration rather than a plugin hunt. If any of your users have ever said the words "can you just put it in the team calendar", the argument is already over.

• Native ActiveSync, so phones sync mail, calendar and contacts as one account
• CalDAV, CardDAV and GroupDAV for Thunderbird, Apple Calendar and everything else standards-based
• Shared calendars and address books with per-object access control
• Outlook compatibility via the Outlook CalDav Synchronizer, a separate third-party tool
• Shipped by default in mailcow, so the integration work is already done for you

Does SOGo support ActiveSync, and can Roundcube?#

Yes — SOGo provides native Microsoft ActiveSync support, stated on its own site. It is not a bridge, a proxy or a paid module; the server speaks the protocol. In practice this is the feature people search for by name, because it is the difference between a self-hosted mail setup that non-technical staff will tolerate and one they will quietly abandon for Gmail.

Roundcube has no ActiveSync of its own, and adding it is not a plugin-shaped problem. ActiveSync is a server protocol with its own state — device IDs, sync keys, partial sync windows — and Roundcube has no place to keep that state. If you need ActiveSync alongside Roundcube you run a separate sync server such as a Z-Push-style gateway or SOGo itself, and Roundcube stays purely the browser interface.

One caveat worth knowing before you promise it to anyone: ActiveSync device state is real state. It has to be backed up, it can wedge on a single misbehaving device, and a botched upgrade can trigger a full resync across every phone at once. It is a feature and an operational responsibility in the same box.

Is Roundcube still maintained?#

Yes. Roundcube's own news page shows security updates 1.6.19 and 1.7.4 released on 6 September 2026, with 1.7.4 as the current download. Two supported branches receiving coordinated security releases on the same day is the behaviour of a maintained project, not an abandoned one.

The governance question behind the search is worth answering too. The project's founder stepped back and Nextcloud took over the project organisation, announced on roundcube.net in November 2023. So Roundcube is not a lone-maintainer risk in the way it was sometimes described before that; it sits under an organisation with a commercial interest in it continuing.

SOGo's maintenance answer is similar in shape. Its site lists version 5.12.11 released on 14 September 2026, developed under Alinto with a public GitHub repository. Neither project is the risk in this comparison. Your own upgrade discipline is.

Which open-source webmail has calendars?#

SOGo does, natively, with CalDAV. Roundcube does not ship one in its default install — its own feature list names message management, the address book, the responsive skin and PGP, and no calendaring.

Calendar functionality can be added to Roundcube through plugins, and several exist, but this is where a lot of deployment plans quietly go wrong. A plugin gives you a calendar view; it does not give you a calendar server. Unless that plugin is talking to a real CalDAV backend you already run, you end up with calendar data living inside the webmail application, invisible to every phone and desktop client your users own.

The honest rule: if calendars matter, decide where the calendar server lives first, then pick the webmail that talks to it. SOGo is that server and its own interface. Roundcube is a client that can be pointed at one.

Can you run Roundcube and SOGo together?#

Yes, and on mailcow it is a common setup. mailcow ships SOGo as the integrated webmail and CalDAV/CardDAV interface, and lists Roundcube separately as a community-managed third-party integration you can add. Both point at the same Dovecot mailboxes over IMAP, so mail state — read, flagged, filed — stays consistent between them.

The usual reason to do it is that people disagree about interfaces. Some users prefer Roundcube's mail-reading experience; the calendar, contacts and phone sync keep running through SOGo regardless of which page anyone has open. Mail is shared because IMAP is the source of truth; calendars are not, because Roundcube is not a participant in them.

The cost is two web applications to patch, two sets of authentication to keep working, and two places a user can change a setting and be confused about why it did not apply everywhere. Run both if there is a real preference to satisfy. Do not run both to avoid making a decision.

The axis most comparisons skip: what you are agreeing to maintain#

Feature tables make SOGo look strictly better, because more rows say yes. That framing hides the actual decision, which is about ownership of state.

Roundcube owns almost nothing. Lose the Roundcube database and you lose user preferences and the personal address book. Your mail is untouched, because it was never Roundcube's. Rebuilding is a reinstall plus a config file, and a botched upgrade is an afternoon.

SOGo owns a great deal: calendars, address books, ACLs, sieve rules it manages, and ActiveSync device state. All of that has to be in your backups and has to survive restores. A major-version upgrade is a maintenance window with a rollback plan, not an afternoon. That is not an argument against SOGo — it is the price of the features, and it is the number you should put in the plan.

There is also a staffing dimension. Roundcube is PHP, which nearly any web host can debug. SOGo runs on Objective-C over GNUstep alongside a database, which is perfectly stable but a smaller pool of people can read a stack trace from. On a two-person team that difference shows up on the worst possible day.

What each one costs#

Both are open source and you can run either without paying a licence fee, which is why the cost conversation moves to support and hosting rather than to a price list.

Both projects also exist alongside commercial offerings and hosted options, and those arrangements change more often than the software does. We do not print third-party prices here, because a figure copied from a comparison page is stale the day the vendor edits theirs. Check the packaging shape on the vendor's own page at the moment you are buying.

The cost that actually differs is operational. SOGo's extra services, extra backups and longer upgrade windows are real hours, so if you are pricing this for a client, price the maintenance shape rather than the download.

Who each is genuinely for#

Roundcube is for the deployment where mail is the product. Hosting companies and control panels, a single-purpose mail VPS, a personal domain, a team that already lives in Google Calendar or Nextcloud and needs nothing more than a browser view of IMAP. It is also the right pick when the person who will maintain it is not a full-time sysadmin.

SOGo is for the small organisation replacing a hosted groupware product. Five to fifty people who need one team calendar, one shared address book and phones that just work — that is exactly the gap SOGo fills, and doing it with Roundcube plus a pile of plugins is more work and less reliable.

For sogo vs roundcube for a small team specifically: if the team shares a calendar, choose SOGo, preferably via mailcow so the wiring is done for you. If the team shares nothing but a mail domain, choose Roundcube and spend the saved hours somewhere else.

1. 1

   Does anyone need to see anyone else's calendar?

   If yes, you need a groupware server. SOGo. If no, keep reading.

2. 2

   Do phones need to sync calendar and contacts from this server?

   If yes, SOGo's native ActiveSync is the shortest path. Roundcube cannot provide this.

3. 3

   Is there already a calendar system in the organisation?

   If yes, do not add a second one. Point people at the existing one and deploy Roundcube for mail.

4. 4

   Who fixes it at 2am?

   If the answer is a generalist rather than a sysadmin, weight Roundcube's smaller surface heavily.

A third option, honestly#

Neither of these answers the question a lot of people are actually asking, which is not "which webmail do I install" but "why does reading my mail take two hours a day". Roundcube and SOGo both give you a competent view of an inbox. Neither triages it, drafts replies or closes loops for you — that is not what a webmail package is for.

That is the job we work on. We build AI Emaily, an AI-native email client that connects to Gmail, Outlook and any IMAP account — including the Dovecot server behind your Roundcube or SOGo install — and adds triage, semantic search across every account, and drafting that follows a Personal Context brain and per-client profiles you set yourself, rather than anything inferred from your mail without you asking. Sends go through approval first, with undo and an audit trail.

The limit, stated plainly: AI Emaily is not a self-hosted webmail package. It is not a replacement for Roundcube or SOGo, it does not run on your server, it is not a CalDAV or ActiveSync server, and if your requirement is that everything stays inside your own infrastructure then this comparison ends at the two options above and you should stop here. What it replaces is the client you read mail in, not the server you run. Pricing is a 7-day free trial on Pro and Autopilot rather than a free tier — details on our pricing page.

How to decide this week#

Pick on the calendar question, install on a throwaway VM, and give it to one real user before you commit a domain to it.

1. 1

   Write down whether calendars are in scope

   One sentence. This decides the stack and everything else follows from it.

2. 2

   If yes, install mailcow and use the bundled SOGo

   You get SOGo already wired to Dovecot with CalDAV, CardDAV and ActiveSync configured, which removes most of the hard part.

3. 3

   If no, install Roundcube against your existing IMAP server

   Confirm login, folder list, sending, and whichever plugins you actually need before you point users at it.

4. 4

   Pilot on the phones your team really uses

   Add one account per platform. ActiveSync and CalDAV problems are device-specific and show up immediately.

5. 5

   Write the backup and upgrade plan before go-live

   For SOGo this includes the database and device state. For Roundcube it is preferences and the address book. Test a restore once.