Best self-hosted calendar sync tools in 2026

By Rida F'kih · November 15, 2026

The best self-hosted calendar sync tool for most people is Keeper.sh, a managed calendar sync service you can also self-host. It copies events one way or two way between Google Calendar, Outlook, iCloud, Fastmail and any CalDAV server, such as Nextcloud, Radicale or Baïkal. Use the hosted version at keeper.sh and there is nothing to run. Use the same code on your own server and every paid feature comes with it. The other options each cover part of the job: vdirsyncer syncs CalDAV and Google from a command line, Outlook Google Calendar Sync (OGCS) pairs Outlook with Google from a Windows PC, and DAVx⁵ puts a server's calendars on an Android phone.

Self-hosted calendar sync tools compared

Each tool is compared on direction, which calendars it reaches, what a copied event shows, and what you have to keep running for it to work. The servers that store a self-hosted calendar, such as Radicale, Baïkal and Nextcloud Calendar, are compared in self-hosted calendar servers and sync tools.

ToolDirectionCalendars it syncsWhat a copy showsStops loops and duplicatesWhat you keep runningLicence
Keeper.shOne way or two way, one connection per directionGoogle Calendar, Outlook, iCloud, Fastmail, any CalDAV server, and iCal links as a sourceA busy block named after the source calendar by defaultYes: each connection skips the copies its reverse madeNothing on the hosted version; one container on your own serverAGPL-3.0; hosted Free plan, or Pro at $9/month (pricing)
vdirsyncerTwo way, by pairing two storagesCalDAV, CardDAV, local folders and Google CalendarThe full eventTracks pairs in a status folder; conflicts follow your configA cron job or timer on a machine that stays onBSD 3-Clause
OGCSOne way or two wayOutlook and Google CalendarThe full event, including attendees, by defaultYes, between its own pairA Windows PC that stays on with OGCS openMPL-2.0
DAVx⁵Two way, device to serverOne CalDAV server and an Android phoneThe full eventNot applicable: it does not copy between accountsThe app on each Android phoneGPL-3.0
Nextcloud Calendar subscriptionsOne way, read-onlyAn iCal link shown inside NextcloudThe full event, read-onlyNot applicableYour Nextcloud serverAGPL-3.0
n8n or ActivepiecesWhatever you buildGoogle Calendar and Outlook steps, among othersWhatever you buildOnly if you build itA workflow server, or their cloudsSustainable Use License 1.0 (n8n); MIT outside enterprise directories (Activepieces)

Licences come from each project's repository, checked on 15 November 2026.

Keeper.sh: managed calendar sync you can also self-host

Keeper.sh reads events from one calendar and writes a copy into another, so every calendar you use shows you as busy at the same times. It connects to Google Calendar and Outlook by sign-in, to iCloud and Fastmail with an app password, and to any CalDAV server by its address, username and password. One CalDAV server counts as one account, however many calendars it holds.

Each copy is a busy block named after the source calendar. The title, description and location are hidden by default, Pro can turn them back on per calendar, and guest lists are never copied. A connection runs one way, so two-way sync is two connections, and each connection skips the copies the other one made. That is what stops two-way sync from looping, a problem explained in what is calendar sync.

The hosted version

The hosted version is the quickest route: sign in at keeper.sh, connect two accounts and pick a direction. There is nothing to install, back up or upgrade, and you don't have to register Google or Microsoft sign-in apps of your own.

  • Free: 2 calendar accounts, 3 connections and 1 shareable calendar link, with changes landing every 30 minutes.
  • Pro: $9 a month or $79 a year for unlimited accounts and connections. Google and Outlook changes land within seconds; iCloud, Fastmail and CalDAV changes land every minute (pricing).

A hosted account can reach a self-hosted CalDAV server as long as the server has a public HTTPS address. A server reachable only at localhost or a home address such as 192.168.1.20 can't be reached from the internet.

The self-hosted version

The self-hosted version runs the same code as the hosted one, and every account on your instance gets every Pro feature with no plan limits (self-hosting). The keeper-standalone image bundles the web app, API, cron, worker and MCP services with PostgreSQL and Redis in one container. Six other images let you place each service yourself (Keeper.sh README, checked 15 November 2026).

What running it yourself involves:

  • Docker and a machine to run it on. Put it behind a reverse proxy that handles TLS if you want to reach it from outside your network.
  • Your own Google and Microsoft OAuth apps. Google Calendar and Outlook need client credentials registered under your own Google Cloud and Azure accounts. iCloud, Fastmail, CalDAV servers and calendar links need nothing extra.
  • A public address for realtime updates. With WEBHOOK_PUBLIC_URL set to a public HTTPS origin, Google and Microsoft push changes and they land within seconds. Without it, the instance polls.
  • Local servers work. A self-hosted instance can reach a CalDAV server on your own network, because private addresses are allowed unless you turn on BLOCK_PRIVATE_RESOLUTION.
  • Your own sign-in. Sign-in can be handed to any OIDC provider, such as Authentik, Keycloak, Pocket ID or Zitadel, and REGISTRATION_EMAIL_DOMAINS limits who can create an account.

Your events, connections and linked accounts live in a PostgreSQL database you run, and CalDAV passwords are encrypted with a key you generate. The trade, as the self-hosting page puts it, is a server, a domain, upgrades and backups in place of the hosted service, which is free for 2 calendar accounts and 3 connections, and $9 a month on Pro for unlimited calendars.

Both versions serve the same MCP server and REST API, so an AI assistant can read and write every connected calendar through one connection. A self-hosted instance serves it at /mcp on your own domain.

vdirsyncer

vdirsyncer is a command-line tool that syncs calendars and address books between storages: CalDAV servers, CardDAV servers, local folders of .ics files, and Google Calendar through its google_calendar storage. You define a pair of two storages in a config file, and each run syncs them both ways (vdirsyncer configuration, checked 15 November 2026).

It is under a BSD 3-Clause licence and still maintained: version 0.21.0 was published on PyPI on 4 September 2026 (PyPI, checked 15 November 2026). It has no scheduler and no background service, so you run it from cron or a systemd timer. Microsoft accounts are not among its documented storages, so it can't reach Outlook, and it copies whole events, not busy blocks.

vdirsyncer suits someone who already lives in a terminal and wants a Radicale or Baïkal server mirrored with a Google calendar or a local folder.

Outlook Google Calendar Sync (OGCS)

OGCS is a free, open-source Windows application that syncs an Outlook calendar with a Google calendar, Outlook to Google, Google to Outlook, or both (OGCS, checked 15 November 2026). Version 2 needs the classic Outlook desktop client. Version 3, still in alpha as of v3.0.6 on 1 November 2026, connects to Microsoft 365 through Outlook Online and is the route for new Outlook (OGCS releases, checked 15 November 2026). It is under MPL-2.0.

It runs on your own PC rather than a server, so it only syncs while that PC is on and OGCS is open. It covers Outlook and Google only. A head-to-head is in the OGCS alternative.

DAVx⁵

DAVx⁵ is an Android app under GPL-3.0 that syncs CalDAV, CardDAV and WebDAV accounts into the phone's own calendar and contacts. It is free to build or install from F-Droid, and sold for a small fee in commercial app stores (DAVx⁵ download, checked 15 November 2026).

DAVx⁵ syncs a phone with a server; it doesn't copy events from one account into another. It is how most Android users reach a Radicale, Baïkal or Nextcloud calendar. To get those events onto a work Google or Outlook calendar as well, pair it with a tool that syncs accounts, such as Keeper.sh.

Nextcloud's own calendar subscriptions

Nextcloud Calendar can add another calendar from an iCal link, such as Google's secret address. The result is a read-only subscription, refreshed once a week by default unless the administrator changes the interval (Nextcloud manual, checked 15 November 2026). It shows the other calendar inside Nextcloud but never writes anything back, so the other side never sees your Nextcloud events.

For two-way sync between Nextcloud and Google or Outlook, see how to sync Nextcloud Calendar with Google Calendar and how to sync Nextcloud Calendar with Outlook.

n8n and Activepieces

n8n and Activepieces are workflow automation platforms you can self-host, with Google Calendar and Outlook steps among their integrations. Neither has a calendar mirroring feature: a sync is a workflow you build, and deletions, moved events, duplicates and loops between two directions are yours to handle.

n8n's Google Calendar node can create, get, update and delete events (n8n docs, checked 15 November 2026). Activepieces' Microsoft Outlook Calendar piece can create, delete and list events, with no triggers (Activepieces, checked 15 November 2026). n8n's Sustainable Use License allows internal business, non-commercial and personal use; Activepieces is MIT outside its enterprise directories.

They make sense when calendar steps are one part of an automation you already run, not as a standing sync between two calendars.

Why CalDAV servers can't sync with each other on their own

CalDAV lets a client read and write a server; it has no instruction for one server to copy its calendars into another. Radicale, Baïkal and Nextcloud have no connector for a Google, Microsoft or Apple account, and Outlook doesn't speak CalDAV at all. So keeping a self-hosted calendar and a Google or Outlook calendar showing the same busy time needs a third piece of software, one that reads one side and writes the other. That is the job of every tool on this page.

Which self-hosted calendar sync tool to pick

  • A self-hosted server kept in two-way sync with Google Calendar, Outlook or iCloud, without running another service: hosted Keeper.sh.
  • The same thing, with everything on your own hardware: self-hosted Keeper.sh.
  • A CalDAV server mirrored with Google or a local folder from a command line: vdirsyncer on a cron job.
  • Outlook and Google on a Windows PC that stays on: OGCS.
  • Your server's calendars on an Android phone: DAVx⁵.
  • Calendar steps inside a larger automation: n8n or Activepieces.

Common questions about self-hosted calendar sync

Can I self-host Keeper.sh?

Yes. The keeper-standalone Docker image runs the whole service, with PostgreSQL and Redis, in one container, and every account on your instance gets every Pro feature with no plan limits. Google Calendar and Outlook need OAuth apps you register yourself. If you'd rather not run a server, the hosted version at keeper.sh is the same code.

Do I need to self-host Keeper.sh to sync a self-hosted calendar?

No. The hosted version connects to any CalDAV server with a public HTTPS address, such as Nextcloud, Radicale or Baïkal, and syncs it with Google Calendar, Outlook, iCloud or Fastmail. Self-hosting Keeper.sh is only needed if you want the sync service on your own hardware too, or your server has no public address.

Is there a free self-hosted calendar sync tool?

Yes. Self-hosted Keeper.sh, vdirsyncer and OGCS cost nothing to run beyond your own machine. Hosted Keeper.sh is also free for 2 calendar accounts and 3 connections, with changes landing every 30 minutes.

Can vdirsyncer sync with Outlook?

No. vdirsyncer's documented storages are CalDAV, CardDAV, local folders and Google Calendar; Microsoft accounts aren't among them. Keeper.sh and OGCS both sync with Outlook.

Does two-way calendar sync create duplicates?

It can, if each direction copies the other's copies back. Keeper.sh avoids this because each connection skips the events its reverse connection wrote. With vdirsyncer or a workflow tool, how conflicts and duplicates are handled depends on your configuration.

Sources

All pages were checked on 15 November 2026.

  1. Keeper.sh README: self-hosted images, environment variables, OAuth and OIDC setup, AGPL-3.0.
  2. Keeper.sh self-hosting: features, providers and requirements of a self-hosted instance.
  3. Keeper.sh pricing: Free and Pro limits and sync timing.
  4. Keeper.sh MCP server and REST API: hosted and self-hosted endpoints.
  5. vdirsyncer configuration: storages and pairs.
  6. vdirsyncer on PyPI: version 0.21.0, 4 September 2026. vdirsyncer repository: BSD 3-Clause.
  7. Outlook Google Calendar Sync: Windows, sync directions, classic Outlook for v2. OGCS releases: v3.0.6 alpha. OGCS repository: MPL-2.0.
  8. DAVx⁵ download: Android, F-Droid and paid stores. DAVx⁵ repository: GPL-3.0.
  9. Nextcloud manual: Calendar app: read-only subscriptions, weekly refresh by default.
  10. n8n Google Calendar node and n8n LICENSE.md: event operations and Sustainable Use License 1.0.
  11. Activepieces Microsoft Outlook Calendar piece and Activepieces LICENSE: actions and MIT licence.
Can Keeper.sh use cookies for analytics?