Communications guide
Self-Hosted Calendar: Pick CalDAV, a Full Suite, or Managed Cloud
Choose Radicale, Baïkal, Nextcloud Calendar, or managed cloud by client compatibility, invitations, recovery, and operating responsibility.
Published and reviewed by OpenAlt · September 28, 2026
Verdict
Choose Radicale when you want a focused, open-source calendar server with CalDAV and CardDAV. Choose Baïkal when you prefer a lightweight DAV server with web-based administration. Choose Nextcloud Calendar when calendars belong inside a broader collaboration platform you already need. Choose managed cloud when nobody can own uptime, TLS, backups, client compatibility, and invitation delivery.
The decision is operational, not ideological. A calendar server stores and syncs calendar data; an email invitation system sends messages and handles deliverability. They are separate jobs. Self-hosting one does not solve the other.
Table of contents
- The three operating models
- Evidence at a glance
- Choose by household or team
- Client and discovery checklist
- Calendar hosting is not invitation delivery
- Migration proof of concept
- Backup, restore, and security
- When managed cloud is better
- FAQ
The three operating models
1. Focused CalDAV: Radicale
Radicale fits “sync calendars and contacts without a full collaboration suite.” Its narrow boundary can reduce resource use and simplify operations. It suits technical individuals, families, and small teams able to run a service and validate clients.
Put it behind a reverse proxy with authenticated CalDAV/CardDAV access; desktop and mobile clients provide the user experience. You still own DNS, TLS, accounts, backups, monitoring, upgrades, and invitation behavior.
As of September 28, 2026, the Kozea/Radicale repository shows 5,056 stars, uses GPL-3.0, and lists version 3.8.1, released September 24, 2026. Start with the project’s deployment documentation. Radicale
2. Lightweight DAV administration: Baïkal
Baïkal is a focused option: a lightweight CalDAV/CardDAV server with dedicated web administration. It suits operators who prefer managing users and collections through an interface. It avoids file sharing, chat, and document collaboration.
You still maintain the web stack, storage, access controls, upgrades, and recovery. A small application is not maintenance-free.
As of September 28, 2026, sabre-io/Baikal shows 3,325 stars, uses GPL-3.0, and lists version 0.12.1, released August 5, 2026. Follow its supported deployment flow and prerequisites. Baïkal installation guide
3. Full collaboration suite: Nextcloud Calendar
Nextcloud Calendar fits when calendar is one part of a broader collaboration environment. If you need file synchronization, shared folders, address books, groups, or other apps, one platform may justify its footprint.
Choose it because the suite is warranted, not merely because it includes a calendar. Expect more components, upgrades, permissions, and capacity decisions.
As of September 28, 2026, the nextcloud/calendar repository shows 1,190 stars and active project activity. GitHub’s latest release endpoint surfaces v3.3.2 from 2022, so do not treat that endpoint as the current packaged application version. Check the Nextcloud release and app context matching your deployment. Nextcloud Calendar repository · Nextcloud Calendar administration
Evidence at a glance
| Option | Best fit | Main strength | Main responsibility |
|---|---|---|---|
| Radicale | Personal, family, small technical team | Focused CalDAV/CardDAV | Infrastructure and client validation |
| Baïkal | Small deployment favoring web administration | Lightweight DAV server | Web stack, accounts, storage, recovery |
| Nextcloud Calendar | Team needing collaboration tools | Calendar integrated with broader services | Suite upgrades, permissions, capacity |
| Managed cloud | No clear operator owner | Outsourced availability and compatibility | Subscription, provider trust, migration control |
Repository stars are context, not a service guarantee. They do not prove backups, mobile behavior, invitation delivery, or support. Confirm deployment requirements, then test the clients and workflows your household or team needs. Radicale · Baïkal
Choose by household or team
For one user, self-hosting makes sense when learning, control, or ownership is part of the goal. Radicale is the smallest commitment; Baïkal fits if its administration model is preferable. If outages are costly, choose managed cloud.
For a family, prioritize simple sharing and recovery. Test account recovery, mobile onboarding, shared calendars, time zones, and invitations before migration. A focused DAV server works when one person owns operations and documents them.
For a small team, identify who handles holidays, outages, certificate failures, and broken upgrades. If ownership is unclear, managed cloud is safer. Choose Nextcloud when calendars depend on files, groups, and collaboration; otherwise, a smaller DAV service reduces administrative surface.
Client and discovery checklist
“CalDAV compatible” does not guarantee identical behavior. Before committing, verify each client:
- Supports account discovery, shared and read-only calendars, and multiple accounts.
- Syncs in the background, notifies, supports offline edits, and reauthenticates.
- Uses automatic discovery or documents the principal, calendar-home, or collection URL.
- Handles time zones, daylight saving, recurrence, cancellations, and deletion.
- Supports attendee changes and reports conflicts between clients.
- Supports CardDAV separately when contacts are required.
- Gives useful certificate and authentication errors.
Test the exact desktop, phone OS, account setup, and server version. Protocol support only starts the check; a proof of concept establishes usability. Nextcloud administration guide
Calendar hosting is not invitation delivery
A self-hosted calendar can sync events without being a reliable outbound mail platform. Invitations require message generation, SMTP credentials, DNS authentication, deliverability, bounce handling, and cross-provider compatibility.
- The calendar server stores events, attendees, recurrence, and changes.
- The mail system sends invitations, updates, and cancellations.
- External providers and clients interpret those messages.
Use a transactional email provider or existing mail service while keeping calendar data elsewhere. Document behavior when mail fails: does the event save, does attendee status change, and can cancellation retry? Test the complete path before promising self-hosted invitations.
Migration proof of concept
Run a reversible pilot before importing real data. Use one test account, desktop client, and phone. Create:
- Simple local event.
- Weekly recurrence.
- Time-zone boundary.
- External invitee.
- Invitation acceptance.
- Invitation update.
- Invitation cancellation.
- Offline edit and reconnection.
- Conflicting edits from two clients.
- Backup-restored event.
Record creation and sync times, notifications, attendee status, displayed time zone, and final content. Test automatic and manual setup. Export, delete, restore, and compare the test calendar. Then migrate a copy of real data, retaining the original export through one normal scheduling cycle.
Backup, restore, and security
Back up calendar data, account configuration, secrets, reverse-proxy configuration, and required database or storage metadata. Event files alone may not restore authentication or deployment.
Rehearse recovery: restored calendars should be readable, clients should reconnect, recurring events should remain intact, and invitations should not resend. Keep one backup offline or in another failure domain; define retention and recovery time.
Use HTTPS, unique credentials, least privilege, timely upgrades, and monitoring for certificates, storage, and suspicious authentication. Restrict admin interfaces, review logs, and plan for unexpected outbound mail. Radicale · Baïkal installation guide
When managed cloud is better
Managed cloud fits when availability matters but nobody owns operations. It also helps when you need dependable invitations, polished clients, delegated administration, recovery assistance, or predictable mobile behavior.
You exchange infrastructure responsibility for provider dependency. Review exports, account recovery, retention, data location, domain and SMTP support, cancellation handling, and incident history. Avoid services that lock away data or export poorly.
See Calendly alternatives, Nextcloud, and related guidance in Scheduling.
FAQ
Is Radicale or Baïkal better for a self-hosted calendar?
Neither is universally better. Radicale suits a focused, minimal CalDAV/CardDAV deployment. Baïkal suits operators who prefer its lightweight server and administration approach. Choose based on deployment comfort, client behavior, and recovery procedures.
Is Nextcloud Calendar overkill?
It is overkill when you only need calendar and contact synchronization. It is appropriate when you already need broader collaboration capabilities and want calendar permissions, users, and files in one platform.
Can a self-hosted calendar send invitations?
It can participate in invitations, but calendar storage and email delivery are separate responsibilities. You need reliable SMTP and must test invitations, updates, cancellations, bounces, and external-recipient behavior.
What is the safest first step?
Run the ten-event proof of concept with one desktop client, one phone, recurring events, time-zone changes, invitations, offline editing, and restore. Keep production data on the existing service until the pilot passes.