Native by default
Calendars, tasks and contacts live in first-party Kamori clients, with offline editing built in.
The encrypted operation log is the source of truth. DAV never defines the cloud model; it is a local desktop projection for interoperability.
Calendars, tasks and contacts live in first-party Kamori clients, with offline editing built in.
Android and iOS can project selected collections into system calendars or contacts only after explicit consent.
The desktop app can provide a localhost-only CalDAV/CardDAV endpoint for established desktop clients.
Calendar / contacts app ↔ local DAV bridge ↔ device cryptoRegistration starts on the web. Desktop and mobile apps are sign-in only and use the same encrypted account state.
WEB
The fastest way to start. First-party calendar, task and contact views, available from any modern browser.
Use Kamori on the web →MAC · WINDOWS · LINUX
Native organizer and sync controls for macOS, Windows and Linux, plus the optional local DAV bridge.
Desktop releases →ANDROID
iOS · Coming soonThe offline-first Android app is available now. The iOS release is coming soon. Optional system projection is per collection and can be disabled again.
Android releases →Kamori uses OPAQUE password authentication, passkeys on the web, device-held keys and a signed encrypted operation log. We document the limits too: timing, membership and traffic volume can remain visible to the service.
The hosted service stores encrypted operations and blobs. Decryption keys remain on authorized devices.
No. The web, desktop and mobile apps are full first-party clients. DAV is an optional desktop compatibility feature.
No. Android and iOS use native system calendar/contact APIs for optional projection; Kamori does not keep a mobile localhost DAV server alive.
The server and web client are AGPL-3.0-only. Self-hosting is planned after the hosted MVP; the current server documentation is available for contributors.
Server documentation ↗