Gulo Gulo is an open-source, mail-first groupware platform built from a shared TypeScript core. It is designed for people who want mail, calendars and contacts to live in one tenant-aware service instead of being scattered across unrelated integrations.
One core, three deployment paths
The project supports three practical deployment targets:
- Standalone for a Linux host under the operator's control.
- cPanel for hosting environments where the panel already owns the account and DNS workflow.
- Plesk for Debian or Ubuntu-oriented hosting environments.
All three targets are built from the same TypeScript source. The packaging boundary stays specific to the operating environment, while the groupware contracts remain shared and testable.
Mail, calendars and contacts
Gulo Gulo is mail-first, but it is not limited to a mailbox view. The platform brings together:
- webmail and tenant-isolated mail operations;
- calendars through CalDAV;
- address books through CardDAV;
- quotas, retention and audit policy;
- tenant-scoped identity and data boundaries.
The CalDAV and CardDAV contracts cover interoperable iCalendar and vCard data, conditional writes, ETags, sync tokens and tombstones. Discovery endpoints provide the usual .well-known and service metadata, with a safe manual fallback when a client cannot discover the service automatically.
The browser surface keeps calendar and contact views deliberately readable, while the authenticated DAV endpoints provide the protocol surface for compatible clients. The project still documents the boundary honestly: real-world verification against every external mail server and every CalDAV/CardDAV client remains a deployment responsibility.
Working with existing hosting panels
If a domain already runs on cPanel or Plesk, Gulo Gulo can sit behind the existing panel rather than replacing the whole hosting account. The panel may continue to own hosting and DNS workflow; Gulo Gulo owns groupware policy, identity, mail, calendars, contacts, quotas, retention and audit.
That integration is deliberately tenant-bound and read-only today. Provider-specific reconciliation is kept separate from the core so that the boundary stays understandable and reversible.
Every deployment still needs a local SMTP/IMAP service reachable by the application. Gulo Gulo connects to that mail service as a client; it does not pretend that a package install alone creates a complete mail infrastructure.
A project that keeps its operational edges visible
The repository includes security, data, interoperability and operations contracts, along with install and upgrade documentation. The current distributable artifacts are operator-facing archives, and the README records where field verification is still required instead of presenting CI as proof of production deployment.
Gulo Gulo is released under the MIT License.
Transparency note
AI-assisted tools are used for test tools and documentation review, including GitHub test-workflow work. Gulo Gulo itself is not an AI product.
Top comments (0)