Nextcloud Calendar: the CalDAV frontend for a self-hosted Nextcloud server

What Nextcloud Calendar solves, and who it is actually for

The problem is not "I need a calendar". It is "I already store files and talk to colleagues on a Nextcloud instance, and I do not want a second account, a second login and a second sharing model for scheduling." Nextcloud Calendar answers that by living inside the server you already run. The README describes it as a calendar app for Nextcloud that syncs events from various devices and lets you edit them online.

The intended user is an administrator or team running self-hosted Nextcloud. The integration list in the README is the real argument: Contacts, Talk, Tasks, Deck and Circles. Tasks and Deck cards with a due date show up in the calendar view, and the README says you can create an associated Talk room when booking a meeting. None of that is available to a standalone calendar client, because none of those objects exist outside Nextcloud.

If you do not run Nextcloud, this app has nothing to offer you. It is not distributed as a standalone web application. The README states it is distributed through the Nextcloud app store and installed from inside your Nextcloud installation. There is no docker run line and no hosted service.

Frontend over CalDAV: where the code actually lives

The most important architectural fact is buried in the support section rather than the feature list. The README says plainly that this repository only manages the frontend, and that bugs or problems with the CalDAV backend should go to the Nextcloud server team. That single sentence tells you where to file an issue and, more usefully, where not to look when something breaks.

The frontend is a Vue application. The package manifest lists @fullcalendar/vue3 alongside the FullCalendar view packages (daygrid, timegrid, list, multimonth, resource-timeline), so the month, week, list and resource views are FullCalendar components wrapped for Vue. Event data is not parsed by hand: the README names the c-dav library for CalDAV access and ical.js for iCalendar parsing, and the repository topics include rfc-5545, the iCalendar specification. Rendering and data access are therefore separate concerns, and a rendering bug and a sync bug will surface in different places.

The build tooling is rspack, not webpack, and the package version is 6.7.0-dev.1. Tests are split: vitest for unit tests, Playwright for end-to-end, PHPUnit for the backend pieces that live here. If you plan to contribute, that split matters more than the feature list, because a change to how an event is displayed usually needs a Vue unit test and possibly a Playwright flow.

Installing Nextcloud Calendar from the app store

The README gives no command-line installation. It says the app is distributed through the Nextcloud app store and can be installed right from your Nextcloud installation, linking to the server's apps management documentation. So the first real use is a click path, not a shell session: open your Nextcloud instance as an administrator, go to the Apps section, find Calendar and enable it. Release tarballs are hosted at the nextcloud-releases/calendar repository if your setup installs from archives instead.

Once enabled, the app appears in the Nextcloud app menu. From there, a first useful action is adding a WebCal feed, which the README lists as a supported feature for things like a team's matchdays. The app also supports inviting attendees, free/busy lookup, reminders in the browser and by email, and search across events.

If you are building the app from source rather than installing the release, the README lists the prerequisites as Node.js and Composer, with these steps:

composer install
npm ci
npm run build

The README documents npm run dev for a development build and npm run watch to rebuild on changes, with npm run build for production. The package manifest shows those scripts run rspack. A source build is for development or packaging, not for a normal server install; the app store path is the supported one for administrators.

Where Nextcloud Calendar is the wrong tool

The clearest limitation is structural: this app cannot be separated from Nextcloud. If you want a calendar for a small group with no file sync, no Talk and no Deck, you are paying the operational cost of a full Nextcloud server for a scheduling view. That is a large amount of PHP, database and upgrade surface for one feature.

The second limitation is support boundaries. Because the repository only manages the frontend, a sync failure, an authentication failure or a CalDAV protocol problem is not fixed here. The README directs those reports to the Nextcloud server project. From an operator's perspective that means two upgrade tracks to keep aligned: the server release and the app release. The app store handles compatibility for the common case, but a mismatch is a class of problem this repository will not resolve for you.

Third, the browser list in the README is dated: Chrome/Chromium 76+, Edge 40+, Firefox 60+, Safari 12.1+, and it still lists Internet Explorer 11. Those floors are old enough that they say little about current browser support. The README does not state which browsers are tested in CI, and the Playwright configuration in the repository would be the place to look, not the README. Treat the list as a minimum, not a guarantee.

How it compares with Radicale plus a generic CalDAV client

The honest alternative for someone who only needs CalDAV is a dedicated CalDAV server such as Radicale, paired with a desktop or mobile client. The difference in approach is the whole point. Radicale stores calendars and speaks CalDAV; it does nothing else. Nextcloud Calendar is the opposite shape: a rich frontend that assumes a Nextcloud server underneath it, providing sharing, WebCal subscriptions, attendees, free/busy and reminders, plus visibility into Tasks and Deck items.

So the choice is not about which calendar is better. It is about whether you want an account system, a sharing model and a set of related apps around your events. If you do, Nextcloud Calendar comes almost free once the server exists. If you do not, Radicale is a smaller thing to run and to upgrade, and you lose every integration the README lists.

A second comparison is with the calendar applications you already have on a phone or laptop. Those connect to a CalDAV account and will happily talk to your Nextcloud server. Nextcloud Calendar's advantage over them is the server-side pieces: sharing with other Nextcloud users and Circles, and the cross-app views. If your users only ever read their own events on their own devices, the app adds less than its install cost suggests.

Maintenance, licensing and the upgrade bill

The repository is not archived and the last push was on 2026-09-10, so development is current. That is a statement about the repository, not a promise about releases. The listed releases go back to v3.3.2 in June 2022, while the package manifest declares version 6.7.0-dev.1, which means the release list does not reflect the current development line. Anyone pinning a version should read the app store page for the version compatible with their server rather than trusting an old tag.

The licence is AGPL-3.0. The README carries SPDX headers naming Nextcloud GmbH and ownCloud, Inc., and the repository has a REUSE.toml and a LICENSES/ directory. For an administrator, the practical consequence is the usual one for AGPL server software: running it on your own server for your own users is the normal case, but if you modify it and expose it to users over a network, the licence's source-availability terms are the part to read. That is a question for your legal team, not something this article can settle.

Upgrade cost is dominated by the coupling to the server. Because the app depends on Nextcloud APIs and on the CalDAV backend, a server upgrade can require an app upgrade, and the app store normally enforces that pairing. Budget for testing both together, and check the supported browser list against whatever your organisation standardises on.

Editorial conclusion

Adopt Nextcloud Calendar if you already run a Nextcloud server and want events, WebCal feeds and sharing in the same account as files, Talk and Tasks. Do not adopt it as a standalone calendar or as a CalDAV server: the README states this repository only manages the frontend, and CalDAV problems go to the Nextcloud server team. Before rolling it out, check the app store page for the version that matches your server release, confirm the browser you standardise on appears in the supported list, and test one CalDAV client against your server before migrating a team.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. nextcloud/calendar on GitHub
3. Project website
4. README
5. Releases