Baïkal

Self-hosted calendar and contact sync, honestly reviewed. No marketing fluff, just what you get when you run your own CalDAV and CardDAV server.

TL;DR

• What it is: A lightweight, self-hosted CalDAV and CardDAV server — the protocol layer that syncs your calendars and contacts across every device, without Google, Apple, or any third party in the middle [1][3].
• Who it’s for: Individuals, families, and small teams who want to own their contact and calendar data, run a privacy-respecting stack, and never pay a recurring sync bill again [1].
• Cost savings: Google Workspace runs $6–$12/user/month. iCloud+ starts at $0.99/mo for 50GB but ties your data to Apple’s ecosystem. Baïkal runs on a $5/mo VPS for as many users as your hardware handles — no per-seat pricing, no data on someone else’s servers [1].
• Key strength: Genuinely lightweight. Runs on nearly any PHP-capable shared host or VPS, uses SQLite if you don’t want to manage a database, and stays out of your way once configured [1][3].
• Key weakness: This is a sync protocol server, not a groupware suite. No webmail, no task UI, no shared document editing. You still need a client — Thunderbird, iOS, DAVx5 on Android — to actually view your calendars and contacts [1][2].

---

What is Baïkal

Baïkal is a CalDAV and CardDAV server. Those two protocols are the open standards that calendars and contacts have used to sync between devices for over a decade — they’re what powers Apple Calendar, Thunderbird, and DAVx5 on Android behind the scenes. When you use Google Calendar or iCloud, a CalDAV server is running somewhere. Baïkal lets you run that server yourself.

The project was created by Jérôme Schneider of Net Gusto and fruux, and is now maintained by volunteers. It’s built on top of sabre/dav — a mature, battle-tested PHP library for DAV protocols — which means Baïkal inherits solid protocol compliance without reimplementing everything from scratch [README][3]. Released under GPL-3.0, it sits at 3,104 GitHub stars as of this review.

The pitch is as plain as the website: “Protect your privacy by hosting calendars and contacts yourself.” There’s no aggressive growth marketing, no VC funding story, no AI angle bolted on. It’s a focused tool that does one thing — expose CalDAV and CardDAV endpoints to your devices — and has been doing it reliably for years [1][3].

What Baïkal is not is equally important to understand upfront. It has no calendar or contacts UI for end users. You manage users and address books through an admin panel, but you don’t open Baïkal in a browser to check your schedule. Your phone, Thunderbird, or Apple Calendar does that over the sync protocol Baïkal provides [1][2]. This distinction trips up people coming from Nextcloud or Google Workspace expecting a full groupware experience.

---

Why people choose it

The core decision is almost always about data sovereignty. If your calendar contains business meetings, client names, and travel plans — and your contacts list contains every professional relationship you’ve built — handing that data to Google or Apple is a non-trivial privacy trade. Baïkal is the minimal-overhead answer to that problem [1].

The comparison in reviews consistently lands in three directions:

Versus Google Calendar / iCloud. This is who most people are actually escaping. The argument isn’t primarily about cost at the personal level — Google Calendar is free and iCloud is cheap. The argument is about data: who indexes it, who can read it, who subpoenas it, and what happens when a policy change kills a feature you rely on. Baïkal eliminates that dependency entirely [1].

Versus Nextcloud. Nextcloud also provides CalDAV and CardDAV sync and is a popular comparison. The difference is scope. Nextcloud is a full cloud platform — file sync, photo management, office suite integrations, and dozens of apps on top. Baïkal is just the sync layer. If you want file sync, Nextcloud is the better choice. If you want calendar and contact sync without running an entire cloud platform, Baïkal is significantly simpler to deploy and maintain [1][2].

Versus SOGo. SOGo is a full groupware server: webmail, shared calendars, contact management, and a web UI for end users [2]. The trade-off the appmus.com comparison makes clear: SOGo requires considerably more infrastructure (external database, mail transport agent, more complex configuration) and provides substantially more features. Baïkal requires almost nothing and provides just the sync protocols. For a solo founder or family who already uses Thunderbird or a mobile client, Baïkal’s simplicity wins. For a team that wants a shared web UI and webmail, SOGo or Nextcloud is the right answer [2].

Versus Radicale. Radicale is another minimal CalDAV/CardDAV server, written in Python, with an even smaller footprint than Baïkal. It doesn’t have a web admin panel at all — configuration is entirely file-based. Baïkal has the edge on usability for anyone who wants to manage users through a browser rather than editing config files.

---

Features

Based on the official website and README:

Core protocol support:

• CalDAV: calendar sync including events, recurring events, and tasks
• CardDAV: contact synchronization with vCard support
• Full multi-user support — each user has their own calendars and address books [1]
• Calendar sharing between users is supported at the protocol level

Client compatibility:

• iOS and macOS native calendar and contacts apps (built-in CalDAV/CardDAV support)
• Android via DAVx5 (free, open-source sync adapter on F-Droid/Play Store)
• Mozilla Thunderbird with the built-in calendar (Lightning)
• Any other CalDAV/CardDAV-capable client — the protocol is open and widely implemented [1][3]

Storage:

• MySQL/MariaDB for multi-user deployments or production setups
• SQLite for single-user or lightweight installs — no database server required [1][3]

Administration:

• Web-based admin panel for user management, calendar creation, and address book management [1]
• No command-line-only setup required once deployed

What’s missing (by design):

• No webmail
• No end-user web UI for viewing calendars or contacts — purely a sync backend [1][2]
• No built-in task management UI
• No document sharing or file sync
• No mobile app (the “mobile_app” feature in the profile refers to client compatibility, not a native app)

---

Pricing: SaaS vs self-hosted math

Baïkal has no pricing page because it has no paid tier. The software is GPL-3.0 licensed and free to self-host. What you’re paying for is infrastructure.

What alternatives cost:

• Google Workspace: $6/user/month (Business Starter), includes Gmail, Calendar, Contacts. A 3-person team = $18/mo, $216/year.
• iCloud+: $0.99–$9.99/mo for storage, but calendar and contacts sync is bundled. Locks you to Apple ecosystem; sharing with Android users is awkward.
• Fastmail: ~$5/user/month — includes CalDAV/CardDAV sync, webmail, and a clean interface. Legitimate alternative if you want managed hosting.
• Proton Calendar + Contacts: €3.99–€9.99/mo for Proton Unlimited. Strong on privacy, but proprietary sync — only works with Proton’s own apps.

Self-hosting Baïkal:

• VPS (Hetzner CX11, or similar): ~$4–6/mo
• Domain: ~$10–15/year
• Baïkal license: $0
• Total: roughly $5–7/mo for unlimited users

For a family of four or a small founding team, the math is stark: $18/mo × 12 = $216/year on Google Workspace, versus $72/year in VPS costs with Baïkal — and you own the data. Data not available on exact per-seat savings beyond these estimates since Baïkal has no commercial tier to compare against [1].

The honest caveat: that $72/year assumes you’re comfortable with initial setup and light ongoing maintenance. If you’re paying someone to deploy and manage it, factor that cost in too.

---

Deployment reality check

The README points to sabre.io/baikal for installation instructions, and both a German and French community guide exist specifically targeting users without deep IT experience [README]. That’s a useful signal — the project acknowledges non-expert users and has community-maintained documentation for them.

What you need:

• A web server with PHP (Apache or nginx; most shared hosting works)
• PHP 7.4+ with standard extensions (curl, dom, PDO)
• MySQL/MariaDB or SQLite
• A domain name or subdomain for your CalDAV endpoint

What makes Baïkal different from most self-hosted software: it can run on shared hosting. You don’t need a VPS with Docker and root access. If you already pay for shared hosting with PHP support, you can deploy Baïkal there. This is a meaningful accessibility advantage over tools like Nextcloud or SOGo, which require more control over the server environment [1][3].

Docker option: The website lists unofficial Docker installation instructions. Docker isn’t the primary supported path (unlike most modern self-hosted tools), but it works and some users prefer it for isolation [website].

What can go wrong:

• CalDAV and CardDAV sync requires correct URL configuration on each client device. This is the step where non-technical users get stuck — iOS settings bury the CalDAV server configuration several menus deep.
• Upgrades require following the upgrade instructions carefully. The README links to a dedicated upgrade page — don’t skip it [README].
• If you’re on shared hosting with restrictive PHP configurations or older PHP versions, you may hit compatibility issues.
• No built-in backup solution. Backing up your SQLite file or MySQL database is your responsibility.

Realistic setup time for someone comfortable with web hosting: 30–60 minutes. For someone setting up a VPS for the first time: 2–3 hours including server setup, nginx/Apache configuration, and client device setup. The clients (iOS, DAVx5, Thunderbird) each need to be pointed at your server URL with your credentials — budget 5–10 minutes per device.

---

Pros / Cons

Pros

• Genuinely lightweight. Minimal resource requirements — runs on shared hosting, a Raspberry Pi, or the cheapest VPS tier. No Docker required, no Kubernetes, no microservices [1][3].
• Proven protocol foundation. Built on sabre/dav, a widely deployed and protocol-compliant DAV library. It works with every standard CalDAV/CardDAV client [1][3].
• Broad client compatibility. iOS, macOS, DAVx5 on Android, Thunderbird, Outlook (with plugin), and any other compliant client [1].
• SQLite support. Eliminates the database server requirement for simple deployments [1][3].
• Web admin panel. You can add users and manage calendars without touching config files [1].
• Can run on shared hosting. This is rare among self-hosted tools and matters for people who don’t want to manage a VPS [1][3].
• GPL-3.0 licensed. Fully open source, no commercial license tiers, no features gated behind a paywall [1][3].
• Community guides in multiple languages. German and French guides specifically written for non-technical users reduce the setup barrier [README].

Cons

• No end-user UI. If a family member needs to check their calendar in a browser, they can’t open Baïkal — they need a client app. This is a hard limitation for anyone expecting a full web interface [1][2].
• No webmail, no tasks UI, no file sync. Baïkal is a sync server, not a groupware suite. If you need those features, you need Nextcloud, SOGo, or something else [2].
• Volunteer-maintained. The project is maintained by volunteers, not a funded company. The pace of updates and responsiveness to security issues depends on contributor availability [README].
• Setup requires some server knowledge. While simpler than most, you still need to configure a web server, point DNS, and set up clients on each device. Non-technical founders doing this alone should budget more time [1].
• No native mobile app. You sync with your existing native apps (iOS Calendar, Google Contacts app, etc.) via DAVx5 — Baïkal itself has no app [profile].
• Minimal community presence. There’s no active forum or Discourse instance. Support is GitHub issues and community-written guides [3].
• Third-party review coverage is thin. Unlike Nextcloud or n8n, Baïkal has almost no recent in-depth reviews or benchmarks. This makes it harder to validate edge cases before committing.

---

Who should use this / who shouldn’t

Use Baïkal if:

• You want to stop syncing your calendars and contacts through Google, Apple, or Microsoft — and you want the simplest possible way to do it.
• You’re on shared hosting and can’t run Docker-based tools.
• You already have clients (iOS, Thunderbird, DAVx5) and just need a server to sync against.
• You’re a developer or sysadmin comfortable with basic web server configuration.
• Your household or small team needs multi-user calendar/contact sync without paying per seat.

Skip it (use Nextcloud instead) if:

• You also want file sync, photo backup, or a web-based document editor. Nextcloud includes Baïkal-equivalent CalDAV/CardDAV plus all of that.
• You want a web UI where family members can browse their calendar in a browser without installing anything.

Skip it (use SOGo instead) if:

• Your team needs shared calendars, webmail, and a web-based groupware interface. SOGo is heavier to deploy but covers all of that [2].

Skip it (use Fastmail or Proton instead) if:

• You want privacy-respecting calendar and contact sync but you don’t want to manage any infrastructure. Fastmail and Proton are managed services with strong privacy postures and CalDAV/CardDAV support.

Skip it (stay on Google or iCloud) if:

• You have fewer than 3 users and the free tiers work fine.
• You can’t manage or pay someone to manage a server.
• You share calendars heavily with people outside your household and need seamless cross-platform sharing without explaining CalDAV client setup.

---

Alternatives worth considering

• Nextcloud — the full-stack alternative. Includes CalDAV/CardDAV, file sync, photo management, and a web UI. Heavier to deploy and maintain, but one install covers everything. The obvious choice if you want more than just calendar/contact sync.
• SOGo — full groupware server with webmail, shared calendar, and contacts web UI. Better for teams that need a web interface. Significantly more complex to set up [2].
• Radicale — another minimal CalDAV/CardDAV server, written in Python, even lighter than Baïkal. No web admin panel — purely config-file-based. For single-user technical deployments.
• Fastmail — managed service at ~$5/user/month. Includes webmail, CalDAV, CardDAV, calendar and contacts UI. The answer if you want the result without the server work.
• Proton Calendar + Contacts — privacy-focused managed service. Strong encryption, but sync works mainly through Proton’s own clients, which limits compatibility with third-party apps.
• EteSync — end-to-end encrypted calendar and contact sync. Self-hostable, more modern stack than Baïkal, but smaller community.

---

Bottom line

Baïkal is the smallest credible answer to a specific question: how do I stop syncing my calendars and contacts through Google or Apple without rebuilding my entire infrastructure? It’s not trying to replace Google Workspace — it’s trying to replace the one piece of Google Workspace you actually need for data sovereignty. If your clients are already in place (iOS, Thunderbird, DAVx5), adding Baïkal takes an afternoon and costs you $5/mo in VPS fees. The trade-off is real: no web UI for end users, no webmail, volunteer maintenance cadence. But for a solo founder, a family, or a small team that just wants its calendar and contact data off someone else’s servers, Baïkal delivers exactly that promise without unnecessary complexity.

If the server setup is the blocker, that one-time deployment is exactly what upready.dev handles for clients.

---

Sources

1. Baïkal: Features, Alternatives & Analysis (2026) — appmus.com. https://appmus.com/software/baikal
2. SOGo vs Baïkal Comparison (2026) | Feature by Feature — appmus.com. https://appmus.com/vs/sogo-vs-baikal
3. Baïkal - CalDAV and CardDAV server — LinuxLinks. https://www.linuxlinks.com/baikal-caldav-carddav-server/

Primary sources:

• GitHub repository and README: https://github.com/sabre-io/baikal (3,104 stars, GPL-3.0 license)
• Official website: https://sabre.io/baikal
• Installation instructions: https://sabre.io/baikal/install/
• Docker installation guide: https://sabre.io/baikal/docker-install/