Davis VS vdirsyncer

you don't setup multiple calendars on a device, you use one auth that manages multiple calendars. I think you are thinking too much about this in theory versus experienced application. Don't over-engineer a solution when a simple one exists. Btw, this is a pretty decent calendar solution if you need a self hosting one. Not sure how good your existing solution is working. https://github.com/tchapi/davis

Have a look at vdirsyncer. Sync calendars to a local directory and then use eMacs to read them.

I found vdirsyncer which seems like a nice and promising idea similar to maildir which I already use with notmuch, even though it seems too opinionated and the support for Google calender seems largely untested/unsupported.

For getting ics files, have you seen vdirsyncer ?

On another topic, I maintain a tool to synchronise calendars (e.g.: events and todos) using CalDav (a standard HTTP-based protocol which a lot of calendar servers implement). I'm actually rewriting this in Rust full-time these days.

I used https://github.com/pimutils/vdirsyncer and made a cronjob for it on my host. The configuration is pretty simple - but always do a backup before testing! :)

Whatever CalDAV type calendar you go with (NextCloud and Radicale have been suggested here, Sabre/DAV, DAViCal and Baikal are other options), in case you need to sync calendars to it, you might want to look at vdirsyncer. This way, everyone can keep using his favorite app and you can still gather everything in once central place and have it all synced. Or you get everyone to set up DAVx5.

I have recently started organizing my calendars using `vdirsyncer` [vdirsyncer](https://github.com/pimutils/vdirsyncer)

Hm. Generally for folks who are familiar with the command line I suggest using vdirsyncer, a nifty little python program that lets you keep remote calendars in sync.