Horde Kronolith vs Decsync Calendar Sync
A side-by-side comparison of two self-hosted calendar & contacts options — licensing, setup difficulty, resource needs, and what each one replaces.
| Feature | Horde Kronolith | Decsync Calendar Sync |
|---|---|---|
| Deploy effort | Read-the-docs project | Read-the-docs project |
| Health score | 69 · Good | 15 · At risk |
| Category | Calendar & Contacts | Calendar & Contacts |
| License | GPL-2.0 | GPL-3.0 |
| Language | PHP | Kotlin |
| Setup difficulty | Hard | Medium |
| Min. RAM | 256 MB | 128 MB |
| Deployment | bare-metal | source, binary |
| GitHub stars | ★ 10 | ★ 699 |
| First released | 2003 | 2018 |
| Replaces | Google Calendar, Exchange | Google Calendar |
What are Horde Kronolith and Decsync Calendar Sync?
Horde Kronolith
Kronolith is the calendar component of the Horde groupware framework. It provides shared calendars, event management, and supports CalDAV synchronization with desktop and mobile clients.
- Part of Horde groupware
- Shared calendar support
- CalDAV synchronization
Decsync Calendar Sync
Decsync is a method and toolset for synchronizing calendars and contacts via a shared folder rather than a central server. Self-hosters pair it with a file-sync service to keep events consistent across devices.
- Folder-based sync
- No central server
- Calendar and contacts
- Pairs with any file sync
Horde Kronolith vs Decsync Calendar Sync: key differences
Horde Kronolith is written in PHP, while Decsync Calendar Sync is built with Kotlin. Licensing differs — GPL-2.0 for Horde Kronolith versus GPL-3.0 for Decsync Calendar Sync. Decsync Calendar Sync is the lighter option, starting around 128 MB of RAM against 256 MB for Horde Kronolith. Horde Kronolith is the more established project (first released 2003), while Decsync Calendar Sync arrived in 2018. Decsync Calendar Sync has the considerably larger community, at 699 GitHub stars versus 10.
Why pick each one
Choose Horde Kronolith if…
- Released under the GPL-2.0 license
- Written in PHP
- Tiny footprint — runs in 256 MB RAM
Choose Decsync Calendar Sync if…
- Server-free architecture
- Privacy friendly
Watch out for
- Requires a sync layer
- Setup is non-trivial
Frequently asked questions
Is Horde Kronolith or Decsync Calendar Sync better?
Decsync Calendar Sync is the stronger all-round pick: it has both the larger community and the simpler medium setup. Consider Horde Kronolith if its specific feature set fits your needs better.
Are Horde Kronolith and Decsync Calendar Sync free and open-source?
Yes. Horde Kronolith is licensed under GPL-2.0 and Decsync Calendar Sync under GPL-3.0. Both can be self-hosted at no software cost.
Can I run Horde Kronolith and Decsync Calendar Sync with Docker?
Horde Kronolith: check the project docs for container support. Decsync Calendar Sync: check the project docs for container support.
Which is lighter on resources, Horde Kronolith or Decsync Calendar Sync?
Decsync Calendar Sync has the smaller minimum footprint at 128 MB of RAM, compared to about 256 MB for Horde Kronolith. Real-world usage depends on library size, user count, and enabled features.
Related comparisons
- Horde Kronolith vs AgenDAV
- Decsync Calendar Sync vs AgenDAV
- Horde Kronolith vs calcurse
- Decsync Calendar Sync vs calcurse
- Horde Kronolith vs Etar
- Decsync Calendar Sync vs Etar
- Horde Kronolith vs EteSync
- Decsync Calendar Sync vs EteSync
- Horde Kronolith vs GNOME Calendar
- Decsync Calendar Sync vs GNOME Calendar