Baïkal

Google Calendar runs on corporate cloud infrastructure, pairing event storage with telemetry and continuous background scripts. Baïkal replaces that dependency with a lightweight CalDAV and CardDAV synchronization server for private hardware. By relying on a local database and standard web protocols, it synchronizes appointments across phones and desktops in milliseconds without consuming server capacity.

Why Baïkal instead of Google Calendar

Google Calendar bundles calendar synchronization with a heavy cloud platform, pushing updates through memory-intensive web applications and background connections. In contrast, Baïkal prioritizes synchronization speed and minimal system overhead. Powered by sabre/dav and written in PHP, Baïkal handles calendar and contact queries using lightweight XML over HTTP. Paired with an SQLite or MySQL database, it answers synchronization requests in milliseconds while using only tens of megabytes of RAM. That low footprint ensures responsive synchronization on low-power hardware like a Raspberry Pi or entry-level virtual server.

The functional difference centers on the interface. Google Calendar and hosted services like Fastmail Calendar include browser views, natural-language event entry, and automated meeting invitations. Baïkal provides no end-user calendar interface—its web portal is strictly an administrative dashboard for provisioning accounts and address books. Users do not view schedules inside Baïkal; they connect native applications such as Apple Calendar on macOS and iOS, Thunderbird on Linux, or DAVx5 on Android. Transitioning requires exporting .ics archives and adding a CalDAV account to each device, after which synchronization runs natively without the lag of cloud web applications.

What it does well

• Native client synchronization: Connects directly with Apple Calendar, Thunderbird, and mobile tools so non-technical users keep their familiar scheduling apps.
• Web administration panel: Includes a simple browser dashboard to add accounts, address books, and calendars without editing configuration files.
• Embedded SQLite storage: Operates from a single SQLite file by default, making backups as simple as copying one file.
• Low resource consumption: Runs comfortably on home NAS units or a Raspberry Pi within a standard PHP environment.
• Combined calendar and contact sync: Supports both CalDAV and CardDAV protocols to keep schedules and address books aligned in one place.