Baikal 0.9.2: A Lean CalDAV/CardDAV Server for Self-Hosted Stacks

This review examines Baikal 0.9.2, a lightweight CalDAV/CardDAV server, assessing its suitability as a backend for self-hosted calendar and task management needs.

TL;DR

Best for: Users needing a minimalist CalDAV/CardDAV backend for personal or small-team self-hosting, prioritizing low resource usage and direct control over their data. Skip if: You require an integrated web UI for calendar and tasks, or advanced scheduling features, as Baikal provides only server functionality and relies entirely on external clients. Bottom line: Baikal excels as a robust, low-overhead backend component, but it demands external frontend solutions for a complete user experience, which can be a significant integration challenge.

METHODOLOGY

This v0 review draws on the founder's published claims and the project's public documentation at the SabreDAV Baikal GitHub repository. Independent benchmarks are pending. Update cadence: re-tested when claims diverge from observed behavior or when significant new versions are released.

This review covers Baikal version 0.9.2, observed as of June 3, 2026. The primary source signal is a Reddit post from /u/The1TrueSteb, seeking recommendations for a self-hosted calendar stack with a web UI and task integration, specifically mentioning their current use of Baikal for the backend. We cover Baikal's core functionality as a CalDAV/CardDAV server, its architectural design, and its stated capabilities for managing calendars and tasks (VTODO). What is not covered in this review includes independent performance benchmarks, long-term workflow integration, or an exhaustive analysis of edge cases. This review focuses on Baikal's role as a backend component within a broader self-hosted stack, directly addressing the user's struggle to find a suitable frontend.

WHAT IT DOES

Minimalist CalDAV/CardDAV server

Baikal is a self-hosted, open-source CalDAV and CardDAV server designed for simplicity and low resource consumption. It provides the backend infrastructure for synchronizing calendars (events) and contacts across various client applications. Built on PHP, it supports SQLite, MySQL, or PostgreSQL as its database backend, offering flexibility for different self-hosting environments. Its core function is to act as a central hub where client applications can store, retrieve, and synchronize calendar events (CalDAV) and contact information (CardDAV).

Task management via VTODO

While Baikal does not offer a direct user interface, it supports the VTODO specification within CalDAV. This means it can store and synchronize tasks, allowing compliant client applications to display and manage them alongside calendar events. The server handles the underlying data structure for tasks, including due dates, priorities, and completion status, making it a viable backend for a unified calendar and task management system, provided the frontend client supports VTODO.

Lightweight and focused architecture

Baikal's primary design principle is minimalism. It intentionally omits features like a built-in web interface, user management panels, or advanced scheduling tools. This focused approach results in a small footprint, making it suitable for deployment on resource-constrained hardware, such as a Raspberry Pi, or within a shared hosting environment. Its configuration is primarily file-based, appealing to users who prefer direct control over their server setup rather than relying on complex graphical administration tools.

WHAT'S INTERESTING / WHAT'S NOT

Baikal's focused minimalism is its most interesting characteristic. For users who strictly need a robust CalDAV/CardDAV server without any extra bells and whistles, it delivers precisely that. Its stability and low resource footprint are significant advantages for self-hosters on constrained hardware or those seeking to minimize overhead. It provides a solid, standards-compliant foundation for calendar and contact synchronization, making it a reliable building block in a custom self-hosted stack. The ability to use SQLite as a backend simplifies deployment, removing the need for a separate database server for smaller installations.

What is not interesting, or rather, what is critically missing, is the project's slow development cycle. The last major release, version 0.9.2, dates back to August 2021. While the software is stable, this slow pace means it may not keep pace with newer PHP versions, evolving security best practices, or modern client expectations without manual intervention. Critically, Baikal offers no integrated web UI. This forces users to source and configure separate frontend applications, which directly addresses /u/The1TrueSteb's challenge in finding a

Pull quote: “Baikal excels as a robust, low-overhead backend component, but it demands external frontend solutions for a complete user experience, which can be a significant integration challenge.”